Systems Engineering ChallengesRuSEC, Moscow, 23-24 of September, 2010

Anatoly LevenchukTechInvestLab.ru, president

INCOSE Russian Chapter, presidentailev@asmp.msk.su

Version 0.3 (27-aug-2010)

Russian View

Context

• INCOSE Russian chapter in 2009-2010 had biweekly regular meetings and one 2-day Workshop (March 2010) to discuss SE challenges.

• EuSEC 2010 chapter leaders meeting (May 2010): “INCOSE SE VISION 2020 should be updated by bottom-up procedure starting from local chapter’s visions of SE challenges. This work was already started by France and Russian chapters.”

• RuSEC 2010 (September 2010): Systems Engineering Challenges International Workshop in Moscow. We are here.

2

Challenges from Current INCOSE SE VISION 2020

Five focus areas:1. Global Systems Engineering Environment2. Systems and their Nature3. Systems Engineering Processes4. Models and Model-Based Systems Engineering5. Systems Engineering Education

Let’s apply “Corrections Early in Lifecycle” principle:

It needs to be updated!3

INCOSE-TP-2004-004-02, V2.03, september 2007http://incose.org/ProductsPubs/pdf/SEVision2020_20071003_v2_03.pdf

2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020

SE Challenges Focus AreasSystems engineering is a method, so we will use ISO 24744 as metamodel!

4

1. Global Systems Engineering Environment: meta-level2. Systems and their Nature 3. Systems Engineering Processes4. Models and Model-Based Systems Engineering5. Systems Engineering Education

Meta-level (SE as a whole)• SE vs. “Plain Engineering”, Art, Science.• Systems thinking (notions of System, System-of-Systems, holon, etc.)• SE Pragmatic (mitigating risks only vs. positive value adding).• Let’s borrow ideas from software engineering immediately, not after 10-15 years

delay.• «Brave new SE» (a blend of model-based, semantically-enabled, cost-based,

generative, SoS etc.) vs. “traditional SE”.• Demystification of “SE Art”: SE Knowledge discovery vs. SE Knowledge design

(Engineering of Systems Engineering).

• SE Knowledge modeling/capture and management: Situational method engineering (OMG SPEM, ISO 24744, SEMAT) and SE Method catalogs (method elements repositories – OPFRO) and BoK (BKCASE).

• SE Ontology (System-of-Systems debate, 4D-debate, etc.).• SE Vocabulary (national/industry specific).• Industry-specific adoptions of SE. «Defense accent» of SE.

5

StageKinds (TimeCycleKinds)

• TimeCycle (LifeCycle) management methods: Agile vs. Waterfall; Lean, Six Sigma and TOC in SE; etc.

• TimeCycles coordination for SoS, multi-contractor work (e.g. DEMO organization engineering framework).

• Project Management in SE (inside or outside)? • What school of project management (PMBoK,

PRINCE2, P2M, TOC, LastPlanner, constraints planning, etc.)?

• TimeCycle methods with Integral Teams, Virtual Collaboration, etc.

6

WorkUnitKinds(SE disciplines, practices, processes etc.)

Traditional set for modern (model-based, semantically-enabled, cost-based, generative, etc.) SE :

• requirements engineering• safety and security engineering• Engineering of system architecture• Design• Configuration management• Integration• Verification and Validation• …..

Or completely new set of disciplines?!• TBD (e.g. High-level modeling)• TBD (e.g. Low-level modeling)• TBD (Generative manufacturing)• …

7

WorkProductKinds

• Megamodel as first class WorkProductKind (configuration management of megamodel)

• System of Systems / Family of Systems• Technology Platform/Generation and

technology as system-of-interest• Human-based system (including enterprise

engineering)

8

ModelKinds, Languages (Metamodels), Notations

• Multiparadigm modeling (SysML, ModelicaML, OPDM, knowledge representation languages)

• Engineering/Architecture Metamodels/Frameworks (UPDM etc.)• Engineering DSLs (like P&ID) vs. Universal Engineering Languages (like SysML or

AADL)

• Semantic/ontology-based megamodel integration (Simantics, ISO 15926, etc.)

• Specific metamodels for SE disciplines:

– Requirements discovery/engineering (e.g. stakeholder models, GORE frameworks and standards, etc.)

– Cost models– Engineering of system architecture (UPDM, MFESA etc.)

– Generative design– Assurance case, design rationale and other reasoning capture models

9

ProducerKinds• People– Roles of systems engineer (requirements engineer, systems

architect, configuration manager, V&V authority, security and safety engineer etc.). How to build SE team with these roles?

– SE Education (continuous education: 1 year experience repeated 20 times should not count as “20 years of experience”)

• Tools– CAD/CAM/CAME/PLM/Wiki/Social networks/etc.: what tools

will support SE in 2020? Data-centric vs. Document-centric, Semantic vs. Vocabulary, Model transformation vs. Model editing, etc.

10

RuSEC 2010: Workshop Recipe

11

MBSE Models*Development process

* Life cycle cost*Requirements engineering

* Safety and securityOntology

and semantics

Situational method

engineering

Open Discussion

• Kirill Lis • Victor Nikolenko• …

12