Successfully reported this slideshow.
Your SlideShare is downloading. ×

Systems Engineering Challenges

Loading in …3

Check these out next

1 of 12 Ad

More Related Content

Similar to Systems Engineering Challenges (20)

More from Anatoly Levenchuk (20)


Recently uploaded (20)

Systems Engineering Challenges

  1. 1. Systems Engineering ChallengesRuSEC, Moscow, 23-24 of September, 2010<br />Russian View<br />Anatoly, presidentINCOSE Russian Chapter,<br />Version 0.3 (27-aug-2010)<br />
  2. 2. Context<br /><ul><li>INCOSE Russian chapter in 2009-2010 had biweekly regular meetings and one 2-day Workshop (March 2010) to discuss SE challenges.
  3. 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. 4. RuSEC 2010 (September 2010): Systems Engineering Challenges International Workshop in Moscow. We are here.</li></ul>2<br />
  5. 5. Challenges from Current INCOSE SE VISION 2020<br />INCOSE-TP-2004-004-02, V2.03, september 2007<br />Five focus areas:<br />Global Systems Engineering Environment<br />Systems and their Nature<br />Systems Engineering Processes<br />Models and Model-Based Systems Engineering<br />Systems Engineering Education<br />Let’s apply “Corrections Early in Lifecycle” principle:<br />It needs to be updated!<br />3<br />
  6. 6. SE Challenges Focus Areas<br />Systems engineering is a method, so we will use ISO 24744 as metamodel!<br />4<br />Global Systems Engineering Environment: meta-level<br />Systems and their Nature <br />Systems Engineering Processes<br />Models and Model-Based Systems Engineering<br />Systems Engineering Education<br />
  7. 7. Meta-level (SE as a whole)<br /><ul><li>SE vs. “Plain Engineering”, Art, Science.
  8. 8. Systems thinking (notions of System, System-of-Systems, holon, etc.)
  9. 9. SE Pragmatic (mitigating risks only vs. positive value adding).
  10. 10. Let’s borrow ideas from software engineering immediately, not after 10-15 years delay.
  11. 11. «Brave new SE» (a blend of model-based, semantically-enabled, cost-based, generative, SoSetc.) vs. “traditional SE”.
  12. 12. Demystification of “SE Art”: SE Knowledge discovery vs. SE Knowledge design (Engineering of Systems Engineering).
  13. 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. 14. SE Ontology (System-of-Systems debate, 4D-debate, etc.).
  15. 15. SE Vocabulary (national/industry specific).
  16. 16. Industry-specific adoptions of SE. «Defense accent» of SE.</li></ul>5<br />
  17. 17. StageKinds (TimeCycleKinds)<br /><ul><li>TimeCycle (LifeCycle) management methods: Agile vs. Waterfall; Lean, Six Sigma and TOC in SE; etc.
  18. 18. TimeCycles coordination for SoS, multi-contractor work (e.g. DEMO organization engineering framework).
  19. 19. Project Management in SE (inside or outside)?
  20. 20. What school of project management (PMBoK, PRINCE2, P2M, TOC, LastPlanner, constraints planning, etc.)?
  21. 21. TimeCycle methods with Integral Teams, Virtual Collaboration, etc.</li></ul>6<br />
  22. 22. WorkUnitKinds(SE disciplines, practices, processesetc.)<br />Traditional set for modern (model-based, semantically-enabled, cost-based, generative, etc.) SE :<br /><ul><li>requirements engineering
  23. 23. safety and security engineering
  24. 24. Engineering of system architecture
  25. 25. Design
  26. 26. Configuration management
  27. 27. Integration
  28. 28. Verification and Validation
  29. 29. …..</li></ul>Or completely new set of disciplines?!<br /><ul><li>TBD (e.g. High-level modeling)
  30. 30. TBD (e.g. Low-level modeling)
  31. 31. TBD (Generative manufacturing)
  32. 32. …</li></ul>7<br />
  33. 33. WorkProductKinds<br />Megamodel as first class WorkProductKind (configuration management of megamodel)<br />System of Systems / Family of Systems<br />Technology Platform/Generation and technology as system-of-interest<br />Human-based system (including enterprise engineering)<br />8<br />
  34. 34. ModelKinds, Languages (Metamodels), Notations<br /><ul><li>Multiparadigm modeling (SysML, ModelicaML, OPDM, knowledge representation languages)
  35. 35. Engineering/Architecture Metamodels/Frameworks (UPDM etc.)
  36. 36. Engineering DSLs (like P&ID) vs. Universal Engineering Languages (like SysML or AADL)
  37. 37. Semantic/ontology-based megamodel integration (Simantics, ISO 15926, etc.)
  38. 38. Specific metamodels for SE disciplines:
  39. 39. Requirements discovery/engineering (e.g. stakeholder models, GORE frameworks and standards, etc.)
  40. 40. Cost models
  41. 41. Engineering of system architecture (UPDM, MFESA etc.)
  42. 42. Generative design
  43. 43. Assurance case, design rationale and other reasoning capture models</li></ul>9<br />
  44. 44. ProducerKinds<br /><ul><li>People
  45. 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. 46. SE Education (continuous education: 1 year experience repeated 20 times should not count as “20 years of experience”)
  47. 47. Tools
  48. 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.</li></ul>10<br />
  49. 49. RuSEC 2010: Workshop Recipe<br />11<br />
  50. 50. Open Discussion<br />KirillLis<br />Victor Nikolenko<br />…<br />12<br />