This practice reinforces the fundamental notion that a system must conform to the needs of the users, instead of your users conforming to the system. In this article, we show common mistakes, and then explain how to correct them.
Use cases drive the dynamic model and, by extension, the entire development effort.
The diagram portrays the essence of a streamlined approach to software development that includes a minimal set of UML diagrams and some valuable techniques that take you from use cases to code quickly and efficiently. The task of building use cases for your new system is based on immediately identifying as many as you can, and then establishing a continuous loop of writing and refining the text that describes them. Along the way, you will discover new use cases, and also factor out commonality in usage. The connection between each use case and a distinct section of your user guide should be obvious. It reinforces the fundamental notion that you are designing a system that will conform to the viewpoints of the users.