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
SEMANTIC Exiting via a FinalState or by a group Transition has the same meaning as for ordinary composite States. Unified Modeling Language 2.5.1 State, StateMachine, submachine, group Transition, Transition, composite State
CONSTRAINT exitPoint – ... If multiple Transitions from orthogonal Regions within the State terminate on this Pseudostate, then it acts like a join Pseudostate. Unified Modeling Language 2.5.1 State, Pseudostate, PseudostateKind::exitPoint, StateMachine, composite State, Region, State::exit, Behavior
CONSTRAINT exitPoint – An exitPoint Pseudostate is an exit point of a StateMachine or composite State that provides encapsulation of the insides of the State or StateMachine. Unified Modeling Language 2.5.1 State, Pseudostate, PseudostateKind::exitPoint, StateMachine, composite State
INFO Exotic baryons containing five quarks (known as pentaquarks) have also been discovered and studied. Wikipedia
SEMANTIC Expressions are ValueSpecifications that specify values resulting from a computation. Unified Modeling Language 2.5.1 Expression, ValueSpecification, computation
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 external - Implies that the Transition, if triggered, will exit the composite (source) State. Unified Modeling Language 2.5.1 Transition, TransitionKind, Transition::kind, Enumeration, TransitionKind::external, State::exit, composite State
INFO f1 is replaced by p1.f, v1 is replaced by p1.lV, x is replaced by lengthchg, k is replaced by springcst, v is replaced by velocitydiff, f is replaced by forcethru, v2 is replaced by p2.v, and f2 is replaced by p2.f. SysPhS-1.1 Constraint ConstraintBlock, constraint parameter, constraint property SysPhS, SysML, Systems Modeling Language, Modelica
INFO Far infrared (FIR) is a region in the infrared spectrum of electromagnetic radiation. Far infrared is often defined as any radiation with a wavelength of 15 micrometers (μm) to 1 mm Wikipedia infrared, infrared astronomy, far infrared
SEMANTIC Features represent structural and behavioral characteristics of Classifiers. Unified Modeling Language 2.5.1 Feature, Classifier, StructuralFeature, BehavioralFeature
INFO Features that are not denoted as a DirectedFeature are implicitly provided features. As such they can be matched against a corresponding required feature. OMG Systems Modeling Language (SysML) 1.7beta1 DirectedFeature, FeatureDirectionKind::provided, FeatureDirectionKind::required, FeatureDirectionKind::providedrequired, FeatureDirectionKind
INFO Fermions differ from bosons, which obey Bose–Einstein statistics. Wikipedia
INFO Fermions include all quarks and leptons, as well as all composite particles made of an odd number of these, such as all baryons and many atoms and nuclei. Wikipedia
INFO Figure 11-10 shows a simplified model of driving and braking in a car that has an automatic braking system. OMG Systems Modeling Language (SysML) 1.6 SysML specification figure, Continuous, «continuous»
EXAMPLE, INFO Figure 11-13 shows a block definition diagram with composition associations between the activities and AdjunctProperty applied to the part ends in Figures 11.10, 11.11, and 11.12, as an alternative way to show the activity decomposition of Figures ... OMG Systems Modeling Language (SysML) 1.6 AggregationKind::composite, Association AdjunctProperty, SysML Block Definition Diagram
EXAMPLE, INFO Figure 11-14 shows a block definition diagram with composition associations between the activity in Figure 11-10 and the types the object nodes in that activity, with AdjunctProperty applied to the object node type end. OMG Systems Modeling Language (SysML) 1.6 AggregationKind::composite, Association, Activity, ObjectNode «activity», SysML specification figure, AdjunctProperty
EXAMPLE, INFO Figure 15-5 shows flow allocation of [an] ObjectFlow to a Connector, or alternatively to an ItemFlow. OMG Systems Modeling Language (SysML) 1.6 ObjectFlow, Connector SysML specification figure, Allocate, ItemFlow
EXAMPLE, INFO Figure 16-5 illustrates the use of the Copy dependency to allow a single requirement to be reused in several requirements hierarchies. The master tag provides a textual reference to the reused requirement. OMG Systems Modeling Language (SysML) 1.6 Dependency, Dependency::client, Dependency::supplier Copy, Requirement
EXAMPLE, INFO Figure 17-1 [Figure 16-7] is a state machine diagram of the BurnishTest test case, which expresses the textual sequence and criteria of the Burnish requirement in state machine form. OMG Systems Modeling Language (SysML) 1.6 callout, StateMachine HSUV sample problem, SysML specification figure, Requirement, TestCase requirements engineering, test engineering
INFO Figure 22 shows an example signal flow application. The block Spring has two ports u and y, of type RealInSignalElement and RealOutSignalElement from the signal flow library ..., respectively. SysPhS-1.1 Port "standard" Port SysPhS
INFO Figure 25 shows an example [USAGE OF A] constraint block for a signal flow application, using ports like those defined in Figure 22, Subclause 10.7.3, except in a system containing a spring attached to another object. SysPhS-1.1 ConstraintBlock SysPhS
INFO Figure 28 shows how a value type with units is defined in SysML, from the units library in Figure 20 [ERROR], Subclause 11.2.2 [ERROR]. It has a value type Force that specializes the Real value type and has newton as unit. The newton unit has a symbol N. SysPhS-1.1 ValueType, Unit, ValueType::unit, Real SysPhS, SysML, Systems Modeling Language, ISO-80000
INFO Figure 47 and Figure 48 show the internal structure of blocks TestBed and SignalProcessor, respectively SysPhS-1.1 SysML Internal Block Diagram SysPhS, signal processing
INFO Figure 47 connects a signal source to a signal processor, which it connects to a signal sink that displays the output. SysPhS-1.1 Port, Connector "standard" Port, SysML Internal Block Diagram SysPhS, signal processing
INFO Figure 47 shows an initial value for source amplitude amp, while Figure 48 shows initial values for amplifier signal gain g and filtering properties xi and alpha ... SysPhS-1.1 Property::defaultValue, Property initial values, context-specific values, initialValues compartment SysPhS, signal processing, amplifier, filter, high-pass filter, low-pass filter
INFO Figure 48 connects the signal processor input to an amplifier, the output of the amplifier to a high-pass filter in parallel with a low-pass filter, the outputs of the filters to a mixer, and the output of the mixer to the signal processor output. SysPhS-1.1 Port, Connector "standard" Port, SysML Internal Block Diagram SysPhS, signal processing
INFO Figure 49-Figure 50 show block definitions for components of TestBed and SignalProcessor in Figure 47 and Figure 48, respectively. SysPhS-1.1 Block SysPhS, signal processing, amplifier, filter, high-pass filter, low-pass filter
INFO Figure 52 through Figure 57 show parametric diagrams for the source, amplifier, high-pass fil[t]er, low-pass filter, mixer, and sink, respectively. SysPhS-1.1 Constraint ConstraintBlock, constraint parameter, BindingConnector, SysML Parametric Diagram, constraint property, MD:ConstraintProperty SysPhS, signal processing
INFO Figure 59 shows the internal structure of a ConnectedTanks block. SysPhS-1.1 SysML Internal Block Diagram SysPhS, hydraulics
INFO Figure 60 shows block definitions for components of ConnectedTanks in Figure 59. SysPhS-1.1 SysPhS, hydraulics
INFO Figure 62 and Figure 63 show the parametric diagrams of the tank and the pipe, respectively. SysPhS-1.1 Constraint constraint parameter, ConstraintBlock, BindingConnector, SysML Parametric Diagram SysPhS
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 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-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-22 shows property-specific types in a model of facilities that includes factories and warehouses. Items flow through facilities, while resources operate on items. OMG Systems Modeling Language (SysML) 1.6 Classifier, Stereotype, Property PropertySpecificType
INFO Figure 8-23 shows the classification of a particular machine over time, identified by its serial number. OMG Systems Modeling Language (SysML) 1.6 Classifier, Stereotype, Property PropertySpecificType
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
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 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-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-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 9-7 happens to use unstereotyped ports on a general block distributed to users, and stereotyped ports on its specializations for implementation, but the modelers might have not used stereotypes at all, if they did not care whether the model met ... OMG Systems Modeling Language (SysML) 1.6 Port FullPort, "standard" Port, ProxyPort
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 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
EXAMPLE, INFO Figure D.10 shows the sequence of communication that occurs inside the HybridSUV when the vehicle is started successfully. OMG Systems Modeling Language (SysML) 1.6 Interaction SysML Sequence Diagram, HSUV sample problem
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
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 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 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.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 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
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
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
EXAMPLE Figure D.21 is an incomplete first step in the refinement of this bus architecture, as it begins to specify the flow properties for InternalCombustionEngine, the Transmission, and the ElectricalPowerController. OMG Systems Modeling Language (SysML) 1.6 Signal, Connector, Port FlowProperty, "standard" Port
EXAMPLE Figure D.22 continues the refinement of this Controller Area Network (CAN) bus architecture using ports. OMG Systems Modeling Language (SysML) 1.6 Signal, Connector, Port FlowProperty, "standard" Port
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
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 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 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.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
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
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 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 Figure D.32 shows the use of constraint properties on a parametric diagram. This diagram shows the use of nested property references to the properties of the parts; OMG Systems Modeling Language (SysML) 1.6 ConstraintBlock, constraint property, SysML Parametric Diagram, nested Property, multi-level property path
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 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 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
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»
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.7 illustrates the overall system behavior for operating the vehicle in Sequence diagram format. OMG Systems Modeling Language (SysML) 1.6 SysML Sequence Diagram, HSUV sample problem
EXAMPLE, INFO Figure D.7 shows the interactions between driver and vehicle that are necessary for the “Drive the Vehicle” Use Case. This diagram represents the “DriveBlackBox” interaction, with [which] is owned by the AutomotiveDomain block. OMG Systems Modeling Language (SysML) 1.6 interaction diagram, Sequence Diagram, UseCase HSUV sample problem
EXAMPLE, INFO Figure D.8 depicts the operational states of the HSUV block, via a State Machine named “HSUVOperationalStates.” OMG Systems Modeling Language (SysML) 1.6 State, StateMachine, StateMachine Diagram HSUV sample problem black box, Object Constraint Language
EXAMPLE, INFO Figure D.9 shows a “black box” interaction, but references “StartVehicleWhiteBox” (Figure D.10), which will decompose the lifelines within the context of the HybridSUV block. OMG Systems Modeling Language (SysML) 1.6 Interaction, Sequence Diagram, Lifeline, interactionOperator ref HSUV sample problem, Block
EXAMPLE, INFO Figure D.9 shows an interaction that includes events and messages communicated between the driver and vehicle during the starting of the vehicle. OMG Systems Modeling Language (SysML) 1.6 Interaction, Event, Message SysML Sequence Diagram
INFO Figures 9.16 and 9.17 are examples of item flow decomposition that modelers might choose, but they are not the only possible decompositions and are not required. OMG Systems Modeling Language (SysML) 1.6 Connector ItemFlow, AssociationBlock
INFO Film or a digital sensor may be located here to record the image, or a secondary mirror may be added to modify the optical characteristics and/or redirect the light to film, digital sensors, or an eyepiece for visual observation. Wikipedia
INFO Flow Port and Flow Specification are deprecated in this version of SysML and are defined for backward compatibility. OMG Systems Modeling Language (SysML) 1.7beta1 DEPRECATED:FlowPort, DEPRECATED:FlowSpecification Systems Modeling Language, SysML, SysMLv1.6, SysMLv1.7
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
CONSTRAINT FlowProperty::1_restricted_types A FlowProperty shall be typed by a ValueType, Block, or Signal. OMG Systems Modeling Language (SysML) 1.6 Signal FlowProperty, ValueType, 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
NOTATION For an item flow with an item property, the label shows the name and type of the item property (in name: type format). Otherwise the item flow is labeled with the name of the classifier of the conveyed items. OMG Systems Modeling Language (SysML) 1.6 Connector, Association, label ItemFlow
INFO For each execution, an Action cannot terminate itself unless it can put at least as many values into its outputs as required by the multiplicity lower bounds on those OutputPins. Values that may remain on the OutputPins from previous executions are not... Unified Modeling Language 2.5.1 Activity, Activity Diagram, Action, Pin, OutputPin, Action::/output, execution, MultiplicityElement::/lower
INFO For every lepton flavor, there is a corresponding type of antiparticle, known as an antilepton, that differs from the lepton only in that some of its properties have equal magnitude but opposite sign. Wikipedia
INFO For every quark flavor there is a corresponding type of antiparticle, known as an antiquark, that differs from the quark only in that some of its properties (such as the electric charge) have equal magnitude but opposite sign. Wikipedia
INFO For example the measurement unit “metre per second” for “velocity” is specified as the product of “metre” to the power one times “second” to the power minus one. OMG Systems Modeling Language (SysML) 1.6 Unit, DerivedUnit
INFO For example “velocity” can be specified as the product of “length” to the power one times “time” to the power minus one, and subsequently “speed” can be specified as “velocity” to the power one. OMG Systems Modeling Language (SysML) 1.6 DerivedQuantityKind, QuantityKind
INFO For example, a block might provide particular services to other blocks as operations, or have a particular geometry accessible to other block, or it might require services and geometries of other blocks. OMG Systems Modeling Language (SysML) 1.6 Feature, Operation, Reception, Property DirectedFeature, FeatureDirectionKind, FeatureDirectionKind::provided, FeatureDirectionKind::required, FeatureDirectionKind::providedrequired, value property
INFO For example, a block specifying a car’s automatic transmission could have a flow property for Torque as an input, and another flow property for Torque as an output. OMG Systems Modeling Language (SysML) 1.6 FlowProperty
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
EXAMPLE For example, a junction Pseudostate can be used to merge multiple incoming Transitions into a single outgoing Transition representing a shared continuation path. Unified Modeling Language 2.5.1 Pseudostate, PseudostateKind::junction, Transition, StateMachine
INFO, NOTATION For example, a label of "liquid: Water" means Water items might flow and these items are the values of the property "liquid," i.e., the values of the "liquid" item property are the instances of Water flowing at any given time. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow
INFO For example, a pump connected to a tank: the pump has an "out" flow property of type Liquid and the tank has an "in" FlowProperty of type Liquid. OMG Systems Modeling Language (SysML) 1.6 InformationFlow ItemFlow, FlowProperty, FlowDirectionKind::in, FlowDirectionKind::out, FlowDirectionKind
INFO For example, a system requirement may be derived from a business need, or lower-level requirements may be derived from a system requirement. OMG Systems Modeling Language (SysML) 1.6 DeriveReqt, Requirement system requirement, business requirement
EXAMPLE, INFO For example, if a particular user model includes an abstract logical structure, it may be important to show how these model elements are allocated to a more concrete physical structure. OMG Systems Modeling Language (SysML) 1.6 Connector, part Allocate, «allocate», structural allocation, Block, part property
INFO For example, if the port types on the general block in Figure 9-7 had behaviors defined, then the proxy specialization would be invalid. If the general ports had binding connectors to internal parts, then the full specialization would be invalid. OMG Systems Modeling Language (SysML) 1.6 Port FullPort, "standard" Port, ProxyPort
INFO For example, in a telescope, the aperture stop is typically the edges of the objective lens or mirror (or of the mount that holds it). One then speaks of a telescope as having, for example, a 100-centimeter aperture. Wikipedia optical telescope, telescope, aperture, optics, astronomy, astrophotography
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 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