Computer room toll System personal Reconstruction version: Document-driven development through documentation

"Background"

Computer room charge system personal reconstruction is nearing the end, in the final stage to fill in the document and the diagram involved in it! After nearly a week of fighting to perfect it, and finally through Master's acceptance. Through the machine room reconstruction to write documents and drawings, their feelings are quite deep, here with you to share.

"Document-driven software development process"

• Introduction to Soft industry:

Software Engineering was born after the software crisis of the 60 's. Since then, as people demand more and more high, resulting in greater complexity of system functions! To develop such a large system, such as a single personal development is impossible to complete, there is no doubt that cooperative development is a good solution; but then how to control a lot of people in accordance with certain norms in a certain period of time to complete the system according to a certain standard ??? This is the software engineering to solve the problem, especially in today's times these problems are increasingly protruding, of course, the soft workers are more and more people's attention.

· Soft Work Documentation:

1. Feasibility Study Report:

① Considerations: Technical and economic law market;

② Description: Whether the system can be developed;

③ View Document personnel: Project manager, technical director, customer.

2. Master plan:

① Description: Control the progress of the project;

② should have a graph: Gantt chart;

③ View Document personnel: Project manager, technical director, developer, tester, post-training customer personnel.

3, Demand Analysis:

① Description: Customers and developers to communicate, for developers to develop software to meet customer needs to provide the basis;

② should have graphs: Functional frame diagram, prototype diagram, use case diagram, function model Diagram (ER diagram), IPO, data dictionary;

③ View Document People: Customers, demand analysts, developers, testers.

4. Summary design:

① Description: The whole framework is designed during the development stage;

② should have a picture: frame composition, package diagrams, Class diagram, interface diagram, flowchart, function module corresponding diagram;

③ View Document personnel: Technical Director, developer.

5. Detailed Design:

① Description: Detailed design of the program;

② should have a diagram: Time series diagram, collaboration diagram, class diagram, activity diagram, State diagram;

③ View Document personnel: Technical Director, developer.

6. Database Documentation:

① Description: Guide Database design planning and implementation;

② should have a diagram: ER diagram, database diagram;

③ View Document People: Database Designer, database administrator, Developer.

7. Coded Documents:

① Description: Design of data structure, algorithm analysis and module implementation;

② should have diagram: interface diagram, function module diagram;

③ View Document Person: Developer.

8. Test Document:

① Description: The development of a good program to test to find the system in the bug;

② should have a picture: test case;

③ View Document People: testers, developers.

9. User manual:

① Description: Allow users to quickly use the system, and in the use of the process problems can be quickly resolved;

② should have a picture: interface;

③ View Document Person: User, document reviewer.

10. Software Delivery:

① Description: Deliver things-target installers, database files, user manuals, demand reports.

② View Document Person: User, project manager, document reviewer.

• Document mapping under the development process:

"Summary"

In the machine room reconstruction, I did not first write the document is to design the database and then programming, the final complement of the document. The right process: write the document first and then refine the document during the development process.

Although I have learned the soft work before, but this time to fill the document before the meaning of the document or to write the trouble, I have to achieve the document is meaningless. However, Master's guidance, I do while looking at the side and small partners to communicate, especially in the drawing documents involved in the diagram (Time series diagram, class diagram, etc.) firsthand experience the guiding significance of the document, but also understand the document-driven software development under the meaning.

In the process of learning the first contact with certain things, the understanding of it and the benefits are not very deep, the heart will be questioned. It is also a question of mind: a person chooses to listen to his own mind to adhere to their own ideas no longer to do these things; another person chooses to do, explore, communicate with others, think, summarize . When the latter kind of person has been enlightened, the former one still remains in question. Life is the same when you change yourself you will find that suddenly the world becomes bigger.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Computer room toll System personal Reconstruction version: Document-driven development through documentation