System design staff point of view:
Demand analysis is a truly clear understanding of user needs and is a thorough understanding of issues to be solved. Before resolving the problem, you should understand the problem, only the real understanding of the problem can better solve the problem. Demand analysis is to give systematic analysis, designers a chance to understand problems - understand what users need.
Demand analysis is also a modeling process, and modeling differently in demand analysis in demand analysis is a user-oriented process. The modeling process in the outstanding design is the process of developers. There is a difference between the two modeling processes, thereby using natural language to describe. In the traditional software engineering, it is not recommended to use a large number of natural language to describe the demand for software, because too many natural languages have triggered a lot of problems. For example, unlike the description of the natural language will have a different understanding of the description of the natural language. After all, we are not a language. This introduces the process of using the description and modeling of the borrowing illustration. The illustration has its own advantages, such as, clear, clearly giving people intuitive feelings. Whether it is a background, it can be understood. This greatly reduces the amphibration in demand analysis. Thereby system designers and users more efficient communication. This also increases the correctness of the software. A variety of different icons are provided in traditional software engineering, each of which is described from different angles, which is the case. The system developers can pick up one or some illustrations that are most suitable for his and his team in different icons. For example, data flow maps, using data flow maps in demand analysis, fully reflecting the logic processes that are transformed when moving in a software system. So is the best image for establishing a functional model; and the entity relationship diagram is to describe the data object and the relationship between them, so it is the best example of establishing a data model. The status conversion diagram changes the state through the external effect of the event, which is an example of establishing a behavior model.
When I do demand analysis, I try to explain the problem. However, there is always a problem that I have troubled me. It should choose what kind of legend to perform the system's description, data flow map, status conversion map or entity relationship diagram? In fact, the answers given by different system designers will not be the same. This is not a philosophical problem but an application problem. From the perspective of customers, the use of entity is the best choice, and the data flow map is completely the same as the system designer. Because the programmer is more concerned about the logic and correlation between the things; and the user only cares about the external characterization and characteristics of things. So the question's answer is only for everyone to find, looking for an illustration of the most user demand and problem solution.
When writing a demand analysis according to the template, I found that there are many template entry requirements to be the exact answer to the initial stage of demand analysis. Some entries must be designed, and the document content can be modified and filled after detailed design. At the same time, I studied the demand analysis document written by other peers, and an excellent demand analysis instructions are not to move according to the specified template entry. In fact, some redundant projects can do not have to care. After all, the real purpose of writing demand analysis is to let system designers know the needs of users. Others don't have to be too strong.
