110 likes | 151 Views
Explore the foundational principles and framework of the Systems Engineering Concept Model (SECM) in this detailed overview. Learn about kernel base concepts, principles for symmetry and consistency, extensibility, and avoiding circular dependencies.
E N D
Formulating theSystems Engineering Concept Model (SECM) Part 2: Kernel Base Concepts Presenting: Charles Galey Christopher Delp Robert Karban MagedElasar
Previously on SECM… • In part 1 we discussed: • Motivation • Approach • General Agreements: • Name: “Systems Engineering Concept Model (SECM)” • Associations and Sub-Classes are used to relate Concepts (i.e. MOF like) • Concept of Kernel and Library separation • Include definitions with each concept • Track open issues in JIRA • Actions • Post part 1 slides (Complete) • Create SECM wiki from WG page (Complete)
SECM Principles • Simple and parsimonious • Patterns to ensure symmetry and consistency • Extensible • SE domain concepts build on Kernel concepts • E.g., System subclasses Block • Avoid circular dependencies • …
Kernel Concepts • Base Concepts • Element • Container • Model • Comment • Relationship • Classifier (i.e. Block) • Feature (i.e. Property) • ValueSpecification • Additional kernel concepts sub-class the base concepts Kernel concepts intended to be domain neutral
Well Formed • Avoid circular dependencies • Oliver model utilized sequenced definitions to avoid circular dependencies • Our model will allow the identification of these dependencies via inspection
Simple and Parsimonious • Types define properties • A Property typed by a Quantity is a “Value Property” • No additional enhancements are specified
Extendable • Enable light weight groupings of concepts and libraries • The SECM Consists of two element groups the Kernel and the Libraries • Elements in libraries will need to be grouped in multiple ways • These groupings will need to be discovered • For example a “Requirement view” might exist in both a view library and a V&V library