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 For example, in Figure 9-15 the connector to the output of the water heater has an item flow indicating distilled water is flowing, even though the out flow property of the water heater indicates it produces water. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow
INFO Item flows in internal block diagrams specify flows local to a block. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow
INFO The keyword «connector» before a property name indicates the property is stereotyped by ConnectorProperty. OMG Systems Modeling Language (SysML) 1.6 Connector, AssociationClass [DEPRECATED] ConnectorProperty, AssociationBlock, ParticipantProperty, «connector»
INFO A connector property can optionally be shown in an internal block diagram with a dotted line from the connector line to a rectangle notating the connector property. OMG Systems Modeling Language (SysML) 1.6 Connector, AssociationClass [DEPRECATED] ConnectorProperty, AssociationBlock, ParticipantProperty
INFO The values of a connector property are instances of the association block created due to the connector referred to by the connector property. OMG Systems Modeling Language (SysML) 1.6 Connector, AssociationClass [DEPRECATED] ConnectorProperty, AssociationBlock, ParticipantProperty
INFO These connectors specify instances of the association block created within the instances of the block that owns the connector. OMG Systems Modeling Language (SysML) 1.6 ConnectorProperty, Connector, AssociationClass AssociationBlock, ParticipantProperty
INFO Connectors can be typed by association classes that are stereotyped by Block (association blocks, see ParticipantProperty ... OMG Systems Modeling Language (SysML) 1.6 Connector, AssociationClass [DEPRECATED] ConnectorProperty, AssociationBlock, ParticipantProperty
EXAMPLE, INFO The lower connector shows its connector property explicitly, enabling the pipe it contains to be connected to a mounting bracket (the additional part and connector definitions are omitted for brevity). OMG Systems Modeling Language (SysML) 1.6 Connector AssociationBlock, SysML specification figure
EXAMPLE, INFO Figure 9-14 modifies Figure 9-9 to use Plumbing as a connector type within the Water Delivery association block. OMG Systems Modeling Language (SysML) 1.6 Connector AssociationBlock, SysML specification figure
EXAMPLE, INFO Figure 9-13 shows the internal structure for the Plumbing association block, which includes a pipe and two fittings (the additional part and connector definitions are omitted for brevity). OMG Systems Modeling Language (SysML) 1.6 Connector, part AssociationBlock, part property
EXAMPLE, INFO Figure 9-12 adds a Plumbing association block for the association between Spigot and Faucet Inlet in Figure 9-11. OMG Systems Modeling Language (SysML) 1.6 Association AssociationBlock
EXAMPLE, INFO The composite connector for Water Delivery is reused three times to establish connections between spigots on the water supply and the inlets of faucets on the bath, sink, and shower. OMG Systems Modeling Language (SysML) 1.6 Connector composite connector
EXAMPLE, INFO The top portion of Figure 9-11 shows specializations of the block WaterClient into Bath, Sink, and Shower. These are used as part types in the internal structure of the block House 2 shown in the lower portion of the figure OMG Systems Modeling Language (SysML) 1.6
EXAMPLE The connector in the top view “decomposes” into the subconnectors in the lower view according to the internal structure of Water Delivery. The subconnectors relate the nested ports of :WaterSupply to the nested ports of :WaterClient. OMG Systems Modeling Language (SysML) 1.6 Connector SysML specification figure, ParticipantProperty, AssociationBlock
EXAMPLE Figure 9-10 shows two views of a block House with a connector of type Water Delivery. OMG Systems Modeling Language (SysML) 1.6 Connector SysML specification figure, ParticipantProperty, AssociationBlock
INFO The internal structure connects hot and cold ports of the participants. OMG Systems Modeling Language (SysML) 1.6 Port AssociationBlock, ParticipantProperty
CONSTRAINT The aggregation of a property stereotyped by ParticipantProperty shall be none OMG Systems Modeling Language (SysML) 1.6 AggregationKind::none, AggregationKind ParticipantProperty
INFO The type of participant properties is shown for clarity, but is always the same as the association end type and can be elided. They are shown with dashed rectangles because they are reference properties. OMG Systems Modeling Language (SysML) 1.6 Port AssociationBlock, ParticipantProperty
INFO The participant properties identify the spigot bank and faucet being connected. The end property on the stereotype refers to the corresponding association end in Figure 9-8. OMG Systems Modeling Language (SysML) 1.6 Port AssociationBlock, ParticipantProperty, ParticipantProperty::end
INFO Figure 9-9 shows the internal structure of Water Delivery defining connectors between the spigots in the bank and inlets on the faucet. OMG Systems Modeling Language (SysML) 1.6 Port AssociationBlock
INFO Figure 9-8 shows an association block Water Delivery between a bank of spigots and a faucet. The «port» keyword indicates which association ends are ports (associations use properties as ends, which can be ports). OMG Systems Modeling Language (SysML) 1.6 Port AssociationBlock
INFO Ports appearing in block compartments can have their direction appear textually before the port name as “in,” “out,” or “inout” determined in the same way as the arrow direction. OMG Systems Modeling Language (SysML) 1.6 Port ProxyPort, FullPort, FlowProperty, FlowProperty::direction, FlowDirectionKind::in, FlowDirectionKind::out, FlowDirectionKind::inout, nested Port
INFO Ports with types that have flow properties in different directions or flow properties that are all in both directions, including have two open arrow heads inside them facing away from each other (<>). This includes the directions of nested and... OMG Systems Modeling Language (SysML) 1.6 Port ProxyPort, FullPort, FlowProperty, FlowProperty::direction, FlowDirectionKind::in, FlowDirectionKind::out, FlowDirectionKind::inout, nested Port
INFO This includes the direction of flow properties on nested ports, and if the port is full and its type is unencapsulated, ports on parts of the port, recursively. The arrows are perpendicular to the boundary lines they overlap. OMG Systems Modeling Language (SysML) 1.6 Port ProxyPort, FullPort, FlowProperty, FlowProperty::direction, FlowDirectionKind::in, FlowDirectionKind::out
INFO Ports with types that have flow properties all in the same direction, either all in or all out, can have an arrow inside them indicating the direction of the properties with respect to the owning block. OMG Systems Modeling Language (SysML) 1.6 Port ProxyPort, FullPort, FlowProperty, FlowProperty::direction, FlowDirectionKind::in, FlowDirectionKind::out
INFO The lower and upper properties of the stereotype give the minimum and maximum number of values, respectively, of the property at the bound end of the related bound reference, for each object reached by navigation along its binding path. OMG Systems Modeling Language (SysML) 1.6 EndPathMultiplicity, BoundReference, EndPathMultiplicity::lower, EndPathMultiplicity::upper
INFO The EndPathMultiplicity stereotype can be applied to properties that are related by redefinition to properties that have BoundReference applied. OMG Systems Modeling Language (SysML) 1.6 EndPathMultiplicity, BoundReference
INFO The specialization on the lower right restricts the number of cylinders to between six and eight, rules out any roll bar, and limits lug bolts per wheel to between 6 and 7, by giving the end path upper and lower values. OMG Systems Modeling Language (SysML) 1.6 Generalization, Property::redefinedProperty BoundReference, BindingConnector, nested Property
INFO The specialization on the lower left restricts the number of cylinders to four, requires a light roll bar, and a total of 24 lug bolts over all the wheels. OMG Systems Modeling Language (SysML) 1.6 Generalization, Property::redefinedProperty BoundReference, BindingConnector, nested Property
INFO The general block on the top does not restrict the bound properties, except the total number of lug bolts is required to be between 24 and 32, rather than 24 and 40 as the associations in Figure 8-15 allow. OMG Systems Modeling Language (SysML) 1.6 Generalization, Property::redefinedProperty BoundReference, BindingConnector, nested Property
INFO Figure 8-17 shows specializations for vehicles that restrict aspects of nested parts by redefining bound references. Paths for bound references are based on the property paths of the corresponding binding connectors. OMG Systems Modeling Language (SysML) 1.6 BoundReference, nested Property, BindingConnector
INFO Figure 8-16 shows the same decomposition in an internal block diagram that includes bound references. The binding connectors have nested connector ends, because they link inside the parts of the vehicle. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, SysML Internal Block Diagram, BoundReference, NestedConnectorEnd
INFO Figure 8-15 shows an example decomposition for vehicles in a block definition diagram. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, SysML Block Definition Diagram
INFO The binding path includes the property at the bound end, and before that, the property path of the bound end, if it is a nested connector end. OMG Systems Modeling Language (SysML) 1.6 BoundReference, BindingConnector, BoundReference::/bindingPath
INFO The bound end of the stereotype is a connector end of one of the binding connectors, opposite the stereotyped property. OMG Systems Modeling Language (SysML) 1.6 BoundReference, BindingConnector, BoundReference::boundEnd
INFO The BoundReference stereotype can be applied to properties that have binding connectors, to highlight their usage as constraining other properties. The bound end of the stereotype is a connector end of one of the binding connectors, opposite the .. OMG Systems Modeling Language (SysML) 1.6 BoundReference, BindingConnector
INFO This portion of concrete syntax is the same as may be shown for values within the UML instance specification notation, but this is the only element of UML InstanceSpecification notation that may be shown in an initial values compartment. OMG Systems Modeling Language (SysML) 1.6 compartment initial values, initialValues compartment, context-specific values
INFO Values are specified in an initialValues compartment by lines in the form <property-name> = <value-specification> or <property-name> : <type> = <value-specification>, each line of which specifies the initial value for one property owned either by ... OMG Systems Modeling Language (SysML) 1.6 compartment initial values, initialValues compartment, context-specific values
INFO Initial value compartments may be specified within nested properties, which then apply only in the particular usage context defined by the outermost containing block. OMG Systems Modeling Language (SysML) 1.6 compartment initial values, initialValues compartment, context-specific values
INFO A compartment with a label of “initialValues” may be used to show values of properties belonging to a containing block. These values override any default values that may have been previously specified on these properties on their originally defining block OMG Systems Modeling Language (SysML) 1.6 initial values, initialValues compartment, context-specific values
EXAMPLE, INFO Figure D.40 shows the same allocation relationships shown in Figure D.38, but in a more compact tabular representation. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem, Allocate, allocation, «allocate»
EXAMPLE, INFO Figure D.41[ ]shows a particular Hybrid SUV (VIN number) satisfying the EPA fuel economy test. Serial numbers of specific relevant parts are indicated. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem
EXAMPLE, INFO Figure D.39 depicts a subset of the PowerSubsystem, specifically showing the allocation relationships generated in Figure D.38. OMG Systems Modeling Language (SysML) 1.6 allocation, Allocate, «allocate»
INFO, NOTATION Multiple arrows coming out of a standalone Pin rectangle is an optional notation for multiple edges coming out of an OutputPin. Unified Modeling Language 2.5.1 ObjectNode, ActivityEdge, ObjectFlow
INFO, NOTATION The standalone Pin in the notation maps to an OutputPin and an InputPin and one ObjectFlow edge between them in the underlying model. This form should be avoided if the Pins are not of the same type. Unified Modeling Language 2.5.1 ObjectNode, ActivityEdge, ObjectFlow
INFO, NOTATION The situation in which the OutputPin of one Action is connected to the InputPin of the same name in another Action via an ObjectFlow may be shown by the optional notations of Figure 16.6. Unified Modeling Language 2.5.1 ObjectNode, ActivityEdge, ObjectFlow
INFO, NOTATION An object flow is notated by an arrowed line. In Figure 15.9, upper right, the two object flow arrows denote a single object flow edge between two pins in the underlying model, as shown in the lower middle of the figure. Unified Modeling Language 2.5.1 ObjectNode, ActivityEdge, ObjectFlow
INFO Note that the incoming and outgoing object flows for the ProvidePower activity have been decomposed. This was done to distinguish the flow of electrically generated mechanical power and gas generated mechanical power, and to provide further insight ... OMG Systems Modeling Language (SysML) 1.6 Activity, ObjectFlow HSUV sample problem
INFO Figure D.38 ... It also uses AllocateActivityPartitions and an allocation callout to explicitly allocate activities and an object flow to parts in the PowerSubsystem block. OMG Systems Modeling Language (SysML) 1.6 Action, Activity, ObjectNode HSUV sample problem, AllocateActivityPartition, Allocate, «allocate», allocation
INFO Figure D.38 shows the ProvidePower activity, which includes Actions invoking the decomposed Activities and ObjectNodes from Figure D.37. OMG Systems Modeling Language (SysML) 1.6 Action, Activity, ObjectNode HSUV sample problem
CONSTRAINT 1_streaming When the «rate» stereotype is applied to a parameter, the parameter shall be streaming. OMG Systems Modeling Language (SysML) 1.6 Parameter, Parameter::isStreaming Rate, Rate::rate, «rate»
CONSTRAINT Rate::rate - In particular, the denominator for units used in the rate property shall be time units. OMG Systems Modeling Language (SysML) 1.6 InstanceSpecification Rate, «rate», Rate::rate time
INFO The «rate» stereotype has a rate property of type InstanceSpecification. The values of this property shall be instances of classifiers stereotyped by «valueType» or «distributionDefinition» ... OMG Systems Modeling Language (SysML) 1.6 InstanceSpecification Rate, «rate», Rate::rate
INFO Streaming is a characteristic of UML behavior parameters that supports the input and output of items while a behavior is executing, rather than only when the behavior starts and stops. The flow may be continuous or discrete ... OMG Systems Modeling Language (SysML) 1.6 Parameter, Parameter::isStreaming, Behavior, execution Rate, «rate», Continuous, «continuous», Discrete, «discrete»
INFO Rate ... When the stereotype is applied to a parameter, the parameter shall be streaming, and the stereotype gives the number of objects or values that flow in or out of the parameter per time interval while the behavior or operation is executing. OMG Systems Modeling Language (SysML) 1.6 Parameter, object token, value, Behavior, Operation, Parameter::isStreaming Rate, «rate» flow, time
INFO Rate ... It does not refer to the rate at which a value changes over time. OMG Systems Modeling Language (SysML) 1.6 value Rate, «rate»
INFO When the «rate» stereotype is applied to an activity edge, it specifies the expected value of the number of objects and values that traverse the edge per time interval, that is, the expected value rate at which they leave the source node and arrive at ... OMG Systems Modeling Language (SysML) 1.6 ActivityEdge, DirectedRelationship::/source, DirectedRelationship::/target, object token, value, ActivityNode Rate, «rate»
INFO Associations can be used between activities and classifiers (blocks or value types) that are the type of object nodes, variables, or parameters in the activity, as shown in Figure 11-5. OMG Systems Modeling Language (SysML) 1.6 Activity, Association, Classifier Block, ValueType
INFO When composition is used with activity blocks, the termination of execution of an activity on the whole end will terminate executions of activities on the part end of the links. OMG Systems Modeling Language (SysML) 1.6 Activity, Association, AggregationKind::composite Block
INFO Activities as blocks can have associations between each other, including composition associations. Composition means that destroying an instance at the whole end destroys instances at the part end. OMG Systems Modeling Language (SysML) 1.6 Activity, Association, AggregationKind::composite Block
EXAMPLE, INFO Figure D.37 defines a decomposition of the activities and objectFlows from the activity diagram in Figure D.36. OMG Systems Modeling Language (SysML) 1.6 Activity, ObjectFlow
INFO One or more result values may be posted to a streaming output Parameter any time after the invocation of a Behavior up to or at its completion. These result values are then available to affect the further course of the execution of the invoking Behavior.. Unified Modeling Language 2.5.1 Behavior, Parameter::isStreaming, Parameter, execution, ParameterDirectionKind::out
INFO If an output Parameter is streaming, then a Behavior execution may provide result values for the Parameter during its course rather than just at completion. Unified Modeling Language 2.5.1 Behavior, Parameter::isStreaming, Parameter, execution, ParameterDirectionKind::out
INFO One or more argument values may be posted to a streaming input Parameter at or any time after the invocation of a Behavior and before its completion. These argument values are then available to affect the further course of the Behavior execution ... Unified Modeling Language 2.5.1 Behavior, Parameter::isStreaming, Parameter, execution, ParameterDirectionKind::in
INFO If an input Parameter is streaming, then argument values may be provided for the Parameter during the course of a Behavior execution rather than just at invocation. Unified Modeling Language 2.5.1 Behavior, Parameter::isStreaming, Parameter, execution, ParameterDirectionKind::in
INFO Parameters may also be marked as streaming (i.e., have the isStreaming property be true). Such Parameters allow values to be passed into and out of a Behavior execution any time during its course, rather than just on invocation and completion. Unified Modeling Language 2.5.1 Behavior, Parameter::isStreaming, Parameter, execution
INFO Continuous ... It is independent from UML streaming, see clause 11.3.2.8. A streaming parameter may or may not apply to continuous flow, and a continuous flow may or may not apply to streaming parameters. OMG Systems Modeling Language (SysML) 1.6 Parameter, ActivityEdge, Parameter::isStreaming Continuous, «continuous», Rate continuous system, flow, energy, water, material
INFO Continuous rate is a special case of rate of flow (see Rate) where the increment of time between items approaches zero. It is intended to represent continuous flows that may correspond to water flowing through a pipe, a time continuous signal, or ... OMG Systems Modeling Language (SysML) 1.6 Parameter, ActivityEdge Continuous, «continuous», Rate continuous system, flow, energy, water, material
INFO These two extensions are useful for ensuring that the most recent information is available to actions by indicating when old values should not be kept in object nodes, and for preventing fast or continuously flowing values from collecting ... OMG Systems Modeling Language (SysML) 1.6 ObjectNode, Pin NoBuffer, «noBuffer», Overwrite, «overwrite»
INFO SysML also extends object nodes with the option to discard values if they do not immediately flow downstream (see NoBuffer in Figure 11-8). OMG Systems Modeling Language (SysML) 1.6 ObjectNode, Pin NoBuffer, «noBuffer»
INFO Extension of object nodes, including pins, with the option for newly arriving values to replace values that are already in the object nodes (see Overwrite in Figure 11-8). OMG Systems Modeling Language (SysML) 1.6 ObjectNode, Pin Overwrite, «overwrite»
INFO Discrete and continuous flows are unified under rate of flow, as is traditionally done in mathematical models of continuous change, where the discrete increment of time approaches zero. OMG Systems Modeling Language (SysML) 1.6 «continuous», «discrete», Continuous, Discrete, Rate continuous system, flow, discrete system
INFO Restrictions on the rate at which entities flow along edges in an activity, or in and out of parameters of a behavior (see Rate in Figure 11-8). This includes both discrete and continuous flows, either of material, energy, or information. OMG Systems Modeling Language (SysML) 1.6 «continuous», Continuous, Discrete, Rate, «discrete» continuous system, material, energy, information, flow
INFO SysML provides extensions that might be very loosely grouped under the term “continuous,” but are generally applicable to any sort of distributed flow of information and physical items through a system. OMG Systems Modeling Language (SysML) 1.6 «continuous» continuous system
EXAMPLE, INFO The stereotypes on the object nodes between actions in the figure apply to parameters of the behaviors or operations called by the actions (see the notation for object nodes described in 11.3.1.4, ObjectNode, Variables, and Parameters). OMG Systems Modeling Language (SysML) 1.6 Activity, Behavior, ObjectNode, Parameter, Operation, Variable functional allocation
EXAMPLE, INFO It is the intent of the systems engineer in this example to allocate this behavior to parts of the PowerSubsystem. It is quickly found, however, that the behavior as depicted cannot be allocated, and must be further decomposed. OMG Systems Modeling Language (SysML) 1.6 Activity, Behavior functional allocation
EXAMPLE, INFO Figure D.36 shows the top level behavior of an activity representing acceleration of the HSUV. OMG Systems Modeling Language (SysML) 1.6 Activity, Behavior
EXAMPLE, INFO It assumes a constant 100hp at the drive wheels, 4000lb gross vehicle weight, and constant values for Cd and Cf. OMG Systems Modeling Language (SysML) 1.6 Timing Diagram, Constraint constraint parameter, ConstraintBlock
EXAMPLE, INFO For illustration purposes, however, the interaction shown in Figure D.35 was generated based on the constraints and parameters of the StraightLineVehicleDynamics constraintBlock, as described in the Figure D.33. OMG Systems Modeling Language (SysML) 1.6 Timing Diagram, Constraint constraint parameter, ConstraintBlock
INFO Timing diagrams, while included in UML 2, are not directly supported by SysML. OMG Systems Modeling Language (SysML) 1.6 Timing Diagram
EXAMPLE, INFO The constraints and parameters in Figure D.33 are detailed in Figure D.34 in Block Definition Diagram format. Note the use of valueTypes [ValueTypes] originally defined in Figure D.2. OMG Systems Modeling Language (SysML) 1.6 Constraint HSUV sample problem, SysML Block Definition Diagram, ValueType, ConstraintBlock, constraint parameter, MD:ConstraintParameter mathematics, equation
INFO, NOTATION Port labels appear in the same format as properties on the end of an association. Port labels can appear inside port rectangles. OMG Systems Modeling Language (SysML) 1.6 Port, label, NamedElement::name, Type
INFO, NOTATION Ports are notated by rectangles overlapping the boundary of their owning blocks or properties (parts or ports) typed by the owning block. OMG Systems Modeling Language (SysML) 1.6 Port
EXAMPLE, INFO The StraightLineVehicleDynamics constraint block from Figure D.32 has been expanded in Figure D.33. ConstraintNotes are used, which identify each constraint using curly brackets {}. In addition, Rationale has been used to explain the meaning ... OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem, Rationale, ConstraintBlock, constraint property, constraint parameter
EXAMPLE, INFO Since overall fuel economy is a key requirement on the HSUV design, this example applies significant detail in assessing it. Figure D.32 shows the constraint blocks and properties necessary to evaluate fuel economy. OMG Systems Modeling Language (SysML) 1.6 Property HSUV sample problem, ConstraintBlock
INFO «moe» A measure of effectiveness (moe) represents a parameter whose value is critical for achieving the desired mission cost effectiveness. OMG Systems Modeling Language (SysML) 1.6 custom Stereotype, user defined Stereotype «moe» non-normative, Measure of Effectiveness
INFO «objectiveFunction» An objective function (aka optimization or cost function) is used to determine the overall value of an alternative in terms of weighted criteria and/or moe's. OMG Systems Modeling Language (SysML) 1.6 custom Stereotype, user defined Stereotype «objectiveFunction», «moe» non-normative, objective function, Measure of Effectiveness
EXAMPLE, INFO This non-normative extension includes stereotypes for an objective function and a measure of effectiveness. The objective function is a stereotype of a ConstraintBlock and the measure of effectiveness is a stereotype of a block property. OMG Systems Modeling Language (SysML) 1.6 custom Stereotype, user defined Stereotype «moe», ConstraintBlock, Block, «objectiveFunction» Measure of Effectiveness, objective function, non-normative
EXAMPLE, INFO It will also be assumed that the overall mission cost effectiveness can be determined by applying an objective function to a set of criteria, each of which is represented by a measure of effectiveness. OMG Systems Modeling Language (SysML) 1.6 «moe» Measure of Effectiveness, objective function
EXAMPLE, INFO A measure of effectiveness (moe) represents a parameter whose value is critical for achieving the desired mission cost effectiveness. OMG Systems Modeling Language (SysML) 1.6 «moe» Measure of Effectiveness
INFO Figure D.31 shows how the overall cost effectiveness of the HSUV will be evaluated. It shows the particular measures of effectiveness for one particular alternative for the HSUV design, and can be reused to evaluate other alternatives. OMG Systems Modeling Language (SysML) 1.6 Stereotype, custom Stereotype, user defined Stereotype «moe» Measure of Effectiveness
INFO Measure of Effectiveness is a user defined stereotype. OMG Systems Modeling Language (SysML) 1.6 Stereotype, custom Stereotype, user defined Stereotype «moe» Measure of Effectiveness
EXAMPLE, INFO Figure D.30 shows the Requirements and VnV views and the supporting views that complete the description of Requirements and VnV respectively for the Hybrid SUV. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem, View
INFO It is sometimes desirable to construct views from other views, and to establish an order for presenting the views. Views may include one or more views as properties, each of which conforms to their viewpoint. The order of the referenced views is ... OMG Systems Modeling Language (SysML) 1.6 Property View, Conform, Viewpoint
INFO View::/viewpoint : Viewpoint [1] The viewpoint for this View is derived from the conform relationship. (derived) OMG Systems Modeling Language (SysML) 1.6 View, View::/viewpoint, Conform, Viewpoint
INFO View::/stakeholder : Stakeholder [0..*] The list of stakeholders is derived from the viewpoint the view conforms to. (derived) OMG Systems Modeling Language (SysML) 1.6 View, View::/stakeholder, Stakeholder
EXAMPLE, INFO Figure D.29 shows the Requirements and VnV views and the model elements they expose. Note that the expose relationship relies on the viewpoint method to identify the entire set of elements that appear in the view. OMG Systems Modeling Language (SysML) 1.6 Requirement, View, Viewpoint, Expose, Conform, View::/viewpoint
INFO Note that the value of the stakeholder property is an instance of the stereotype not the class to which the stereotype is applied. OMG Systems Modeling Language (SysML) 1.6 View, Viewpoint, Stakeholder, View::/stakeholder, Viewpoint::stakeholder
INFO The stakeholder and viewpoint share the same concern via comments that are shown textually as values of the concern property. The comments could be shown graphically with annotation relationships to stakeholders and viewpoints, if needed. OMG Systems Modeling Language (SysML) 1.6 View, Viewpoint, Stakeholder, Stakeholder::/concern, Viewpoint::concernList
INFO Figure D.28 shows the Requirements and VnV viewpoint definitions with relationships to stakeholders, concerns and views. OMG Systems Modeling Language (SysML) 1.6 View, Viewpoint, Stakeholder, Stakeholder::/concern, Viewpoint::concernList