Document management-in progress

DevsuiteThe document management tool in the system is calledKnowledgewiseIn the concept of "knowledge as the core", it is a core position, because in the software development process, each stage needs to be exposed to documents, from Requirement documents to design documents to development documents to test documents and to release document maintenance documents, the document is always required, and the same document may be constantly changed throughout the process, so passKnowledgewiseTracks every change that is important or important to the development process.

 

InKnowledgewiseA document is recorded by means of an item, that is, a document corresponds to an entry. Each entry consists of fields such as the title, description, owner, and attachment, these fields are custom and can be added according to your needs. This is the so-called basic attribute. The entry also has some advanced attributes, such as permission control, process control, version control, and history tracking. Next I will introduce this system based on the actual process of our company.

 

1. first of all, I will not go into details about those institutional, contractual, and training documents, because these documents do not need to be viewed by everyone, or even confidential, it cannot be seen by many people. PassKnowledgewiseIt can be saved to a location that only relevant personnel can see.KnowledgewiseYou can set different permissions for each file and folder, for exampleRead-only, editable, deleted, and created,Of courseInvisible. Therefore, it is okay to set complex permission combinations. (Permission management)

 

In the two figures below, we can see that we can set different permissions for folders and files, and set different permissions for different people, which means that both people are managers, I can also make a file visible to only one of them.

 

 

 

2. then there are some design documents, development documents, FAQs, and so on. These documents will always go through many processes to generate a finished product in the actual process. Let's take the design documents as an example, A design document may be divided into the following parts: draft-> preliminary review-> continue modification-> review-> final modification-> final review-> agree that these processes, and in each process, the person in charge of the process is not necessarily the same. The draft may be handled by ordinary designers, the preliminary review should be handled by the design team lead, and the final review may be handled by the design director, therefore, we need to set up strict workflows and corresponding permissions. The process has just been said. For example, this document is in the "Preliminary Review" stage, the design team lead must have the permission to change the document to the modification state. Others do not have the permission, and even others cannot see the document in this state, in this way, the design team lead must review the document before continuing to modify the document. Some people do not want to skip the process and change the status as soon as possible (of course, inKnowledgewiseYou can skip the process and change the status through custom settings. Under normal circumstances, this must be done by someone with certain permissions, such as a supervisor or manager )(Process Management)

 

The following two figures are a typical document process. The first figure is a custom process in the system, and the second figure is the actual usage of the system client, from the creation to the final creation of a document, the process must be completed by the person in charge of each State under normal circumstances. This basically guarantees the quality of a document. In the system, every person who can access the system can view the document tasks in different States that need to be processed as soon as they enter the system, including writing documents, modifying documents, and reviewing documents.

 

 

 

 

(To be continued)