User Tools

Site Tools


bok:eng:mbse:method

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
bok:eng:mbse:method [2020/09/11 07:55]
anwlur [JPL State Analysis (SA)]
bok:eng:mbse:method [2020/09/17 14:17]
anwlur [JPL State Analysis (SA)] added dev activities
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 269: Line 269:
     * Describing methods by which objectives will be achieved     * Describing methods by which objectives will be achieved
  
 +=== 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
 +  - Goals are elaborated as (typically) stereotyped use cases whilst the temporal aspect of goals is defined as constraints and analysed in parametric diagrams.
  
-  * 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 === 
  
  
bok/eng/mbse/method.txt ยท Last modified: 2020/09/18 10:38 by anwlur