|
A use case diagram is a type of behavioral diagram defined by the Unified Modeling Language (UML). Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals—represented as use cases—and any dependencies between those use cases. Image File history File links Broom_icon. ...
In the field of software engineering, the Unified Modeling Language (UML) is a standardized specification language for object modeling. ...
In the Unified Modeling Language (UML), an actor is something or someone who supplies a stimulus to the system. ...
A use case is a technique used in software and systems engineering to capture the functional requirements of a system. ...
While SysML uses the same notation as UML for use cases, system engineers model at the system or systems-of-systems level. SysML, or Systems Modeling Language, is a general-purpose systems engineering modeling language. ...
Systems engineering (or systems design engineering) as a field originated around the time of World War II. Large or highly complex engineering projects, such as the development of a new airliner or warship, are often decomposed into stages and managed throughout the entire life of the product or system. ...
UML Use Case Diagram OMG's UML standard defines a graphical notation for diagramming use cases, but no format for describing use cases. While the graphical notation and descriptions are important, they are documentation of the use case—a purpose that the actor can use the system for. Object Management Group (OMG) is a consortium, originally aimed at setting standards for distributed object-oriented systems, and is now focused on modeling (programs, systems and business processes) and model-based standards in some 20 vertical markets. ...
In the field of software engineering, the Unified Modeling Language (UML) is a standardized specification language for object modeling. ...
A use case is a technique used in software and systems engineering to capture the functional requirements of a system. ...
In the Unified Modeling Language (UML), an actor is something or someone who supplies a stimulus to the system. ...
The true value of a use case lies in two areas:
- The written description of system behavior regarding a business task or requirement. This description focuses on the value provided by the system to external entities such as human users or other systems.
- The position or context of the use case among other use cases. As an organizing mechanism, a set of consistent, coherent use cases promotes a useful picture of system behavior, a common understanding between the customer/owner/user and the development team.
 The diagram on the right describes the functionality of a simplistic Restaurant System. Use cases are represented by ovals and the actors are represented by stick figures. The Patron actor can Eat Food, Pay for Food, or Drink Wine. Only the Chef actor can Prepare Food. Note that both the Patron and the Cashier are involved in the Pay for Food use case. The box defines the boundaries of the Restaurant System, i.e., the use cases shown are part of the system being modelled, the actors are not. Image File history File links Restaurant-UML-UC.png Summary Sample UML use case diagram Licensing File history Legend: (cur) = this is the current file, (del) = delete this old version, (rev) = revert to this old version. ...
