"Requirements Engineering-software modeling and Analysis" book Three

The common requirements analysis techniques include upper and lower article, data flow Diagram, entity contact graph, functional entity matrix, function decomposition diagram, process dependency graph, use case diagram, class diagram, interaction diagram, activity diagram, constraint language of the opponent, Micro Specification, dictionary, state transition diagram and so on.

We've learned the context diagram before. Its main function is to describe the boundaries and linkages between the system and the external entities in the environment. He illustrates the boundaries and environment of the system from a real-world perspective, and identifies all inputs and outputs. The data flow diagram is also used frequently, it describes the function processing of the system from the input to the output from the angle of transmitting and processing. The method of functional decomposition is used to simplify the processing of complex problems with hierarchical structure. such as use case diagrams, class diagrams, interaction diagrams, etc., have been learned in previous studies of UML, but are seldom used. Their function is no longer detailed.

There are a variety of technologies for demand analysis, and learning all of these technologies is not an easy task. For each technology, not only need extensive reading, but also need to do a lot of practice, in order to grasp the connotation of each technology well. Practice shows that the biggest problem faced by demand engineers in modeling and analysis is not the mastery of specific technologies, they have the ability to learn and master every technology. The comprehensive application of demand analysis technology is the greatest difficulty for demand analysis personnel.

In the fifth chapter of software requirements analysis, we identify what is the basis of software risk management, including inaccurate estimates, the accurate estimation of the veto, the state of the project is unclear, capital turnover, technical risk, lack of knowledge and so on, so we need to carefully carry out risk management for each project, identify the elements of risk management, Documenting it and managing it properly will help stakeholders understand the risk situation and status throughout the project development process.

"Requirements Engineering-software modeling and Analysis" book Three