Read "UML War Needs Analysis" feeling a

Read the "UML War Needs analysis," the beginning of "nonsense", I deeply feel the rigor of UML senior users and comprehensive.

First, the first part-"Why should I write this book"-is the goal in the software requirements analysis. The modesty language is fascinating, tells us "uses the UML" is the key, through the actual combat ability to truly grasp the UML "God"--uml to embody one kind of work thought and the method. Target :

(1) Understand how UML can help us improve our needs analysis ability;

(2) The practice of demand analysis;

(3) The practice of demand management.

Secondly, the second part-"Who is fit to read this book"-is the stakeholder. Rigorous rhetoric, let us not Pianan corner, I am learning college students, so I can get in this book the benefits are:

Experience the "brutal" software requirements analysis work, learn about UML and requirements analysis, requirements management knowledge, and prepare for future work.

Finally, the third part-"design ideas of the chapters of this book"-is the requirement analysis report of the software requirement. Arrange the whole task in a clear and orderly manner, and schedule the coding work for the software.

Read "UML War Needs Analysis" feeling a