Your SlideShare is downloading. ×
Model Integration for Systems Engineering
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Model Integration for Systems Engineering

1,206
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,206
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
34
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

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 Agroskin RuSEC 2010
  • 2. Life Cycle of a « Typical Design »
    • 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
    Concept Production Utilisation Retirement Development Concept Implementation Development Moderni sation Implementation Moderni sation Retirement
  • 3. Modernisation stage as a project Architecture trade-off analysis … Requirements engineering Goal model Technical-economic model Conceptual Design
    • Life cycle of a modernisation project :
    • 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 )
    Project’s modelling standard
  • 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 Recommendation s (OWL, RDF languages and notations) .
  • 6. Metamodel for model-based requirements engineering
  • 7. From wishes to requirements
    • Make 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 capital expenses 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 )
  • 15. Metamodel for configuration and simulation of a model
  • 16. Configuration modelling
  • 17. Configuration Power-1 in Modelica
  • 18. Configuration Accum-1 in Modelica
  • 19. Metamodel in ISO 24744 context
  • 20. Data integration – ISO 15926 Model_primitive_class Equipment_model_class Functional_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 .
  • 23. Thank you!
    • Victor Agroskin
    • [email_address]
    • +7 (495) 7 48-5388