model integration for systems engineering
TRANSCRIPT
1
Integration of High-level System Model, Cost Model, Environment Model and Life Cycle Model for
Typical Design
Requirements Engineering and Architecture Options Definition Stage
Victor AgroskinRuSEC 2010
2
Life Cycle of a «Typical Design»
Concept Production Utilisation RetirementDevelopment
Concept ImplementationDevelopmentModernisation
ImplementationModernisation
Retirement
• Generic LC
• Life cycle of a “Typical Design” for a technological platform
• Peculiarities of a “Modernisation” stage– Stakeholders’ variety– Multiple goals– Complex structure of vested interests
3
Modernisation stage as a project
3
Architecture trade-off analysis …Requirements
engineering
Goa
l mod
elT
echn
ical
-ec
onom
ic m
odel
Conceptual Design
1. Life cycle of a modernisation project:
2. Requirements engineering and Architecture trade-off analysis – Models and work products:
• Stakeholders -> Requirements -> Goals & Technical proposals
• Goals -> Goal achievement criteria
• Technical Proposals -> Architectural configurations -> Options -> Full architectural configurations -> Simulations
• Simulations & Goal achievement criteria -> Conceptual design
4
Megamodel
– Metamodels (formal conceptualisation of a model’s content)
– Domain model for “Technology and economy of power plants” (content model)
– Libraries and model registers (simulated and/or executed models under configuration management)
4
Project’smodellingstandard
5
Project’s modelling standard• Modelling standard
– Uniform system of objects and relationships– Collaboration support for distributed modelling teams– Possibility to compare modelling effort results for various teams– Consolidation possibilities for model items– Are standardised: principles of item and class selection for
technical and economic model, their relationships – Not standardised: modelling methods and languages
• Possible foundations for the standard (meta-standards):– ISO 15288 (Systems Engineering practices), ISO 42010 (architecture
description recommendations), ISO 24744 (engineering method development), ISO/IEC 19501 (UML language), W3C Recommendations (OWL, RDF languages and notations).
5
6
Metamodel for model-based requirements engineering
7
From wishes to requirementsMake an excess load in peak demand hours possible for a typical power plant in an environment with deficit installed capacity .
8
Goal model in i*
Earn extra cash in peak hours
Steam boiler with excess capacity
and heat accumulator
Steam boiler and turbogenerator
with excess capacity
Minimize capitalexpenses
Power plant has a free capacity in night hours
9
Model Primitives• Primitives are selected for the needs of architectural
configuration modelling – minimal required system breakdown
• Primitives are organised in several classifying structures simultaneously:– Hierarchy of equipment types – for model parameters
inheritance. “Catalog” logic.– Hierarchy of system’s functional organisation –
architectural configuration development. PBS logic for CAD systems.
– (Hierarchy of system’s spatial organisation – for future design stages. “Building-room-area” logic.)
10
Metamodel for modelling and model configuration
11
Classification of primitives and parameters in OWL
12
Primitive libraries in Modelica – inheritance (1)
13
Primitive libraries in Modelica – inheritance (2)
14
Primitive libraries in Modelica – inheritance (3)
1515Metamodel for configuration and simulation of a model
16
Configuration modelling
17
Configuration Power-1 in Modelica
18
Configuration Accum-1 in Modelica
1919Metamodel in ISO 24744 context
20
Data integration – ISO 15926Model_primitive_class
Equipment_model_classFunctional_element_model_class
Model_primitive
Steam_generation_island_model Heat_accumulating_equipment_model
#Heat_accumulator_model
21
Standards, languages and tools
• Metamodels – standards– ISO 24744 ?– i* Eclipse– ISO 15926 ?
• Modelling - languages– Class design
• UML Eclipse• OWL Protégé
– Primitive design• Таблицы Excel• OWL Protégé• Modelica OpenModelica,
Dymola
– Trade-off simulation• Modelica OpenModelica,
Dymola
i*
22
What to do next – «ideal program»
• Align class inheritance in various models – set theory classes, object-oriented programming classes
• Finalise the list of metamodel standars and select tools to integrate
• Map selected data models (metamodels) to ISO 15926 (submit standard classes to RDL)
• Select a repository supporting:– 15926 data model– Model configuration management
• Tool integration–15926 adaptors• Real program?
– Model repository + manual configuration control? Impossible to do with hundreds of classes.
– Migrate from standard to standard and change repositories (i.e. Excel – Protégé – Dymola+SVN)? To loose variety of viewpoints.
22
