User Tools
bok:eng:mbse:method
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
bok:eng:mbse:method [2020/09/11 07:55] anwlur [JPL State Analysis (SA)] |
bok:eng:mbse:method [2020/09/18 10:38] (current) anwlur [JPL State Analysis (SA)] |
||
|---|---|---|---|
| Line 245: | Line 245: | ||
| * Mission Planning & Execution supplies Control Goals to State Control | * Mission Planning & Execution supplies Control Goals to State Control | ||
| * Mission Planning & Execution supplies Knowledge Goals to State Estimation | * Mission Planning & Execution supplies Knowledge Goals to State Estimation | ||
| - | * State Estimation supplies State Functions (?) to State Knowledge | + | * State Estimation supplies State Functions :?: to State Knowledge |
| * State Knowledge supplies State Values to State Control | * State Knowledge supplies State Values to State Control | ||
| * Models bridges State Estimation, Knowledge and Control | * Models bridges State Estimation, Knowledge and Control | ||
| Line 268: | Line 268: | ||
| * Keep track of system constraints and operating rules | * Keep track of system constraints and operating rules | ||
| * Describing methods by which objectives will be achieved | * Describing methods by which objectives will be achieved | ||
| - | |||
| - | |||
| - | |||
| - | * Unordered List Item | ||
| - | * Make system intent explicit in the design and implementation | ||
| - | * Controllers use state estimates as inputs - not direct measurements | ||
| - | * Single controller per state variable | ||
| - | * Single estimator per state variable | ||
| - | |||
| - | === Example === | ||
| - | |||
| - | |||
| === Development Activities === | === Development Activities === | ||
| + | - The foundation of the JPL SA methodology is the control system and the //system under control// are explicitly different. This separation is formalized in an //ontology// which is written in OWL2. JPL used [[https://protege.stanford.edu/|Protege]] as the editing environment. | ||
| + | - This ontology is mapped to SysML artifacts using Query/View/Transformation (QVT), a model-to-model transformation standard by OMG. | ||
| + | - A context diagram (block diagram) includes //Analysis Context// with parts //System Under Control// and //Control System// | ||
| + | - In a state effects diagram (=internal block diagram) map the relationship between different state variables contained within the context. Use //affects// and //affectedBy// relationships. | ||
| + | - Define mathematical relationships between State Variables with parametric diagrams | ||
| + | - Control System is designed. A State Variable has only 1 //Controller// and (may) have only one //Estimator// | ||
| + | - The //HardwareAdapter// is modeled to be an interface between the Control System and System Under Control. Measurements flow from System Under Control to Control System, Controls flow the other way. | ||
| + | - Goals are elaborated as (typically) stereotyped use cases whilst the temporal aspect of goals is defined as constraints and analyzed in parametric diagrams. | ||
| ==== Object-Process Methodology (OPM) ==== | ==== Object-Process Methodology (OPM) ==== | ||
| ==== SYSMOD ==== | ==== SYSMOD ==== | ||
| + | |||
| + | ==== Funcational Architecture Methodology ==== | ||
| + | |||
bok/eng/mbse/method.1599810936.txt.gz · Last modified: 2020/09/11 07:55 by anwlur
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
