Document management on lessons learned from software engineering

Chaos in document management is the most fatal and confusing of the previous project. I personally think it is terrible if a project team develops a system without a document, in system development, there is no effective management of documents. What we need to do is a product, not a test product that we entertain ourselves. As a product, we must adopt standards, the standards will be discussed in detail later, whether it is the standards that the customer gives us or the standards that the development team gives itself. When there are standards, relevant documents are necessary. The benefits of the documents are cleared. It plays an important role at any stage of software development, deployment, and maintenance, I think the document is not in the form of a development team owner's attitude towards the document and I feel happy with the success or failure of this system (exaggerated ).

In addition to carefully working on relevant documents at various stages, we also need to effectively manage the documents. The following describes some development of document management over the past few years, which is just a reference. You are welcome to add more and more bricks.

1. The document version is required.

Like software, if you do not manage or control the version of a document, modifications to the document will lead to confusion. Especially for large projects, you must control the version of the document management, otherwise, every time you modify the document, you cannot find out when to make any modifications.ProgramStaff's work is very difficult to carry out.

2. Special personnel are required for documents.

If a group has enough people, I hope one person will be responsible for document management. If the development team is busy, one person in the group will be responsible, no one can take all the documents at will.

3. Strict regulations should be imposed on document modification.

Once a document is created, it cannot be modified at will. Of course, you must carefully discuss and determine the document before it is finalized. Once the document is determined, it cannot be modified at will, especially in the early stage, such as requirement analysis, after a change in demand analysis, all the design documents must be changed. This change will affect the overall progress of the system and the quality of the software. Make a record of why this change is made every time you modify it. The modified part will affect the document that must contain the initiator and approver of the document modification.

4. Number of documents.

I personally think that only one document is required for each version of a development team of less than 10 people. In particular, there is only one document circulating in the developer's hands during the development phase, you can view documents by reading each other. Not every document may affect the progress of the project. After each document modification in the previous project, each person can print a document of nearly pages. One is a huge waste, and the other is that the version is not properly controlled. Each person has more than one document, at the beginning, we were still quite clear about which document should be used in the end.