Difference between revisions of "Framework Realisation Pattern"
From Model Based Systems Engineering Wiki
(→Architecture Framework Context View) |
(→Architecture Framework Context View) |
||
Line 13: | Line 13: | ||
Model Organisation is also constrained by limitations of the modelling tool and the need to obey modelling language constraints. | Model Organisation is also constrained by limitations of the modelling tool and the need to obey modelling language constraints. | ||
+ | |||
+ | ==Ontology Definition View== | ||
+ | To be defined | ||
+ | |||
+ | ==View Relationship View== | ||
+ | To be defined | ||
+ | |||
+ | ==View Context Views== | ||
+ | To be defined | ||
+ | |||
+ | ==View Definition Views== | ||
+ | To be defined | ||
+ | |||
+ | ==Rule Definition== | ||
+ | To be defined |
Revision as of 10:16, 28 April 2017
Contents |
Model Organisation Pattern
This Pattern has been proposed by J Gladstone.
Architecture Framework Context View
The main aim of the Model Organisation Pattern is to Organise the Model. This includes the following use cases:
- Present Model Structure - to define the structure of the model
- Support Model Navigation - to allow navigation between different parts of the model
- Manage Model Clutter - to prevent the model structure from being filled up with clutter
This last need its itself constrained by the need to for any model organisation to be flexible and extendable, to allow it to cope with any particular modelling needs encountered during normal work.
Model Organisation is also constrained by limitations of the modelling tool and the need to obey modelling language constraints.
Ontology Definition View
To be defined
View Relationship View
To be defined
View Context Views
To be defined
View Definition Views
To be defined
Rule Definition
To be defined