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/17 14:17] anwlur [JPL State Analysis (SA)] added dev activities |
bok:eng:mbse:method [2020/09/18 10:38] (current) anwlur [JPL State Analysis (SA)] |
||
|---|---|---|---|
| Line 271: | Line 271: | ||
| === 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. | + | - 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. | - 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// | - 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 | + | - In a state effects diagram (=internal block diagram) map the relationship between different state variables contained within the context. Use //affects// and //affectedBy// relationships. |
| - | - Goals are elaborated as (typically) stereotyped use cases whilst the temporal aspect of goals is defined as constraints and analysed in parametric diagrams. | + | - 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.1600352231.txt.gz · Last modified: 2020/09/17 14:17 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
