"UML War Needs Analysis" read NOTE I

The first contact with UML was last year, when Liu Lijia teacher taught for us, because there was no specific project, so the UML Course is not very important, I think most people should be the same as I do UML did not give enough attention, this semester we opened the software requirements analysis This course, and let me re-contact UML , I chose to read the UML The Book of demand Analysis to enhance my UML the understanding.

According to the author, he began to think that UML diagrams did not simplify the project, but instead became a burden, but gradually understood the importance of UML to the project after the author began to work. He can express clearly the function of a software, the boundary, the interactive process. Although people who have not learned the UML can not understand the meaning of the various diagrams, but when the user understand that this will be for us and the user's communication brings a lot of convenience, to avoid in the demand analysis phase because of the ambiguous expression of users and our understanding of the gap, After all, the previous demand analysis horseshoes will cause the subsequent stages will be absurd, the book said: The customer needs a ladder, the system analyst learned is a stool, the developer made out is a table, testers think is a chair ...

We must understand the customer in order to do the demand analysis. What does this bring to the customer? What if you don't do this? Only by fundamentally understanding the needs of customers, we can give users reasonable advice, to really solve the problem customers need to solve, rather than make a bunch of useless code!

We have to do is to achieve a win, the customer got what he wants, and we get the user's recognition, this is our win-wins.

The customer's needs are always changing, and we should get used to it instead of complaining. A good software company is not the kind of company that every time customers ask for headaches, a good software company will stand in the customer's perspective to consider the problem, and each time will want to customers in front, to give customers reasonable advice to convince customers.

The third chapter introduces the concept of class diagram in detail, class diagram is the most commonly used diagram in UML, each software system will involve a lot of people, the business of the man and the goods, these things may have a lot of relations between, a lot of things happen. Class diagrams can help us identify these people, business concepts, items and things, and clarify their relationships.

After further study, my understanding of UML and requirements analysis is bound to be more in-depth.

"UML War Needs Analysis" read NOTE I