Computer room toll System personal refactoring version: Those diagrams in the soft work document

"Preface"

figure, when referring to this word, there will be a lot of images in the mind, it is important to believe that we all understand that compared to the text, it is more vivid image just fits the human brain Memory Law A lot of people also know that the animation principle is to use a picture is only the speed of conversion is fast enough, but also familiar with the mind map and so on. Below we introduce here is software engineering involved in the diagram!

"Figure"

in the previous blog, "Computer room toll system personal Reconstruction version: Document-driven development through documentation" introduces the software in all stages of the document is what the diagram! But no detailed description of the various diagrams, in the end of the entire machine room reconstruction, deeply document is the essence of the whole development, and the picture is the essence of the document. Thus, in this blog post, the machine room is reconstructed as an example to introduce the essence of this essence.

• Gantt Chart:

1, Introduction: The development of task and time allocation, control the entire development process;

2. Recommended drawing tools: Visio;

3. My Gantt Chart:

• Prototype diagram:

1, Introduction: The prototype is a user and demand personnel to reach an important basis, can be in advance to let users have perceptual knowledge;

2, recommended drawing tools:Axure;

3. My prototype diagram:

· IPO Map:

1, Brief introduction: Clear each module specific input, the output, as well as the processing process;

2, recommended drawing tools: Windows comes with drawing tools;

3. My IPO Map:

• Functional frame diagram:

1, Introduction: Clear the function of the whole system;

2, recommended drawing tools: Edraw;

3, my function frame diagram:

• Package diagram:

1, Introduction: In the machine room reconstruction it is equivalent to the frame diagram;

2. Recommended Drawing tools:EA (etherprise Architect); ；

3. My package diagram:

• Use case diagram:

1, Introduction: The whole system has the integrity of the control;

2. Recommended Drawing tools:EA (etherprise Architect); ；

3. My use case diagram:

• Class Diagram:

1, Introduction: Planning out the development process requires developers to complete the work;

2. Recommended Drawing tools:EA (etherprise Architect);

3. My class Diagram:

• Timing Diagram:

1, Introduction: Clear how developers can implement a function;

2. Recommended Drawing tools: EA (etherprise Architect);

3. My timing diagram:

Summary

After reading this blog post, please look back at the readers, believe that many people in the mind will be rippling out of these pictures, which is enough to see the importance of the picture and intuitive. Before writing the document, I hated drawing these UML diagrams and some auxiliary diagrams, thinking that it was a waste of time to draw these things, and now think about how ridiculous I thought. At the same time, I also fell in love with drawing, now encountered problems without thinking or confusion, take pen or open software painting.

And let yourself have a deeper understanding of what you don't have to say .

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

Computer room toll System personal refactoring version: Those diagrams in the soft work document