Webel: SysML: TIP: Try "reverse" time ordered effect-from-cause Dependencies. Because it's harder to depend on something that does not already exist!
Webel: SysML4Mathematica: TIP: Representing Mathematica Paclets and their inter-dependencies as SysML Packages modelled in SysML Package Diagrams can really help you organise your Wolfram Language code on complex projects!
Webel: SysML: TIP: CONVENTION (default policy suggestion): Use reverse time ordering for Dependency, reserve Usage, PackageImport, ElementImport for software dependencies
Webel Parsing Analysis: SysML: Pseudo Semantic Triple: A «pa:triple» may be applied to a Dependency between SysML Blocks and/or Actors or Properties typed by them.
Simplified profile for Webel Parsing Analysis for SysML1.6+ in MagicDraw/Cameo (adapt as required) Gallery Tutorial TRAIL: Theory and best practices for the Webel Parsing Analysis recipe for SysMLv1.6+ Section Slide kind UML Profile Diagram
Webel Parsing Analysis: A stereotype with keyword «pa:from» may be applied to a Dependency from a Package to another Package within the Source Input Zone to indicate that all of its Elements were directly or indirectly elicited from source Documents.
Package Diagram index of Source Input Zone and elicited model elements in the Target Model Zone Gallery Tutorial TRAIL: Theory and best practices for the Webel Parsing Analysis recipe for SysMLv1.6+ Section Slide kind SysML Package Diagram
Additional Dependency relationships between ValueTypes and their Units on some SysML diagrams on this site are for educational illustration only (you don't need them in your own SysML models).
An eyepiece is a type of lens that is attached to a variety of optical devices such as telescopes and microscopes. Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model Section Slide kind SysML Block Definition Diagram (BDD)
The objective is the optical element that gathers light from the object being observed and focuses the light rays Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model Section Slide kind SysML Block Definition Diagram (BDD)
The reflecting telescope uses mirrors to collect and focus light Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model Section Slide kind SysML Block Definition Diagram (BDD)
Focus BDD for block RefractingTelescope Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model Section Slide kind SysML Block Definition Diagram (BDD)
The first known practical telescopes were refracting telescopes Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model Section Slide kind SysML Block Definition Diagram (BDD)
Our first Parsing Analysis diagram about telescopes Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: Optical telescopes from Wikipedia: Structure and port-based light flow model Section Slide kind SysML Block Definition Diagram (BDD)
Mass and charge of electron and positron Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia Section Slide kind SysML Block Definition Diagram (BDD)
Modelling antiparticles, antileptons, and antimatter This content has been marked as discussing an ADVANCED topic! Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia Section Slide kind SysML Block Definition Diagram (BDD)
Leptons and interactions Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia Section Slide kind SysML Block Definition Diagram (BDD)
Spin for elementary particles and composite particles Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia Section Slide kind SysML Block Definition Diagram (BDD)
Mass of charged leptons and decay (Part 2) Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia Section Slide kind SysML Block Definition Diagram (BDD)
Mass of charged leptons and decay (Part 1) Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia Section Slide kind SysML Block Definition Diagram (BDD)
Our first Parsing Analysis diagram about leptons Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia Section Slide kind SysML Block Definition Diagram (BDD)
Webel: A plain Dependency that is not stereotyped is always strictly timed-ordered; the supplier (target) must exist before the client (source).
Dependency vs Usage vs Association vs Connector Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 08:01: The building Blocks of SysML Slide kind SysML Block Definition Diagram (BDD)
A Usage is a Dependency in which the client Element requires the supplier Element (or set of Elements) for its full implementation or operation. Source Unified Modeling Language 2.5.1
This means that the complete semantics of the client Element(s) are either semantically or structurally dependent on the definition of the supplier Element(s). Source Unified Modeling Language 2.5.1
A Dependency is a Relationship that signifies that a single model Element or a set of model Elements requires other model Elements for their specification or implementation. Source Unified Modeling Language 2.5.1
MagicDraw/Cameo: If you can't find Usage on a particular diagram just use a Dependency then the refactor context menu item.
Examples of Dependency and Usage Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 08:01: The building Blocks of SysML Slide kind SysML Block Definition Diagram (BDD)
The Block Definition Diagram in SysML defines features of blocks and relationships between blocks such as associations, generalizations, and dependencies. Source OMG Systems Modeling Language (SysML) 1.6
TestCase and Verify metamodel Gallery Tutorial TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo Section 16:01: Requirements engineering in SysML Slide kind UML diagram UML Profile Diagram
A Verify relationship is a dependency between a requirement and a test case or other model element that can determine whether a system fulfills the requirement. As with other dependencies, the arrow direction points from the (client) element to the (suppl Source OMG Systems Modeling Language (SysML) 1.6
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. Source OMG Systems Modeling Language (SysML) 1.6
Copy::2_same_text The text property of the client requirement is constrained to be a read-only copy of the text property of the supplier requirement and this applies recursively to all subrequirements Source OMG Systems Modeling Language (SysML) 1.6
Copy::1_source_and_taget_are_requirements A Copy dependency may only be created between two NamedElements that have a subtype of the abstractRequirement stereotype applied Source OMG Systems Modeling Language (SysML) 1.6
When a Copy dependency exists between two requirements, the requirement text of the client requirement is a read-only copy of the requirement text of the requirement at the supplier end of the dependency. Source OMG Systems Modeling Language (SysML) 1.6
A Copy dependency created between two requirements maintains a master/slave relationship between the two elements for the purpose of requirements re-use in different contexts Source OMG Systems Modeling Language (SysML) 1.6
A Copy relationship is a dependency between a supplier requirement and a client requirement that specifies that the text of the client requirement is a read-only copy of the text of the supplier requirement. Source OMG Systems Modeling Language (SysML) 1.6
Satisfy::getSatisfies (in ref : NamedElement) : AbstractRequirement [0..*] Source OMG Systems Modeling Language (SysML) 1.6
Satisfy::1_supplier_is_requirement The supplier shall be an element stereotyped by any subtype of «AbstractRequirement». Source OMG Systems Modeling Language (SysML) 1.6
As with other dependencies, the arrow direction points from the satisfying (client) model element to the (supplier) requirement that is satisfied. Source OMG Systems Modeling Language (SysML) 1.6
A Satisfy relationship is a dependency between a requirement and a model element that fulfills the requirement. Source OMG Systems Modeling Language (SysML) 1.6
DeriveReqt::2_client_is_requirement The client shall be an element stereotyped by a subtype of AbstractRequirement. Source OMG Systems Modeling Language (SysML) 1.6
DeriveReqt::1_supplier_is_requirement The supplier shall be an element stereotyped by a subtype of AbstractRequirement. Source OMG Systems Modeling Language (SysML) 1.6
As with other dependencies, the arrow direction points from the derived (client) requirement to the (supplier) requirement from which it is derived. Source OMG Systems Modeling Language (SysML) 1.6
A DeriveReqt relationship is a dependency between two requirements in which a client requirement can be derived from the supplier requirement. Source OMG Systems Modeling Language (SysML) 1.6
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. Source OMG Systems Modeling Language (SysML) 1.6
The expose relationship relates a view to one or more model elements. Each model element is an access point to initiate the query. Source OMG Systems Modeling Language (SysML) 1.6
Dependency/Usage relationships in some referenced UML/SysML diagrams on this site are for educational illustration only, they are NOT part of the actual model.
