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 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
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