Sparx Systems Forum
Enterprise Architect => Uml Process => Topic started by: Legacy_Code on June 14, 2005, 07:50:46 am
-
What is the use case "notation" and how do we represent it?What does it containt?
-
Do you mean the use case diagram?
Use cases are a technique for articulating functional (and other) requirements from the perspective of an actor and that actor's interaction with the system.
Use Case diagrams present a graphical representation of the problem domain. They display the boundary of the solution, and shows how the actors interact with the use cases supported by that solution. It also can be used to display relationships between use cases and between actors.
A Use Case is a group of related requirements that combine to bring value to an Actor. The Use Case is modeled as an Oval with the name of the use case within or below the oval. Each Use Case is given an unique name. The oval represents the complete Use Case, including the main scenario and all alternative and exception scenarios.
A commonly used variant of the use case diagram for describing solution scope is the Business Use Case. A “Business” Use Case symbol has a diagonal line through the oval in order to differentiate it from the System Use Case. Business Use Cases typically model the behaviour of an organization from the perspective of its customers.
The notation of the Use Case Diagram is defined in UML 2.0 standard. A full description of this standard is maintained by the Object Management Group and can be found at http://www.uml.org.
-
hi,
The meaning terms are "Uses" and "Extends". i'm afarid it's not "Include"! :-/
-
hi,
The meaning terms are "Uses" and "Extends". i'm afarid it's not "Include"! :-/
"Uses" and "Extends" (and "Includes") were supported by early versions of UML. "Uses" and "Includes" have both been replaced by "Include"; "Extends" has been replaced by "Extend".