Use Case DiagramThe use case model captures the requirements of a system. Use cases are a means of communicating with users and other stakeholders what the system is intended to do.
Basic Use Case Diagram Symbols and NotationsSystemDraw your system's boundaries using a rectangle that contains use cases. Place actors outside the system's boundaries.
Use CaseDraw use cases using ovals. Label with ovals with verbs that represent the system's functions.
ActorsActors are the users of a system. When one system is the actor of another system, label the actor system with the actor stereotype.
RelationshipsIllustrate relationships between an actor and a use case with a simple line. For relationships among use cases, use arrows labeled either "uses" or "extends." A "uses" relationship indicates that one use case is needed by another in order to perform a task. An "extends" relationship indicates alternative options under a certain use case.
AssociationAn association specifies a semantic relationship that can occur between typed instances. It has at least two ends represented by properties, each of which is connected to the type of the end. More than one end of the association may have the same type.
CollaborationA collaboration is represented as a kind of classifier and defines a set of cooperating entities to be played by its roles, as well as a set of connectors that define communication paths between the participating instances. The cooperating entities are the properties of the collaboration.
DependencyA dependency is a relationship that signifies that a single or a set of model elements requires other model elements for their specification or implementation. This means that the complete semantics of the depending elements is either semantically or structurally dependent on the definition of the supplier elements.
ExtendThis relationship specifies that the behavior of a use case may be extended by the behavior of another use case. The extension takes place at one or more specific extension points defined in the extended use case. Note, however, that the extended use case is defined independently of the extending use case and is meaningful independently of the extending use case. On the other hand, the extending use case typically defines behavior that may not necessarily be meaningful by itself. instead, the extending use case defines a set of modular behavior increments that augment an execution of the extended use case under specific conditions.
IncludeInclude is a Directed Relationship between two use cases, implying that the behavior of the included use case is inserted into the behavior of the including use case. It is also a kind of Named Element so that it can have a name in the context of its owning use case. The including use case may only depend on the result of the included use case. This value is obtained as a result of the execution of the included use case.
GeneralizationA generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, specific classifier inherits the features of the more general classifier.
NoteA note (comment) gives the ability to attach various remarks to elements. A comment carries no semantic force, but may contain information that is useful to a modeler.
|
Online Classes through Skype and Team ViewerBook: Google Map API |