This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next 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:36] anwlur [JPL State Analysis (SA)] |
||
---|---|---|---|
Line 274: | Line 274: | ||
- 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. | ||
+ | - | ||