UML War Needs analysis Read Note 06

UML War Needs analysis Read Note 06

This time I read the last two chapters of the UML War Requirement analysis and have a summary of the book

In general, the role of UML is to conduct structural modeling and behavior modeling, so that the entire demand analysis quickly and comprehensively will not produce too much fault, according to these two models, is the entire software writing context is clearly visible. The role of demand analysis is to clear the project background, to find users or stakeholders, to resolve the project business process, clear and solve customer problems. And UML is used to solve the next three problems, UML is a tool in the end, so that our work becomes convenient and not easy to make a mistake, the author in the explanation, will give some small examples, is to explain more vivid, through examples are more easy to understand, I believe the actual use of the following examples will be more exciting.

The reason why demand is so difficult is because the client side wants to spend less money function as much as possible, while the idea of the software company is to spend less work, the customer's idea is constantly changing, but this change overall is to want to the final goal, Kezhouqiujian's story shows that the changing customer idea to let them sign confirmation is meaningless, Customers constantly ask questions when a double-win effect, indicating that customers have been applying this software, so that software companies can also get their own desired economic and other aspects of the ' win '. The customer is certainly aware of their own domain, so they begin with a higher demand perception than a software developer, but only later will the developer's needs become more cognitive than the customer can really do the software. The core of demand analysis is to solve the problem that software has no use, and the core of software design is to solve the problem of software development cost, the more the bottom user is easy to put forward the problem of requirement specification, the more high-level is apt to ask the question of demand, the combination of demand and UML The structure of UML diagram can be used to model the customer's business structure, the business concept and other static structure of the systematic combing and refining, that is, the business concept of combing and refining is called the structure modeling, business process is called behavior modeling.
On the object-oriented and process-oriented, the beginning of the programming is a line of lonely code, and later on to deal with complex problems is just a line of code appears cluttered, and then a method, the encapsulation of some behavior, by invoking the method to achieve the purpose of operation, and then the structure of large-scale software can not just through function calls to meet, Object-oriented C + + emerged. Two use cases in common with minimum assurance and success scenarios and extended scenario extensions are possible in the execution of the unexpected situation in the case of the black box is not too concerned about the specific details, said the different methods applicable to different environments, the size of the software is different for use cases of the formal level of the requirements are also different, Formally, according to the use case pattern of an item to add a scene, definition, rather than complete only the description of the scene, from the use case can be seen in part or the main requirements, the purpose of the use case is aimed at the user, let the user know in advance what the new system is for the purpose of the requirements of the scope, the use of terminology,

Finally summarizes the structure diagram has six kinds, the behavior chart has seven kinds. All the contents of this book cannot be wholly believed, and all must digest knowledge according to their own understanding.

UML War Needs analysis Read Note 06