The document discusses the challenges faced in systems engineering as presented at the RUSEC 2010 workshop in Moscow, emphasizing a need to update the INCOSE SE Vision 2020 through a bottom-up approach. It identifies five focus areas for systems engineering, including education, processes, and the integration of ideas from software engineering. The document outlines various methods and models for effective systems engineering, including those that pertain to project management, lifecycle management, and the roles of systems engineers.

1. Systems Engineering ChallengesRuSEC, Moscow, 23-24 of September, 2010Russian ViewAnatoly LevenchukTechInvestLab.ru, presidentINCOSE Russian Chapter, presidentailev@asmp.msk.suVersion 0.3 (27-aug-2010)

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

3. 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.”

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

5. Challenges from Current INCOSE SE VISION 2020INCOSE-TP-2004-004-02, V2.03, september 2007http://incose.org/ProductsPubs/pdf/SEVision2020_20071003_v2_03.pdfFive focus areas:Global Systems Engineering EnvironmentSystems and their NatureSystems Engineering ProcessesModels and Model-Based Systems EngineeringSystems Engineering EducationLet’s apply “Corrections Early in Lifecycle” principle:It needs to be updated!3

6. SE Challenges Focus AreasSystems engineering is a method, so we will use ISO 24744 as metamodel!4Global Systems Engineering Environment: meta-levelSystems and their Nature Systems Engineering ProcessesModels and Model-Based Systems EngineeringSystems Engineering Education

7. Meta-level (SE as a whole)SE vs. “Plain Engineering”, Art, Science.

8. Systems thinking (notions of System, System-of-Systems, holon, etc.)

9. SE Pragmatic (mitigating risks only vs. positive value adding).

10. Let’s borrow ideas from software engineering immediately, not after 10-15 years delay.

11. «Brave new SE» (a blend of model-based, semantically-enabled, cost-based, generative, SoSetc.) vs. “traditional SE”.

12. Demystification of “SE Art”: SE Knowledge discovery vs. SE Knowledge design (Engineering of Systems Engineering).

13. 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).

14. SE Ontology (System-of-Systems debate, 4D-debate, etc.).

15. SE Vocabulary (national/industry specific).

16. Industry-specific adoptions of SE. «Defense accent» of SE.5

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

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

19. Project Management in SE (inside or outside)?

20. What school of project management (PMBoK, PRINCE2, P2M, TOC, LastPlanner, constraints planning, etc.)?

21. TimeCycle methods with Integral Teams, Virtual Collaboration, etc.6

22. WorkUnitKinds(SE disciplines, practices, processesetc.)Traditional set for modern (model-based, semantically-enabled, cost-based, generative, etc.) SE :requirements engineering

23. safety and security engineering

24. Engineering of system architecture

25. Design

26. Configuration management

27. Integration

28. Verification and Validation

29. …..Or completely new set of disciplines?!TBD (e.g. High-level modeling)

30. TBD (e.g. Low-level modeling)

31. TBD (Generative manufacturing)

32. …7

33. WorkProductKindsMegamodel as first class WorkProductKind (configuration management of megamodel)System of Systems / Family of SystemsTechnology Platform/Generation and technology as system-of-interestHuman-based system (including enterprise engineering)8

34. ModelKinds, Languages (Metamodels), NotationsMultiparadigm modeling (SysML, ModelicaML, OPDM, knowledge representation languages)

35. Engineering/Architecture Metamodels/Frameworks (UPDM etc.)

36. Engineering DSLs (like P&ID) vs. Universal Engineering Languages (like SysML or AADL)

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

38. Specific metamodels for SE disciplines:

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

40. Cost models

41. Engineering of system architecture (UPDM, MFESA etc.)

42. Generative design

43. Assurance case, design rationale and other reasoning capture models9

44. ProducerKindsPeople

45. 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?

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

47. Tools

48. 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

49. RuSEC 2010: Workshop Recipe11

50. Open DiscussionKirillLisVictor Nikolenko…12