Do project data flow feel more complex general how do we comb the data flow?

Do project data flow feel more complex general how do we comb the data flow?

Reply content:

Do project data flow feel more complex general how do we comb the data flow?

I am glad to answer the landlord's question.

The data flow in the project, if not clear, is really a very painful problem, but also increases the risk of the project, then how to figure out the data flow. Here are some of my experience, for reference only:

1. Documentation, from project inception, to the final on-line, document management, must be done;
2. or documents, from the requirements analysis, summary design, detailed design, must have the corresponding documents, and need to ensure that the update;
3. UML diagram, this is a very important thing, when the project is big, you will find that you can not leave this thing, such as flowchart, Time series diagram, class diagram and so on;
4. If necessary, would you consider going back to the university's software engineering course?

@JellyThink's opinion is quite agreed, but it's a different idea.

1. UML图: The more complex the process to draw clear this diagram, and how this painting is a science, too complex logic can be expressed in several graphs, such as the relationship between the module diagram, the flow chart within the module.
2. 文档: Why put it in the second place, I think the document does not have to write so much, the focus is to explain the meaning of this UML and why to design, so enough. No one is looking at the document and no one is maintaining the outdated document is not really as good as no!
3. 简单实用: Most do not like books on the rules and regulations, but can learn from some predecessors summed up the experience, the focus is the study methodology, the purpose is to do the immediate things, do not do a business system is not to follow the standard of XX process to do, usually is time-consuming and laborious and useless.

