Use Case View Summary
This text is translated from Mark Priestley "Practical Object-Oriented Design With UML", it is a summary of the use case map, add my own understanding and memory, and I hope to help everyone. Interested friends contact me to discuss, learn together, and improve together. My email: kenli2000@163.com.
l Use the example view (Use Cases). Actors describe the roles that the user can play during and system interaction. Use examples describe the functionality of the system to the ACTORS.
The use case defines a particular type of transaction between users and systems. An example of a particular type of interaction, or an instance of an example can be described in Scenarios. UML does not give the formal definition of use cases and scenes.
l Scene can be defined as a statement of the basic event occurrence process described by the use example, and states the abnormal conditions that may occur.
l Use the example (USE Case Diagram) to participate in the ACTORs and Conditions participating in the system. There is an Actor and a condition that exists in the case. This actor is involved in this use.
L-use cases and use cases, there is a general relationship between the Actor and Actor (similar to the superclass, inheritance) between class CLASS, that is, a certain example or actor is another special case.
l There is also this "include" relationship between the use case, that is, one use case can contain another one. Similar to function calls, this provides a mechanism for reuse of the use case.
Another relationship between the use case "Extend" runs a use case to provide an optional function. This relationship is defined by defining the extension and when performing what feature is performed. This information is optional in the example diagram.
l A use case or a scene implementation describes a structure that enables this use case (or scene) function, interactive object.
l Sequence Diagram and Collaboration Diagram Draw a message involved in an object in an interaction and the intermittently transmitted messages, which can describe an implementation of a use case.
The translation is here, I want to explain my understanding to prevent everyone from watching.
Use case view is the first step in demand to ultimate implementation, the target system needs to have potential or obvious functions, with those target users, these things are still not completed, and next should be implemented The function is further analyzed that those use cases are actually one, and there are those relationships between the use cases, as the general relationships, extended relationships, etc. listed above. Of course this is also applicable to the Actor. Single use case map is sometimes too simple, it is not enough to describe a detailed situation of a certain example. This is a scenario must not be less, using text to describe the case, normal process, and abnormal abnormal conditions, very useful. Of course, further analysis can be made to start drawing a sequence diagram and collaboration diagram of each use case.