A use case is a technique used in software and systems engineering to capture the functional requirements of a system. ...
In the Unified Modeling Language (UML), an actor is something or someone who supplies a stimulus to the system. ...
Interaction among actors is not shown on the use case diagram. If this interaction is essential to a coherent description of the desired behavior, perhaps the system or use case boundaries should be re-examined. Alternatively, interaction among actors can be part of the assumptions used in the use case.
Actor Generalization
The only relationship allowed between actors is generalization. This is useful in defining overlapping roles between actors. The notation is a solid line ending in a hollow triangle drawn from the specialized to the more general actor.
Image File history File links No higher resolution available. ...
Use Case Relationships Three relationships among use cases are supported by the UML standard, which describes graphical notation for these relationships. Image File history File links No higher resolution available. ...
Include In one form of interaction, a given use case must include another. The first use case often depends on the outcome of the included use case. This is useful for extracting truly common behaviors from multiple use cases into a single description. The notation is a dashed arrow from the including to the included use case, with the label "«include»". This usage resembles a macro expansion where the included use case behavior is placed inline in the base use case behavior. There are no parameters or return values.
Extend In another form of interaction, a given use case (the extension) may extend another. This relationship indicates that the behavior of the extension use case may be inserted in the extended use case under some conditions. The notation is a dashed arrow from the extension to the extended use case, with the label «extend». This can be useful for dealing with special cases, or in accommodating new requirements during system maintenance and extension.
To make the points at which extension may occur explicit extension points may be defined in a use case which are listed in a compartment below the use case name.
Generalization In the third form of relationship among use cases, a generalization/specialization relationship exists. A given use case may be a specialized form of an existing use case. The notation is a solid line ending in a hollow triangle drawn from the specialized to the more general use case. This resembles the object-oriented concept of sub-classing, in practice it can be both useful and effective to factor common behaviors, constraints and assumptions to the general use case, describe them once, and deal same as except details in the specialized cases.
External links Unified Modeling Language (UML) (category) ( view • talk • edit )
| Background
| | Organisations: Object Management Group (OMG) • UML Partners In the field of software engineering, the Unified Modeling Language (UML) is a standardized specification language for object modeling. ...
Object Management Group (OMG) is a consortium, originally aimed at setting standards for distributed object-oriented systems, and is now focused on modeling (programs, systems and business processes) and model-based standards in some 20 vertical markets. ...
Persons: Grady Booch • Ivar Jacobson • James Rumbaugh Grady Booch (born February 27, 1955) is a software designer, a software methodologist and a design pattern enthusiast. ...
Ivar Hjalmar Jacobson (born in Ystad, Sweden, on September 2, 1939) is a Swedish computer scientist. ...
Dr. James Rumbaugh is a computer scientist and object methodologist who is best known for his work in creating the Object Modeling Technique (OMT) and the Unified Modeling Language (UML). ...
| Concepts
| | Object oriented: programming (OOP) • analysis and design (OOAD) Object-oriented analysis and design (OOAD) is often part of the development of large scale systems and programs often using the Unified Modeling Language (UML). ...
Structure: Actor • Attribute • Class • Component • Interface • Object • Package In the Unified Modeling Language (UML), an actor is something or someone who supplies a stimulus to the system. ...
In computing, attributes are entities that define properties of objects, elements, or files. ...
In object-oriented programming, a class is a programming language construct used to group related fields and methods. ...
In the Unified Modeling Language, a component diagram depicts how a software system is split up into physical components and shows the dependencies among these components. ...
An interface defines the communication boundary between two entities, such as a piece of software, a hardware device, or a user. ...
In strictly mathematical branches of computer science the term object is used in a purely mathematical sense to refer to any thing. While this interpretation is useful in the discussion of abstract theory, it is not concrete enough to serve as a primitive datatype in the discussion of more concrete...
A package is a collection or grouping of related classes or classes with related functionality. ...
Behavior: Activity • Event • Message • Method • Operation • State • Use case Activity is a result of interaction between system and the actor. ...
An event is a notable occurrence at a particular point in time. ...
In computer science, message passing is a form of communication used in concurrent programming, parallel programming, object-oriented programming, and interprocess communication. ...
In object-oriented programming, the term method refers to a subroutine that is exclusively associated either with a class (called class methods, static methods, or factory methods) or with an object (called instance methods). ...
In information processing, a state is the complete set of properties (for example, its energy level, etc. ...
A use case is a technique used in software and systems engineering to capture the functional requirements of a system. ...
Relationships: Aggregation • Association • Composition • Dependency • Generalization (or Inheritance) Some factual claims in this article or section need to be verified. ...
In Object_oriented programming, Association defines a relationship between classes of objects which allows one object instance to cause another to perform an action on its behalf. ...
This article does not cite any references or sources. ...
In computer science, coupling or dependency is the degree to which each program module relies on each one of the other modules. ...
For the term in the context of mathematical logic, see Generalization (logic). ...
This article or section does not cite any references or sources. ...
Extensibility: Profile • Constraint • Stereotype • Tagged values A profile in the Unified Modeling Language provides a generic extension mechanism for building UML models in particular domains. ...
In the Unified Modeling Language, a stereotype is a name denoted with guillemets (not double angle brackets) that conveys a high level category, type, or meaning of an item. ...
Other concepts: Multiplicity • Role Hierarchy of UML 2. ...
| | Diagrams | | Structure diagrams
Class diagram • Component diagram • Composite structure diagram • Deployment diagram • Object diagram • Package diagram Hierarchy of UML 2. ...
In the Unified Modeling Language, a component diagram depicts how a software system is split up into physical components and shows the dependencies among these components. ...
A Unified Modeling Language (UML) composite structure diagram shows the internal structure of a class and the collaborations that this structure makes possible. ...
A sample deployment diagram. ...
A Unified Modeling Language (UML) object diagram shows a complete or partial view of the structure of a modeled system, at a specific point in time. ...
In the Unified Modeling Language, a package diagram depicts how a system is split up into logical groupings by showing the dependencies among these groupings. ...
| Behavior diagrams
Activity diagram • State Machine diagram • Use case diagram • Communication diagram • Interaction overview diagram • Sequence diagram • Timing diagram In the Unified Modeling Language, an activity diagram represents the business and operational step-by-step workflows of components in a system. ...
State diagrams are used to graphically represent finite state machines. ...
In the Unified Modeling Language (UML) 2. ...
Example of a UML 2 diagram The Message Sequence Chart technique has been incorporated into the Unified Modeling Language (UML) diagram under the name of Sequence Diagram. ...
Timing diagrams (UML 2. ...
| | Topics | | Compared to relational database model (ERD) • Glossary of UML terms • Systems Modeling Language (SysML) • UML colors: This article or section is not written in the formal tone expected of an encyclopedia article. ...
This glossary of Unified Modeling Language terms covers all versions of UML. Individual entries will point out any distinctions that exist between versions. ...
SysML, or Systems Modeling Language, is a general-purpose systems engineering modeling language. ...
UML color standards are a set of four colors associated with Unified Modeling Language (UML) diagrams. ...
| | Role | Moment, Interval | Description | Party, place, thing | | Tools(category) and Processes | | List of UML tools • Rational Unified Process (RUP) A UML tool is an application software that supports some or all parts of the processes or the creation of the artifacts described in the software industry standard Unified Modeling Language (UML), which is used in the field of software engineering. ...
This article lists Unified Modeling Language tools, classified by their proprietary or non-proprietary status. ...
The Rational Unified Process (RUP) is an iterative software development process created by the Rational Software Corporation, now a division of IBM. The RUP is an extensive refinement of the (generic) Unified Process. ...
| |
Feeds |
Contact