We strongly recommend two classic oo books and their inspiration for case writing.

Agile Software Development: Principles, models and practices"

Classic old book, no need to say more

The classic examples show the application of almost all major related technologies in Object-Oriented agile development.

 

《UML and pattern applications (formerly known as version 2nd)"

"People often ask me which one is the best book to guide them into the world. After reading this book, it has become my only choice.

--- Martinfowler

 

This book has the following characteristics:

1This book leads readers to discuss the specific iterative development processOoSoftwareUpIterative development process. Will not appear previously known to have mo YiUMLThe view does not know where to use it.

2The actual content of this book is not similar.RoseThe issue of the company's propaganda bias is not the orientation of the academic school with future academic goals.

3The combination of various aspects of software development in the book, and the components of these respective aspects are just right in the book.

4Read carefully. Every sentence in the book is carefully written by the author. It is almost a good sentence, especially the box marked with a profound meaning, with little nonsense.

 

for example, our team is currently collecting Use Case stage, I learned from this book and found many previous Use Case error awareness on .

1 , The Relationship Between the use case diagram and the use case diagram is a secondary part in the case work. The use case itself is a document in text format, and the work of the use case means writing the text. (previously focused on rose contains small people and ovans, as well as arguments over their arrows for connecting lines ). A common sign of newbie (or academic) in case modeling is focused on the relationship between Use Case Diagrams and use cases, rather than text. Top case experts (for example, Anderson , flower , Cockburn ) less emphasis on Use Case charts and Use Case relationships ...

 

2 , It is worth noting that A common case error is that many low-level cases are defined. These use cases are only equivalent (Basic Business Process) EBP A simple step, sub-function, or sub-task in. What I understand EBP It is a user (the role may be an external system) who can clearly reach a user's goal through this use case, and the fulfillment of this goal has measurable business value for the user. For example, user login is generally not a use case but a process. As stated in the book, if CEO Q: "What have you done today ?" You replied, "I logged on. 20 Times !" He will not leave any impression. Login serves to accomplish other useful tasks. Therefore, we found that, for example, reading the plug-in list file is a process. UI Platform system, so the interface must be involved; otherwise, use cases should be avoided to describe the interface)

This book is still under exploration and will be shared with you in the future. If you have any thoughts on this book or use case, do you have any questions?