Use case modeling is simply an answer to 'What do the users (customers) want'. So what is use case? What is use case diagram and is use case modeling simple or powerful? Some people believe that use case diagram is so powerful that can represent many different aspects of a software, from describing system requirements to modeling the internal behaviors of the system. Another misunderstanding is just opposite to the first one. One is that, use case diagram is too simple, as it does not explain anything important and it is not worth drawing. There are two common misunderstanding about use case modeling or UML use case diagram. Use case diagrams belong to the family of behavioral diagrams.ġ0 Tips to Create Professional Use Case Diagram It does not show the order in which steps are performed to achieve the goals of each use case.It only summarizes some of the relationships between use cases, actors, and systems.It is an effective technique for communicating system behavior in the user's terms by specifying all externally visible system behavior.Ī use case diagram does not show the detail of the use cases: Use case modeling helps us to design a system from the user's perspective. Use cases once specified can be denoted both textual and visual representation (such as UML). A use case represents a high level business goal to be achieved by someone, some parties, or some sub-systems through interacting with a system, which can be the system under developed, or the system to maintain, depends on the nature of your software project. The identification of use cases helps define system scope, ensuring that the requirements to be found will all be aligned with the business values, needs and strategy. A use case is a tool for identifying the business goals of a system.

Online tool use case diagram