Figure D.31 - Defining Measures of Effectiveness and Key Relationships (Parametric Diagram)

Gallery
Tutorial
TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7]
Section
Section: SysML-1.6: HSUV sample
UML keywords
Stereotype
custom Stereotype
user defined Stereotype
SysML keywords
«moe»
Keywords
Slide kind
SysML Parametric Diagram
In the spec this diagram is called 'HSUV MOEs'.
Click on the image to view it full size
SysML-1.6: Figure D.31 has constraint parameter 'vc' on ':CapacityEquation', which is inconsistent w.r.t. parameters 'V1', 'V2', 'V3' and constraint {pcap=Sum(Vi)) shown in Figure D.26.
Up next
Figure D.33 - Straight Line Vehicle Dynamics Mathematical Model (Parametric Diagram)
Notes
[ISSUE] SysML-1.6: Figure D.31 has constraint parameter 'vc' on ':CapacityEquation', which is inconsistent w.r.t. parameters 'V1', 'V2', 'V3' and constraint {pcap=Sum(Vi)) shown in Figure D.26.
[NAMING]{SUGGESTED} Webel: SysML: You don't need to call every ConstraintBlock a 'SomethingEquation'
[NAMING, STYLE]{STRONG} Webel: "Trust the Metaclass or Stereotype" of an Element to indicate what type of element it is (you don't have to repeat it in the name)
[CAPABILITY, FEATURE, TIP, TOOL] In MagicDraw/Cameo an assigned stereotype of a Classifier that types an instance-like element (such as a part Property) "shines through" unless it has an instance-level stereotype assigned. This is sometimes called a "secondary stereotype".
[NAMING, POLICY]{STRICT} SysML: Naming: Always use either anonymous or first letter lower case for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")! Valid: 'lowerCamelCase' OR 'tla' vs TLA acronym OR 'uCC' vs UpperCamelCase
[CAPABILITY, FEATURE, STYLE, TIP]{RECOMMENDED} TIP: UML/SysML: MagicDraw/Cameo: Consider showing the constraint parameter name and type label inside the small rectangular parameter symbol on SysML Parametric Diagrams. Dr Darren swears by it!
Snippets (quotes/extracts)
  [SysML-1.6] Measure of Effectiveness is a user defined stereotype.
  [SysML-1.6] 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.
  [SysML-1.6] A measure of effectiveness (moe) represents a parameter whose value is critical for achieving the desired mission cost effectiveness.
  [SysML-1.6] 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.
  [SysML-1.6] 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.
  [SysML-1.6] «moe» A measure of effectiveness (moe) represents a parameter whose value is critical for achieving the desired mission cost effectiveness.
  [SysML-1.6] «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.
  [SysML-1.6] Binding connectors, as defined in Clause 8 are used to bind each parameter of the constraint block to a property in the surrounding context.
  [SysML-1.6] 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..
  [SysML-1.6] All properties of a constraint block are constraint parameters, with the exception of constraint properties that hold internally nested usages of constraint blocks.
Visit also
Visit also (backlinks)
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)