Snippets (text quotes and extracts from authoritative sources)

A Snippet is a short quote or extract (typically a phrase, a sentence, or at most a few sentences) from an authoritative source document such as a specification, technical manual, or design manual. Throughout this site, content is often related to supporting Snippets and each Snippet page links back to the content pages that reference it! The Snippet and Note concepts are very closely related and they support each other.

The Snippet concept is also at the heart of the Parsing Analysis recipe for UML® and SysML®

Kind Snippet quote/extract Source UML keywords SysML keywords Keywords
INFO Each link may be realized by something as simple as a pointer or by something as complex as a network connection, and may represent the possibility of instances being able to communicate because their identities are known by virtue of being passed in ... Unified Modeling Language 2.5.1 Connector, link, instance, StructuredClassifier, roles
INFO A Connector specifies links ... between two or more instances playing owned or inherited roles within a StructuredClassifier. Unified Modeling Language 2.5.1 Connector, link, instance, StructuredClassifier, roles
INFO A Usage is a Dependency in which the client Element requires the supplier Element (or set of Elements) for its full implementation or operation. Unified Modeling Language 2.5.1 Usage, Dependency, Dependency::client, Dependency::supplier, DirectedRelationship, NamedElement
INFO This means that the complete semantics of the client Element(s) are either semantically or structurally dependent on the definition of the supplier Element(s). Unified Modeling Language 2.5.1 Dependency, Dependency::client, Dependency::supplier, DirectedRelationship, NamedElement
INFO A Dependency is a Relationship that signifies that a single model Element or a set of model Elements requires other model Elements for their specification or implementation. Unified Modeling Language 2.5.1 Dependency, Dependency::client, Dependency::supplier, DirectedRelationship, NamedElement
INFO If a Property has a specified default, and the Property redefines another Property with a specified default, then the redefining Property’s default is used in place of the more general default from the redefined Property. Unified Modeling Language 2.5.1 Property, Property::redefinedProperty, Property::defaultValue
INFO A derived Property may redefine one which is not derived. An implementation shall ensure that the constraints implied by the derivation are maintained if the Property is updated. Unified Modeling Language 2.5.1 Property, Property::redefinedProperty, Property::isDerived
INFO Property is indirectly a kind of RedefinableElement, so Properties may be redefined. The name and visibility of a Property are not required to match those of any Property it redefines. Unified Modeling Language 2.5.1 Property, Property::redefinedProperty, NamedElement, NamedElement::name, VisibilityKind, NamedElement::visibility, RedefinableElement
NOTATION Members that are inherited by a Classifier may be shown on a diagram of that Classifier by prepending a caret ’^’ symbol to the textual representation that would be shown if the member were not inherited. Unified Modeling Language 2.5.1 Classifier, Generalization
NOTATION Constraint properties and their parameters also have their own notations ... OMG Systems Modeling Language (SysML) 1.6 Property, Port constraint property, MD:ConstraintProperty
NOTATION Ports are special cases of properties, and have a variety of notations ... OMG Systems Modeling Language (SysML) 1.6 Property, Port part property, MD:PartProperty
NOTATION A reference property is shown by a dashed-outline box, consistent with UML. OMG Systems Modeling Language (SysML) 1.6 Property reference property, MD:ReferenceProperty
NOTATION A part or value property is always shown on an internal block diagram with a solid-outline box. OMG Systems Modeling Language (SysML) 1.6 Property part property, value property, MD:PartProperty, MD:ValueProperty
INFO Four general categories of properties of blocks are recognized in SysML: parts, references, value properties, and constraint properties. OMG Systems Modeling Language (SysML) 1.6 Property part property, value property, constraint property, reference property, MD:PartProperty, MD:ConstraintProperty, MD:ReferenceProperty, MD:ValueProperty
NOTATION A compartment with the label “structure” may appear as part of a block definition to show connectors and other internal structure elements for the block being defined. This compartment may contain any of the graphical elements of an internal block diagram OMG Systems Modeling Language (SysML) 1.6 compartment, internal structure compartment, Connector Block, SysML Internal Block Diagram, internal structure
INFO Properties of any type may be shown in a "properties" compartment or in additional compartments with user-defined labels. OMG Systems Modeling Language (SysML) 1.6 Property, compartment Block, properties compartment
INFO Part, reference, value, and constraint properties may be shown in block definition compartments with the labels "parts," "references," "values," and "constraints" respectively. OMG Systems Modeling Language (SysML) 1.6 Property Block, value property, MD:ValueProperty, reference property, MD:ReferenceProperty, constraint property, MD:ConstraintProperty, parts compartment, references compartment, values compartment, constraints compartment
INFO A property typed by a SysML ValueType is classified as a value property, and always has composite aggregation. OMG Systems Modeling Language (SysML) 1.6 Property, AggregationKind, Property::aggregation, AggregationKind::composite Block, value property, MD:ValueProperty
INFO A property typed by a SysML Block that has composite aggregation is classified as a part property, except for the special case of a constraint property ... OMG Systems Modeling Language (SysML) 1.6 Property, AggregationKind, Property::aggregation, AggregationKind::composite Block, part property, MD:PartProperty
INFO A property typed by a Block that does not have composite aggregation is classified as a reference property. OMG Systems Modeling Language (SysML) 1.7beta1 Property, AggregationKind, Property::aggregation, AggregationKind::shared, AggregationKind::none Block, part property, reference property, shared property, MD:SharedProperty, MD:ReferenceProperty, MD:BlockProperty
INFO Constraint properties are further defined in Clause 10. A port is another category of property, as further defined in Section 9. OMG Systems Modeling Language (SysML) 1.6 Property, AggregationKind, Property::aggregation, AggregationKind::composite, Port Block, MD:ConstraintProperty, constraint property
INFO SysML establishes four basic classifications of properties belonging to a SysML Block or ValueType. OMG Systems Modeling Language (SysML) 1.6 Property Block, ValueType
INFO Classifier::isAbstract : Boolean [1..1] If true, the Classifier can only be instantiated by instantiating one of its specializations. An abstract Classifier is intended to be used by other Classifiers e.g., as the target of Associations or Generalizations Unified Modeling Language 2.5.1 Classifier::isAbstract, Classifier, Class
INFO SysML blocks can be used throughout all phases of system specification and design, and can be applied to many different kinds of systems. OMG Systems Modeling Language (SysML) 1.6 Block systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
NOTATION SysML Blocks also extend the capabilities of UML classes and connectors with reusable forms of constraints, multi-level nesting of connector ends, participant properties for composite association classes, and connector properties. OMG Systems Modeling Language (SysML) 1.6 StructuredClassifier, Class, Connector Block, UML4SysML, NestedConnectorEnd, nested Property, ParticipantProperty, ConnectorProperty systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
NOTATION SysML blocks always include an ability to define internal connectors, regardless of whether this capability is needed for a particular block. OMG Systems Modeling Language (SysML) 1.6 StructuredClassifier, Class, Connector, internal Connector Block, UML4SysML systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
NOTATION SysML blocks are based on UML classes as extended by UML composite structures. Some capabilities available for UML classes, such as more specialized forms of associations, have been excluded from SysML blocks to simplify the language. OMG Systems Modeling Language (SysML) 1.6 StructuredClassifier, Class, Association Block, UML4SysML systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
NOTATION Blocks may also specify operations or other features that describe the behavior of a system OMG Systems Modeling Language (SysML) 1.6 Operation, BehavioralFeature, Activity, Interaction, StateMachine, Behavior, operations compartment Block systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
NOTATION SysML also allows each usage to define context-specific values and constraints associated with the individual usage, such as 25 psi for the front tires and 30 psi for the rear tires. OMG Systems Modeling Language (SysML) 1.6 Property, part, Property::defaultValue, Constraint Block, block property, part property, initial values, context-specific values, initialValues compartment systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
NOTATION For example, a block that represents the definition of a wheel can be used in different ways. The front wheel and rear wheel can represent different usages of the same wheel definition. OMG Systems Modeling Language (SysML) 1.6 Property, TypedElement, TypedElement::type, part Block, block property, part property systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
NOTATION A part belonging to a block, for example, may be typed by another block. The part defines a local usage of its defining block within the specific context to which the part belongs. OMG Systems Modeling Language (SysML) 1.6 Property, TypedElement, TypedElement::type, part Block, block property, part property systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
NOTATION A property can represent a role or usage in the context of its enclosing block. A property has a type that supplies its definition. OMG Systems Modeling Language (SysML) 1.6 Property, TypedElement, TypedElement::type Block, block property, value property, constraint property, part property, reference property systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
NOTATION Various notations for properties are available to distinguish these specialized kinds of properties on an internal block diagram. OMG Systems Modeling Language (SysML) 1.6 Property Block, block property, value property, SysML Internal Block Diagram systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO Constraint Properties are a special class of property used to constrain other properties of blocks... OMG Systems Modeling Language (SysML) 1.6 Property, part, Constraint Block, block property, constraint property, ConstraintBlock systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO Ports are a special class of property used to specify allowable types of interactions between blocks ... OMG Systems Modeling Language (SysML) 1.6 Property, Port, ports compartment Block, block property systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO A block can include properties to specify its values, parts, and references to other blocks. OMG Systems Modeling Language (SysML) 1.6 Property, part Block, value property, part property, reference property, MD:ValueProperty, MD:PartProperty, MD:ReferenceProperty, values compartment, parts compartment, references compartment systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO The Internal Block Diagram in SysML captures the internal structure of a block in terms of properties and connectors between properties. OMG Systems Modeling Language (SysML) 1.6 Diagram, Property Block, SysML Internal Block Diagram, internal structure systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO It captures the definition of blocks in terms of properties and operations, and relationships such as a system hierarchy or a system classification tree OMG Systems Modeling Language (SysML) 1.6 Diagram, Feature, Relationship, Association, Generalization, part, Property, Operation Block, SysML Block Definition Diagram systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO The Block Definition Diagram in SysML defines features of blocks and relationships between blocks such as associations, generalizations, and dependencies. OMG Systems Modeling Language (SysML) 1.6 Diagram, Feature, Relationship, Association, Dependency, Generalization Block, SysML Block Definition Diagram systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO Parts in these systems may interact by many different means, such as software operations, discrete state transitions, flows of inputs and outputs, or continuous interactions. OMG Systems Modeling Language (SysML) 1.6 part, Property, State, Transition, ParameterDirectionKind::in, ParameterDirectionKind::out, ParameterDirectionKind::inout, ParameterDirectionKind::return Block, part property, flow, Continuous, «continuous», FlowDirectionKind, FlowDirectionKind::in, FlowDirectionKind::inout, ActivityAllocatePartition, Discrete, «discrete» systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language, logical decomposition, physical decomposition, functional decomposition, software, hardware, human, human resource
INFO These include modeling either the logical or physical decomposition of a system, and the specification of software, hardware, or human elements. OMG Systems Modeling Language (SysML) 1.6 Block systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language, logical decomposition, physical decomposition, functional decomposition, software, hardware, human, human resource
INFO The specific kinds of components, the kinds of connections between them, and the way these elements combine to define the total system can all be selected according to the goals of a particular system model. OMG Systems Modeling Language (SysML) 1.6 Property, part, Connector Block, part property, reference property, shared property, block property systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO Blocks provide a general-purpose capability to model systems as trees of modular components. OMG Systems Modeling Language (SysML) 1.6 Property, part Block, part property, reference property, shared property, block property systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO Each block defines a collection of features to describe a system or other element of interest. These may include both structural and behavioral features, such as properties and operations, to represent the state of the system and behavior ... OMG Systems Modeling Language (SysML) 1.6 Feature, StructuralFeature, BehavioralFeature, Property, Operation, Behavior Block, «system» systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
INFO Blocks are modular units of system description. OMG Systems Modeling Language (SysML) 1.6 Block systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language
NOTATION A compartment with the label “receptions” may appear as part of a block definition to show signal receptions. The “«signal»” keyword is optional in this compartment. OMG Systems Modeling Language (SysML) 1.6 receptions compartment, «signal», Signal, Reception block compartment
INFO Although SysML indirectly imports the UML 2 PrimitiveTypes library ... due to the transitivity of package import, SysML provides a PrimitiveValueTypes model library that systems engineers can extend via SysML’s ValueType stereotype. OMG Systems Modeling Language (SysML) 1.6 ModelLibrary ValueType, PrimitiveValueType
INFO Stakeholder::concernList : Comment [0..*] OMG Systems Modeling Language (SysML) 1.6 Comment Stakeholder, Stakeholder::concernList
INFO Stakeholder::/concern : String [0..*] (derived) OMG Systems Modeling Language (SysML) 1.6 String Stakeholder, Stakeholder::/concern
INFO A Conform relationship is a generalization between a view and a viewpoint. The view conforms to the specified rules and conventions detailed in the viewpoint. When this is done, the view is said to conform to the viewpoint. OMG Systems Modeling Language (SysML) 1.6 Generalization, Extension Conform, View, Viewpoint
CONSTRAINT Viewpoint::2_create_view_operation The property ownedOperation shall include at least one operation named "View" with the UML Create stereotype applied. OMG Systems Modeling Language (SysML) 1.6 «Create», constructor, Operation, Class::ownedOperation Viewpoint, View
CONSTRAINT Viewpoint::1_method_derived_from_create_operations The derived values of the method attribute shall be the names of the methods of the operations stereotyped by the UML Create stereotype on the classifier stereotyped by Viewpoint. OMG Systems Modeling Language (SysML) 1.6 «Create», constructor, Operation, BehavioralFeature::method Viewpoint, Viewpoint::/method
INFO Viewpoint::stakeholder : Stakeholder [0..*] Set of stakeholders whose concerns are to be addressed by the viewpoint. OMG Systems Modeling Language (SysML) 1.6 Viewpoint, Viewpoint::stakeholder, Stakeholder, Stakeholder::/concern, Viewpoint::/concern
INFO Viewpoint::purpose : String [1] The purpose addresses the stakeholder concerns. OMG Systems Modeling Language (SysML) 1.6 String Viewpoint, Viewpoint::purpose, Stakeholder, Viewpoint::/concern, Stakeholder::/concern
INFO Viewpoint::presentation : String [0..*] The specifications prescribed for formatting and styling the view. OMG Systems Modeling Language (SysML) 1.6 String Viewpoint, Viewpoint::presentation, View
INFO Viewpoint::/method : Behavior [0..*] The behavior is derived from the method of the operation with the Create stereotype. (derived) OMG Systems Modeling Language (SysML) 1.6 Behavior, «Create», constructor, Operation, BehavioralFeature::method Viewpoint, Viewpoint::/method URI, URL
INFO Viewpoint::language : String [0..*] The languages used to express the models that represent content which is represented by the view. The language specification such as its metamodel, profile, or other language specification is referred to by its URI. OMG Systems Modeling Language (SysML) 1.6 Viewpoint, Viewpoint::language URI, URL
INFO Viewpoint::concernList : Comment [0..*] The interests of the stakeholders addressed by this viewpoint. OMG Systems Modeling Language (SysML) 1.6 Comment::body Viewpoint, Stakeholder, Stakeholder::/concern, Viewpoint::/concern, Stakeholder::concernList, Viewpoint::concernList
INFO Viewpoint::/concern : String [0..*] The interest of the stakeholders displayed as the body of the comments from concernList. (derived) OMG Systems Modeling Language (SysML) 1.6 Comment::body Viewpoint, Stakeholder, Stakeholder::/concern, Viewpoint::/concern, Stakeholder::concernList, Viewpoint::concernList
INFO For example, the security viewpoint may require the security requirements, security functional and physical architecture, and security test cases. OMG Systems Modeling Language (SysML) 1.6 Viewpoint, Stakeholder, Stakeholder::/concern, Viewpoint::/concern, View
INFO A Viewpoint is a specification of the conventions and rules for constructing and using a view for the purpose of addressing a set of stakeholder concerns. They specify the elements expected to be represented in the view... OMG Systems Modeling Language (SysML) 1.6 Viewpoint, Stakeholder, Stakeholder::/concern, Viewpoint::/concern, View
INFO Just like a Class, a Stereotype may have Properties, which have traditionally been referred to as Tag Definitions. When a Stereotype is applied to a model element, the values of the Properties have traditionally been referred to as tagged values. Unified Modeling Language 2.5.1 Stereotype, stereotype Property, tagged value, tag definition
CONSTRAINT A stereotype must be contained, directly or indirectly, in a profile. Unified Modeling Language 2.5.1 Stereotype, Profile
INFO A Comment is shown as a rectangle with the upper right corner bent (this is also known as a “note symbol”). The rectangle contains the body of the Comment. The connection to each annotatedElement is shown by a separate dashed line. Unified Modeling Language 2.5.1 Comment, Comment::annotatedElement, Comment::body, MD:anchor
INFO ElementGroup::/size : Integer [1] Number of members in the group. Derived. (derived) OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup, ElementGroup::/size, ElementGroup::/member
INFO ElementGroup::orderedMember : Element [0..*] Organize member according to an arbitrary order. Optional. (subsets: ElementGroup::member) OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup, ElementGroup::orderedMember
INFO ElementGroup::name : String [1] Name of the element group OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup, ElementGroup::name
INFO ElementGroup::/member : Element [0..*] Set specifying the members of the group. Derived from Comment::annotatedElement. (derived) OMG Systems Modeling Language (SysML) 1.6 Comment, Comment::annotatedElement ElementGroup, ElementGroup::/member
INFO ElementGroup::/criterion : String [0..1] Specifies the rationale for being member of the group. Adding an element to the group asserts that the criterion applies to this element. Derived from Comment::body. (derived) OMG Systems Modeling Language (SysML) 1.6 Comment, Comment::body ElementGroup, ElementGroup::/criterion, ElementGroup::/member
INFO Element groups can be members of other element groups, but this does not imply that members of the first are members of the second. OMG Systems Modeling Language (SysML) 1.6 Comment, Comment::annotatedElement ElementGroup, ElementGroup::/member
INFO The elements in a group are identified by the modeler, as opposed to being the result of a query, as in views. OMG Systems Modeling Language (SysML) 1.6 Comment, Comment::annotatedElement ElementGroup, ElementGroup::/member
INFO Element groups do not own their elements and thus an element can participate in an unlimited number of groups. OMG Systems Modeling Language (SysML) 1.6 Comment, Comment::annotatedElement ElementGroup, ElementGroup::/member
INFO Grouped elements are the annotated elements of the comment to which the stereotype is applied. This has several implications: OMG Systems Modeling Language (SysML) 1.6 Comment, Comment::annotatedElement ElementGroup, ElementGroup::/member
INFO ElementGroups appear in diagrams as comments, and properties of the stereotype appear in the notation for stereotype properties. OMG Systems Modeling Language (SysML) 1.6 Comment, Stereotype, stereotype Property ElementGroup
INFO Optionally, members of an element group can be ordered using its orderedMember property. OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup, ElementGroup::/member, ElementGroup::orderedMember
INFO The criterion for membership in an element group is specified by the body of the comment the stereotype is applied to. By grouping elements, the modeler asserts that the criterion of the group applies to the member. OMG Systems Modeling Language (SysML) 1.6 Comment, Comment::body ElementGroup, ElementGroup::/member, ElementGroup::/criterion
INFO Element groups are named using the name property. OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup, ElementGroup::name
INFO The semantics of ElementGroup is modeler-defined. In particular, the body text is not restricted. It can describe the grouped elements as well as elements or values related to the grouped elements. OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup
INFO For example, it can group elements that are associated with a particular release of the model, have a certain risk level, or are associated with a legacy design. OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup
INFO The ElementGroup stereotype provides a lightweight mechanism for grouping various and possibly heterogeneous model elements by extending the capability of comments to refer to multiple annotated elements. OMG Systems Modeling Language (SysML) 1.6 Comment ElementGroup
INFO AllocateActivityPartition::2_not_uml_semantics ... Classifiers or Properties represented by an «AllocateActivityPartition» do not have any direct responsibility for invoking behavior depicted within the partition boundaries. ... OMG Systems Modeling Language (SysML) 1.6 ActivityPartition AllocateActivityPartition, behavior allocation functional allocation
INFO AllocateActivityPartition::2_not_uml_semantics The «AllocateActivityPartition» shall maintain the constraints, but not the semantics, of the UML::ActivityPartition. OMG Systems Modeling Language (SysML) 1.6 ActivityPartition AllocateActivityPartition, behavior allocation functional allocation
CONSTRAINT AllocateActivityPartition::1_actions_on_client_ends An Action appearing in an "AllocateActivityPartition" shall be the /client (from) end of an "allocate" dependency. The element that represents the "AllocateActivityPartition" shall be the /supplier ... OMG Systems Modeling Language (SysML) 1.6 Dependency::client, Dependency::supplier AllocateActivityPartition, Allocate
INFO A typical example is the allocation of activities to blocks (e.g., functions to components) OMG Systems Modeling Language (SysML) 1.6 Allocate, behavior allocation functional allocation
INFO ... does not try to limit the use of the term “allocation,” but provides a basic capability to support allocation in the broadest sense. It does include some specific subclasses of allocation for allocating behavior, structure, and flows. OMG Systems Modeling Language (SysML) 1.6 Allocate, behavior allocation functional allocation, structural allocation, flow allocation
INFO The allocation relationship can provide an effective means for navigating the model by establishing cross relationships, and ensuring the various parts of the model are properly integrated. OMG Systems Modeling Language (SysML) 1.6 Allocate
INFO System modelers often associate various elements in a user model in abstract, preliminary, and sometimes tentative ways. Allocations can be used early in the design as a precursor to more detailed rigorous specifications and implementations. OMG Systems Modeling Language (SysML) 1.6 Allocate
INFO The concept of “allocation” requires flexibility suitable for abstract system specification, rather than a particular constrained method of system or software design. OMG Systems Modeling Language (SysML) 1.6 Allocate
INFO Allocation is the term used by systems engineers to denote the organized cross-association (mapping) of elements within the various structures or hierarchies of a user model. OMG Systems Modeling Language (SysML) 1.6 Allocate
INFO UseCases need not be owned by their subject. Unified Modeling Language 2.5.1 UseCase, UseCase::subject
INFO A UseCase may be owned either by a Package or by a Classifier. Although the owning Classifier typically represents a subject to which the owned UseCases apply, this is not necessarily the case ... Unified Modeling Language 2.5.1 UseCase, UseCase::subject, Behavior, BehavioredClassifier, Package, Classifier
CONSTRAINT, INFO Two UseCases specifying the same subject cannot be associated as each of them individually describes a complete usage of the subject. Unified Modeling Language 2.5.1 UseCase, UseCase::subject, Behavior, BehavioredClassifier, Association
INFO UseCases may have associated Actors, which describe how an instance of the Classifier realizing the UseCase and a user playing one of the roles of the Actor interact. Unified Modeling Language 2.5.1 UseCase, UseCase::subject, Behavior, BehavioredClassifier, Actor, Association
INFO It may also be described indirectly through a Collaboration that uses the UseCase and its Actors as the Classifiers that type its parts. Unified Modeling Language 2.5.1 UseCase, UseCase::subject, Behavior, BehavioredClassifier, Collaboration, Actor, part, Classifier
INFO The behaviors of a UseCase can be described by a set of Behaviors (through its ownedBehavior relationship), such as Interactions, Activities, and StateMachines, as well as by pre-conditions, post-conditions and natural language text where appropriate. Unified Modeling Language 2.5.1 UseCase, UseCase::subject, Behavior, BehavioredClassifier, BehavioredClassifier::ownedBehavior, Interaction, StateMachine, Behavior::precondition, Behavior::postcondition
INFO Moreover, the UseCases may also state the requirements the specified subject poses on its environment by defining how the Actors should interact with the subject so that it will be able to perform its services. Unified Modeling Language 2.5.1 UseCase, UseCase::subject external requirement
INFO UseCases can be used both for specification of the (external) requirements on a subject and for the specification of the functionality offered by a subject. Unified Modeling Language 2.5.1 UseCase, UseCase::subject functional requirement, external requirement
INFO It is deemed complete if, after its execution, the subject will be in a state in which no further inputs or actions are expected and the UseCase can be initiated again, or in an error state. Unified Modeling Language 2.5.1 UseCase, Behavior, BehavioredClassifier, UseCase::subject error handling
INFO Each UseCase specifies a unit of useful functionality that the subject provides to its users (i.e., a specific way of interacting with the subject). This functionality must always be completed for the UseCase to complete. Unified Modeling Language 2.5.1 UseCase, Behavior, BehavioredClassifier, UseCase::subject
INFO A subject of a UseCase could be a system or any other element that may have behavior, such as a Component or Class. Unified Modeling Language 2.5.1 UseCase, Behavior, BehavioredClassifier, Class, Component, UseCase::subject