UML War Needs analysis read Note 04

UML War Needs analysis read Note 04

After reading the first 8 chapters of the UML War needs analysis, my understanding of the book reached a node. According to the list of the book and the names of the chapters, I divided the book into two parts, the first part is the concrete use of UML summary and explanation, the second part is a concrete example of deep application. After reading the first part, I did some tidying up and understanding.

First, it is the use of various diagrams . UML diagram of the actual use of the structure of UML: Class diagram: Must be used to analyze business concepts. Component diagrams and deployment diagrams: Must be used to analyze the needs of the IT infrastructure, software architecture, and so on. Behavioral UML: Use case diagrams: Must be used. Activity diagrams, state machine diagrams, Sequence diagrams: You must use at least one of them to analyze your business processes. The remaining figures are rarely or basically unused.

class Diagram : In the actual work, we need to put out all the business objects, characters, etc that we know in the demand research, draw their relationship, repeated deliberation, to get the appropriate business model gradually. Therefore, the actual display of the class diagram allows us to fully systematic understanding of the relationship between stakeholders, if there are errors, redundancy, but also at a glance, reduce the burden of demand analysis. Class diagram Let us basically understand the business concept, so that we should understand the business process, the process of the Three Musketeers to help a lot.

The first is the activity diagram , this figure is basically our previous high school mathematics study flowchart, and in the demand analysis, he has his own steps; 1. What is the business purpose of the process? 2. What are the roles involved in this process? What are the main roles? 3. Exclude anomalies (i.e. branch processes) and draw the normal process, i.e. the backbone process. 4. Identify the activities and roles in the backbone process. 5. Gradually increase the branching process, the key branch process to express, but not all to write out (if necessary, note description). 6. Proper control of grain size. 7. First draw the whole, then optimize. 8. Before and after the optimization, collate the business redundancy or unreasonable place with the customer exchange.

Then the state machine diagram , the thinking points: 1. What is the process about? 2. What is the status of this character? 3. This represents the branching structure when a state can be replaced by one or two states.

The last is the sequence diagram , 1. Analyze a process from a complex process, and then parse each process in the following way. 2. Analyze what roles are involved in this process? 3. Analyze the roles of each role in the process and the professional characteristics of each role. 4. Break the process down into interactions between roles and figure out what the "interface" between the roles is. 5. Organize these "interactions" in a sequential diagram. 6. In the above process, continuously consider the rationality of the business process, whether it can be optimized or reorganized. Flowchart, as the name implies, is to show the flow diagram, only the whole process has a clear thinking, to find the system needs to do things, and the flow chart is the process of finding more image concrete, not have big flaws; the next is the most commonly used, the most indispensable use case diagram.

use case diagram : 1. Streamline (on the basis that the customer can understand accurately). 2. Describe it in the customer's language. 3. Comprehensive and focused, with detailed focus and difficult points. 4. Customers and higher than customers, not blindly. 5. Refine the use case, the granular control of the underlying use case is broadly consistent, flexible grasp.

UML War Needs analysis read Note 04