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 The view and the model elements related to the view are passed to the constructor when it is invoked. The method describes how the exposed elements are navigated to extract the desired information. OMG Systems Modeling Language (SysML) 1.6 Dependency, «Create» Expose, View, Viewpoint::/method
INFO The expose relationship relates a view to one or more model elements. Each model element is an access point to initiate the query. OMG Systems Modeling Language (SysML) 1.6 Dependency Expose, View
CONSTRAINT A Stakeholder stereotype can only be applied to UML::Actor or UML::Class which are not a UML::Association. OMG Systems Modeling Language (SysML) 1.6 Actor, Class Stakeholder
INFO A stakeholder represents a role, group, or individual who has concerns that will be addressed by the View of the model. OMG Systems Modeling Language (SysML) 1.6 Actor, Class Stakeholder, View
INFO Figure D.27 shows the user-defined Performance Viewpoint, and the elements that populate the HSUV specific PerformanceView. The PerformanceView itself may contain a number of diagrams depicting the elements it contains. OMG Systems Modeling Language (SysML) 1.6 Viewpoint, View
INFO Figure D.26 defines the various model elements that will be used to conduct analysis in this example. It depicts each of the constraint blocks/equations that will be used for the analysis, and key relationships between them. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock, constraint property, constraint parameter, nested ConstraintBlock equation, mathematics
INFO In addition, behavior allocation may also include the allocation of Behaviors to BehavioralFeatures of Blocks (e.g., Operations). OMG Systems Modeling Language (SysML) 1.6 Behavior, BehavioralFeature, Operation Allocate, allocation, «allocate», Block functional allocation
INFO It is acknowledged that this concept does not support a standard object-oriented paradigm, not[r] is this always even desirable. Experience on large scale, complex systems engineering problems have proven, however, that segregation of form and function... OMG Systems Modeling Language (SysML) 1.6 Behavior Allocate, allocation, «allocate» functional allocation
INFO Behavior allocation relates to the systems engineering concept segregating form from function. This concept requires independent models of "function" (behavior) and "form" (structure), and a separate, deliberate mapping between elements in each of these.. OMG Systems Modeling Language (SysML) 1.6 Behavior Allocate, allocation, «allocate» functional allocation
INFO The following paragraphs describe types of allocation that are typical in systems engineering. OMG Systems Modeling Language (SysML) 1.6 Allocate, allocation, «allocate»
INFO The Allocate stereotype specializes DirectedRelationshipPropertyPath to enable allocations to identify their sources and targets by a multi-level path of accessible properties from context blocks for the sources and targets. OMG Systems Modeling Language (SysML) 1.6 Allocate, allocation, «allocate», DirectedRelationshipPropertyPath, multi-level property path
INFO Allocate is directional in that one NamedElement is the "from" end (no arrow), and one NamedElement is the "to" end (the end with the arrow). OMG Systems Modeling Language (SysML) 1.6 «keyword», Abstraction, NamedElement Allocate, allocation, «allocate»
INFO Allocate is a stereotype of a UML4SysML::Abstraction that is permissible between any two NamedElements. It is depicted as a dependency with the "allocate" keyword attached to it. OMG Systems Modeling Language (SysML) 1.6 «keyword», Abstraction, NamedElement Allocate, allocation, «allocate»
INFO It is expected that an «allocate» relationship between model elements is a precursor to a more concrete relationship between the elements, their properties, operations, attributes, or sub-classes. OMG Systems Modeling Language (SysML) 1.6 «keyword», Class, Element, Property, attribute, Operation, Classifier::attribute Allocate, allocation, «allocate»
INFO Allocate is a dependency based on UML::Abstraction. It is a mechanism for associating elements of different types, or in different hierarchies, at an abstract level. Allocate is used for assessing user model consistency and directing future design ... OMG Systems Modeling Language (SysML) 1.6 Allocate, allocation
EXAMPLE, INFO The Fuel store represents a quantity of fuel in the FuelTankAssy, which is drawn by the FuelPump for use in the engine, and is refreshed, to some degree, by fuel returning to the FuelTankAssy via the FuelReturnLine. OMG Systems Modeling Language (SysML) 1.6 Connector HSUV sample problem, SysML Internal Block Diagram
EXAMPLE, INFO The fdist connector inside the InternalCombustionEngine block has been expanded into the fuel regulator and fuel rail parts. These more detailed design elements are related to the original connectors using the allocation relationship. OMG Systems Modeling Language (SysML) 1.6 Connector HSUV sample problem, SysML Internal Block Diagram
EXAMPLE, INFO Figure D.25 shows how the connectors fuelDelivery and fdist on Figure D.19 have been expanded to include design detail. The fuelDelivery connector is actually two connectors, one carrying fuelSupply and the other carrying fuelReturn. OMG Systems Modeling Language (SysML) 1.6 Connector HSUV sample problem, SysML Internal Block Diagram
INFO, NOTATION A parametric diagram is a restricted form of internal block diagram that shows only the use of constraint blocks along with the properties they constrain within a context. OMG Systems Modeling Language (SysML) 1.6 Property ConstraintBlock, MD:ConstraintParameter, constraint parameter, constraint property, SysML Parametric Diagram, value property
INFO, NOTATION The usage of a constraint block is distinguished from other parts by a box having rounded corners rather than the square corners of an ordinary part. OMG Systems Modeling Language (SysML) 1.6 «keyword» ConstraintBlock, «constraint», constraint property
INFO, NOTATION A constraint block is defined by a keyword of «constraint» applied to a block definition. Properties of this block define parameters of the constraint, with the exception of properties that hold internally nested usages of constraint blocks. OMG Systems Modeling Language (SysML) 1.6 «keyword» ConstraintBlock, «constraint», MD:ConstraintParameter, constraint parameter, constraint property
INFO, NOTATION If the property has no name, the property’s type name can be used instead. e.g., car:Engine:Cylinder:Piston.length car.e.c.p.length OMG Systems Modeling Language (SysML) 1.6 Property, Type, NamedElement::name multi-level property path, pathname dot notation anonymous
INFO, NOTATION In other words, the internal property shown with a path name in the left-hand side of Figure 8-1 is equivalent to the innermost nested box shown at the right. OMG Systems Modeling Language (SysML) 1.6 Property multi-level property path, pathname dot notation, nested Property
INFO, NOTATION This notation is purely a notational shorthand for a property that could otherwise be shown within a structure of nested property boxes, with the names in the dotted string taken from the name that would appear at each level of nesting OMG Systems Modeling Language (SysML) 1.6 Property multi-level property path, pathname dot notation, nested Property
INFO, NOTATION If any of the properties named in the path name string identifies a reference property, the property box is shown with a dashed-outline box, just as for any reference property on an internal block diagram. OMG Systems Modeling Language (SysML) 1.6 Property multi-level property path, pathname dot notation, reference property, MD:ReferenceProperty, MD:SharedProperty, shared property
INFO, NOTATION A colon and the type name for the property may optionally be shown following the dotted name string. OMG Systems Modeling Language (SysML) 1.6 Property multi-level property path, pathname dot notation
INFO, NOTATION The name of the referenced property is built by a string of names separated by “.”, resulting in a form of path name that identifies the property in its local context. OMG Systems Modeling Language (SysML) 1.6 Property multi-level property path, pathname dot notation
INFO, NOTATION A property name shown inside or outside the property box may take the form of a multi-level name. This form of name references a nested property accessible through a sequence of intermediate properties from a referencing context. OMG Systems Modeling Language (SysML) 1.6 Property multi-level property path, pathname dot notation
INFO The context for the usages of constraint blocks shall also be specified in a parametric diagram to maintain the proper namespace for the nested properties. OMG Systems Modeling Language (SysML) 1.6 Constraint, context ConstraintBlock, SysML Parametric Diagram, block property, NestedConnectorEnd, constraint property mathematics, equation
INFO This allows a value property (such as an engine displacement) that may be deeply nested within a containing hierarchy (such as vehicle, power system, engine) to be referenced at the outer containing level (such as vehicle-level equations). OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock, SysML Parametric Diagram, block property, NestedConnectorEnd, pathname dot notation, nested Property mathematics, equation
INFO A pathname dot notation can be used to refer to nested properties within a block hierarchy. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock, SysML Parametric Diagram, block property, NestedConnectorEnd, pathname dot notation, nested Property mathematics, equation
INFO The constrained properties, such as mass or response time, typically have simple value types that may also carry units, quantity kinds, or probability distributions. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock, SysML Parametric Diagram, block property, value property, Unit, QuantityKind mathematics, equation, probability distribution
INFO The usage of a constraint binds the parameters of the constraint, such as F, m, and a, to specific properties of a block, such as a mass, that provide values for the parameters. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock, SysML Parametric Diagram, constraint parameter, MD:ConstraintParameter, Block, block property, value property mathematics, equation
INFO Parametric diagrams include usages of constraint blocks to constrain the properties of another block. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock, SysML Parametric Diagram mathematics, equation
INFO The constraints can be nested to enable a constraint to be defined in terms of more basic constraints such as primitive mathematical operators. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock, nested ConstraintBlock mathematics, equation
INFO Reusable constraint definitions may be specified on block definition diagrams and packaged into general-purpose or domain-specific model libraries. Such constraints can be arbitrarily complex mathematical or logical expressions. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock, MD:ConstraintParameter, constraint parameter, SysML Block Definition Diagram mathematics, equation
INFO Constraint blocks define generic forms of constraints that can be used in multiple contexts. For example, a definition for Newton’s Laws may be used to specify these constraints in many different contexts. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock, MD:ConstraintParameter, constraint parameter mathematics, equation
INFO A constraint block includes the constraint, such as {F=m*a}, and the parameters of the constraint such as F, m, and a. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock, MD:ConstraintParameter, constraint parameter mathematics, equation
INFO Such constraints can also be used to identify critical performance parameters and their relationships to other parameters, which can be tracked throughout the system life cycle. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock mathematics, equation
INFO Constraint blocks can be used to specify a network of constraints that represent mathematical expressions such as {F=m*a} and {a=dv/dt}, which constrain the physical properties of a system. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock mathematics, equation
INFO Constraint blocks provide a mechanism for integrating engineering analysis such as performance and reliability models with other SysML models. OMG Systems Modeling Language (SysML) 1.6 ConstraintBlock
NOTATION A constraint property may be shown on a parametric diagram using a rectangle with rounded corners. This graphical shape distinguishes a constraint property from all other properties and avoids the need to show an explicit «constraint» keyword. Otherwise.. OMG Systems Modeling Language (SysML) 1.6 Property, «keyword» SysML Parametric Diagram, constraint parameter, constraint property, MD:ConstraintParameter, BindingConnector, «constraint» notation
INFO All properties that appear, other than the constraints themselves, shall either be bound directly to a constraint parameter, or contain a property that is bound to one (through any number of levels of containment). OMG Systems Modeling Language (SysML) 1.6 Property SysML Parametric Diagram, constraint parameter, constraint property, MD:ConstraintParameter, BindingConnector
INFO A parametric diagram is defined as a restricted form of internal block diagram. A parametric diagram may contain constraint properties and their parameters, along with other properties from within the internal block context. OMG Systems Modeling Language (SysML) 1.6 Property SysML Parametric Diagram, constraint parameter, constraint property, MD:ConstraintParameter
INFO A constraint property is a property of any block that is typed by a constraint block. It holds a localized usage of the constraint block. Binding connectors may be used to bind the parameters of this constraint block to other properties of the block ... OMG Systems Modeling Language (SysML) 1.6 ConstraintBlock, constraint parameter, MD:ConstraintParameter, BindingConnector, constraint property
INFO All properties of a constraint block are constraint parameters, with the exception of constraint properties that hold internally nested usages of constraint blocks. OMG Systems Modeling Language (SysML) 1.6 ConstraintBlock, constraint parameter, MD:ConstraintParameter, BindingConnector, constraint property
INFO Binding connectors, as defined in Clause 8 are used to bind each parameter of the constraint block to a property in the surrounding context. OMG Systems Modeling Language (SysML) 1.6 ConstraintBlock, constraint parameter, MD:ConstraintParameter, BindingConnector
INFO A constraint block typically defines one or more constraint parameters, which are bound to properties of other blocks in a surrounding context where the constraint is used. OMG Systems Modeling Language (SysML) 1.6 Constraint, Port ConstraintBlock, constraint parameter, MD:ConstraintParameter
INFO A constraint block is a block that packages the statement of a constraint so it may be applied in a reusable way to constrain properties of other blocks. OMG Systems Modeling Language (SysML) 1.6 Constraint ConstraintBlock
INFO As with any connector owned by a SysML Block, the ends of a binding connector may be nested within a multi-level path of properties accessible from the owning block. The NestedConnectorEnd stereotype is used to represent such nested ends just as for ... OMG Systems Modeling Language (SysML) 1.6 Connector, Property BindingConnector, Block, NestedConnectorEnd, multi-level property path
INFO If the properties at the ends of a binding connector are typed by a Block, the connector specifies that the instances of the properties shall refer to the same block instance. OMG Systems Modeling Language (SysML) 1.6 Connector, Property, instance BindingConnector, Block, block property
INFO If the properties at the ends of a binding connector are typed by a ValueType, the connector specifies that the instances of the properties shall hold equal values, recursively through any nested properties within the connected properties. OMG Systems Modeling Language (SysML) 1.6 Connector, Property BindingConnector, ValueType, value property
INFO A Binding Connector is a connector which specifies that the properties at both ends of the connector have equal values. OMG Systems Modeling Language (SysML) 1.6 Connector BindingConnector
EXAMPLE, INFO Figure D.24 is a parametric diagram showing how fuel flowrate is related to FuelDemand and FuelPressure value properties. OMG Systems Modeling Language (SysML) 1.6
INFO A FlowProperty signifies a single flow element to/from a block. A flow property has the same notation as a Property only with a direction prefix (in | out | inout). Flow properties are listed in a compartment labeled flow properties. OMG Systems Modeling Language (SysML) 1.6 Property FlowProperty, FlowProperty::direction, FlowDirectionKind::in, FlowDirectionKind::out, FlowDirectionKind::inout, FlowDirectionKind
INFO Flow properties specify the kinds of items that might flow between a block and its environment, whether it is data, material, or energy. The kind of items that flow is specified by typing flow properties. OMG Systems Modeling Language (SysML) 1.6 FlowProperty
INFO Blocks with ports can type other ports (nested ports). OMG Systems Modeling Language (SysML) 1.6 Port nested Port
INFO SysML extends blocks to support flow properties and provided and required features. OMG Systems Modeling Language (SysML) 1.6 provided Feature, required Feature, Block, FlowProperty
EXAMPLE, INFO The ports on the FuelTankAssembly and InternalCombustionEngine (as shown in Figure D.19) are defined in Figure D.23. OMG Systems Modeling Language (SysML) 1.6 Port HSUV sample problem
EXAMPLE, INFO Inversely, the InternalCombustionEngine can read the isControlOn property of the PowerControlUnit across the connector to determine if the unit is still operating, and possibly shut down if it is not. OMG Systems Modeling Language (SysML) 1.6 Connector HSUV sample problem, provided Feature, required Feature, part property, Block
EXAMPLE, INFO By invoking these operations, the PowerControlUnit can set the throttle and mixture of the InternalCombustionEngine. The PowerControlUnit can also read properties of the InternalCombustionEngine across the connector to find out the rpm, temperature, ... OMG Systems Modeling Language (SysML) 1.6 Connector HSUV sample problem, provided Feature, required Feature, part property, Block
EXAMPLE, INFO Since the ecu:PowerControlUnit part and ice:InternalCombustionEngine part are connected via these ports, the ecu:PowerControlUnit part may invoke setThrottle and setMixture on the ice:InternalCombustionEngine part via its ice port, across the connector... OMG Systems Modeling Language (SysML) 1.6 Port HSUV sample problem, provided Feature, required Feature, part property, Block
EXAMPLE, INFO This means the provided features of ICE are provided by the ctrl port of InternalCombustionEngine, and required by the ice port of PowerControlUnit, while the required features of ICE are required by the ctrl port of InternalCombustionEngine, and provided OMG Systems Modeling Language (SysML) 1.6 Port HSUV sample problem, provided Feature, required Feature, part property, Block
EXAMPLE, INFO For example, the ICE block specifies the provided operations setMixture and setThrottle, the provided properties RPM, temperature, and isKnocking, and required property isControlOn, as shown in Figure D.20. This block types the ctrl port of ... OMG Systems Modeling Language (SysML) 1.6 Property, Operation HSUV sample problem, provided Feature, required Feature, part property, Block
EXAMPLE, INFO The ecu:PowerControlUnit part has three ports with required and provided features, each connected to a port of another part. Each of the ports in this example is typed by a block specifying provided and required features available via connectors ... OMG Systems Modeling Language (SysML) 1.6 Port, part, Connector HSUV sample problem, provided Feature, required Feature, part property
EXAMPLE, INFO Figure 9-6 is a fragment of the ibd:PwrSys diagram used in the HybridSUV Sample Problem in Annex D. (The complete diagram is in Figure D.19.) OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem
INFO Figure D.20 provides definition of the block that types the ports linked by connector c1 in Figure D.19 OMG Systems Modeling Language (SysML) 1.6 Connector, Port HSUV sample problem, Block
INFO FlowProperty::direction : FlowDirectionKind [1] Specifies if the property value is received from an external block (direction="in"), transmitted to an external Block (direction="out") or both (direction="inout"). OMG Systems Modeling Language (SysML) 1.6 FlowProperty, FlowProperty::direction, FlowDirectionKind, FlowDirectionKind::in, FlowDirectionKind::out, FlowDirectionKind::inout
INFO, RULE These multiplicities may be assumed if not shown on a diagram. To avoid confusion, any multiplicity other than the default should always be shown on a diagram. OMG Systems Modeling Language (SysML) 1.7 Association, AggregationKind, multiplicity, AggregationKind::composite, AggregationKind::shared, MultiplicityElement::upperValue, MultiplicityElement::lowerValue, MultiplicityElement, MultiplicityElement::/lower, MultiplicityElement::/upper, Property::isNavigable(), DirectedRelationship::/target
INFO, RULE A part or shared association has a default multiplicity of [0..1] on the black or white diamond end. A unidirectional association has a default multiplicity of 1 on its target end. OMG Systems Modeling Language (SysML) 1.7 Association, AggregationKind, multiplicity, AggregationKind::composite, AggregationKind::shared, MultiplicityElement::upperValue, MultiplicityElement::lowerValue, MultiplicityElement, MultiplicityElement::/lower, MultiplicityElement::/upper, Property::isNavigable(), DirectedRelationship::/target
EXAMPLE, INFO SysML defines defaults for multiplicities on the ends of specific types of associations. OMG Systems Modeling Language (SysML) 1.7 Association, AggregationKind, multiplicity HSUV sample problem
EXAMPLE, INFO The dashed borders on Fuel denote a store, which keeps track of the amount and mass of fuel in the FuelTankAssy. This is also depicted in Figure D.18. OMG Systems Modeling Language (SysML) 1.6 AggregationKind, AggregationKind::shared HSUV sample problem
EXAMPLE, INFO The dashed borders on FrontWheel and BrakePedal denote the “use-not-composition” relationship depicted elsewhere in Figure D.16 and Figure D.18. OMG Systems Modeling Language (SysML) 1.6 AggregationKind, AggregationKind::shared HSUV sample problem
EXAMPLE, INFO Figure D.19 shows how the parts of the PowerSubsystem block, as defined in the diagram above, are used. It shows connectors between parts, ports, and connectors with item flows. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem
EXAMPLE, INFO Figure D.17 shows how the top level model elements in the above diagram are connected together in the HybridSUV block. OMG Systems Modeling Language (SysML) 1.6 Connector HSUV sample problem, Block
INFO Like UML, SysML defines no specific semantics or constraints for properties with shared aggregation, but particular models or tools may interpret them in specific ways. OMG Systems Modeling Language (SysML) 1.6 AggregationKind::shared, AggregationKind, Association, Property
INFO SysML also supports properties with shared aggregation, as shown by a white diamond symbol on an association. OMG Systems Modeling Language (SysML) 1.6 AggregationKind::shared, AggregationKind, Association, Property
EXAMPLE, INFO Figure D.16 defines components of the HybridSUV block. Note that the BrakePedal and WheelHubAssembly are used by, but not contained in, the PowerSubsystem block. OMG Systems Modeling Language (SysML) 1.6 AggregationKind::shared, AggregationKind::none HSUV sample problem, Block, shared property, reference property
EXAMPLE, INFO Note that the interactions DriveBlackBox and Stac4rtVehicleBlackBox (described in D.4.3 Elaborating Behavior (Sequence and State Machine Diagrams), are depicted as owned by the AutomotiveDomain block. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem
EXAMPLE, INFO Figure D.15 provides definition for the concepts previously shown in the context diagram. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem
EXAMPLE, INFO Figure D.14 contains two diagrams that show requirement containment (decomposition), and requirements derivation in tabular form. This is a more compact representation than the requirements diagrams shown previously. OMG Systems Modeling Language (SysML) 1.6 Requirement table, query table, report table
EXAMPLE, INFO The Power requirement is satisfied by the PowerSubsystem, and a Max Acceleration test case verifies the Acceleration requirement. OMG Systems Modeling Language (SysML) 1.6 UseCase HSUV sample problem, Requirement, TestCase, Verify, Block, «subsystem»
EXAMPLE, INFO The “refine” relation, introduced in Figure D.12, shows how the Acceleration requirement is refined by a similarly named use case. OMG Systems Modeling Language (SysML) 1.6 UseCase HSUV sample problem, Requirement, Refine
EXAMPLE, INFO Figure D.13 focuses on the Acceleration requirement, and relates it to other requirements and model elements. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem, Requirement
EXAMPLE, INFO Note also that rationale can be attached to the «deriveReqt» relationship. In this case, rationale is provided by a referenced document “Hybrid Design Guidance.” OMG Systems Modeling Language (SysML) 1.6 Refine HSUV sample problem, Requirement, DeriveReqt, Rationale requirements engineering
EXAMPLE, INFO Note how PowerSourceManagement is “RefinedBy” the HSUVOperationalStates model (Figure D.8). OMG Systems Modeling Language (SysML) 1.6 Refine HSUV sample problem, Requirement, Refine requirements engineering
INFO The Refine stereotype specializes UML4SysML Refine and DirectedRelationshipPropertyPath to enable refinements to identify their sources and targets by a multi-level path of accessible properties from context blocks for the sources and targets. OMG Systems Modeling Language (SysML) 1.6 Refine, DirectedRelationship::/source, DirectedRelationship::/target Refine, DirectedRelationshipPropertyPath
EXAMPLE, INFO Various other model elements may be necessary to help develop a derived requirement, and these model element may be related by a «refinedBy» relationship. OMG Systems Modeling Language (SysML) 1.6 Refine HSUV sample problem, Requirement, DeriveReqt, Refine requirements engineering
EXAMPLE, INFO Derived requirements, for the purpose of this example, express the concepts of requirements in the HSUVSpecification in a manner that specifically relates them to the HSUV system. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem, Requirement, DeriveReqt requirements engineering
EXAMPLE, INFO Figure D.12 shows a set of requirements derived from the lowest tier requirements in the HSUV specification. OMG Systems Modeling Language (SysML) 1.6 HSUV sample problem, Requirement, DeriveReqt requirements engineering
INFO When a requirement has nested requirements, all the nested requirements apply as part of the container requirement. Deleting the container requirement deleted [deletes] the nested requirements, a functionality inherited from UML. OMG Systems Modeling Language (SysML) 1.6 Requirement, composite (compound) requirement, subrequirement requirements engineering
INFO Subrequirements shall be accessed through the "nestedClassifier" property of a class. OMG Systems Modeling Language (SysML) 1.6 Class, Class::nestedClassifier, Classifier Requirement, «system», AbstractRequirement, composite (compound) requirement, subrequirement requirements engineering
INFO The default interpretation of a compound requirement, unless stated differently by the compound requirement itself, is that all its subrequirements shall be satisfied for the compound requirement to be satisfied. OMG Systems Modeling Language (SysML) 1.6 Class Requirement, «system», AbstractRequirement, composite (compound) requirement, Satisfy, subrequirement requirements engineering
INFO Compound requirements can be created by using the nesting capability of the class definition mechanism. OMG Systems Modeling Language (SysML) 1.6 Class Requirement, «system», AbstractRequirement, composite (compound) requirement requirements engineering
INFO A requirement is a stereotype of both Class and Abstract Requirement. OMG Systems Modeling Language (SysML) 1.6 Class Requirement, «system», AbstractRequirement requirements engineering
INFO Requirements are used to establish a contract between the customer (or other stakeholder) and those responsible for designing and implementing the system. OMG Systems Modeling Language (SysML) 1.6 Requirement, «system» requirements engineering, contract, customer, stakeholder, designer
INFO A requirement may specify a function that a system must perform or a performance condition that a system must satisfy. OMG Systems Modeling Language (SysML) 1.6 Requirement, Satisfy, «system» requirements engineering, function, system, performance condition
INFO A requirement specifies a capability or condition that must (or should) be satisfied. OMG Systems Modeling Language (SysML) 1.6 Requirement, Satisfy requirements engineering
EXAMPLE, INFO The containment (cross hair) relationship, for purposes of this example, refers to the practice of decomposing a complex requirement into simpler, single requirements. OMG Systems Modeling Language (SysML) 1.6 containment Requirement, HSUV sample problem
EXAMPLE, INFO The vehicle system specification contains many text based requirements. A few requirements are highlighted in Figure D.11, including the requirement for the vehicle to pass emissions standards, which is expanded for illustration purposes. OMG Systems Modeling Language (SysML) 1.6 Requirement, HSUV sample problem