Sys ML adoption issues OMG Sys ML Roadmap

  • Slides: 12
Download presentation
Sys. ML adoption issues OMG Sys. ML Roadmap WG 2014 -04 -22 Uwe Kaufmann

Sys. ML adoption issues OMG Sys. ML Roadmap WG 2014 -04 -22 Uwe Kaufmann

Classification of issues Inventory SYSML – ADOPTION ISSUES Uwe Kaufmann Model. Alchemy Consulting 2014

Classification of issues Inventory SYSML – ADOPTION ISSUES Uwe Kaufmann Model. Alchemy Consulting 2014 Folie 2

MBSE Adoptions issues Source: Sys. ML Assessment & Roadmap Approach / SE DSIG •

MBSE Adoptions issues Source: Sys. ML Assessment & Roadmap Approach / SE DSIG • • • • • • Uwe Kaufmann Model. Alchemy Consulting 2014 More focus on mechanical engineering Provide more examples/guidance Availability of libraries of reusable models Availability of patterns Language stability Increased analysis capabilities A clear value assessment from using Sys. ML Model consistency Domain specific icons Support for continuum of models that support early concepts and more detailed formal models Agility of modeling Dynamic (i. e. simulation) and static analysis capabilities Capture of trade studies Reduce the number of ways things can be modeled. This is a source of confusion to modelers Ability to represent model in textual form Better handling of large number of requirements FMEA capabilities Consider industries which are not highly regulated Consider how to model humans Make the model invisible (transparent) to support other discipline engineers MDA for Sys. ML 3

Issues categorisation Categories may trigger different ways to resolve issues • Language issues –

Issues categorisation Categories may trigger different ways to resolve issues • Language issues – – • Integration issues – – – • Uwe Kaufmann Model. Alchemy Consulting 2014 Support for MBSE Modeling guidelines, procedural models (e. g. SYSMOD) … Organisational issues – – – • Model libraries, standard parts Reusability of models … Methodology issues – – – • Model Exchange PLM … Deployment / Implementation issues – – – • Constructs (e. g. mech. eng. ) Extensibility Domain adaptability … How MBSE changes enterprise development processes Transition process from „traditional“ SE to MBSE Stakeholder issues (probably a new dimension? ) … 4

Formerly presented in Man. TIS, March 2014 SE – PLM INTEGRATION Uwe Kaufmann Model.

Formerly presented in Man. TIS, March 2014 SE – PLM INTEGRATION Uwe Kaufmann Model. Alchemy Consulting 2014 Folie 5

Outcome of Gf. SE Workshop, Feb. 2014 – part 1 Requirements on PDM/ PLM

Outcome of Gf. SE Workshop, Feb. 2014 – part 1 Requirements on PDM/ PLM • Requirements on PDM-Tools from SE perspective: – Extension of Datastructures for SErelavant data including classes, relations, attributes – Extension of PDM-Systems to represent networked structures. – Persistency of relations between components over system borders. – Need to represent additional articfacts: Gf. SE = German chapter of INCOSE Workshop held Feb. 13 -14, Hannover, Germany Special session on PLM Integratioin; ~12 participants from Industry and Research Uwe Kaufmann Model. Alchemy Consulting 2014 • Requirements • Functions • System architectures – Support for Functional Mock-Ups (FMU). – Support for validation verification with model-based derivation of test cases. 6

Outcome of Gf. SE Workshop, Feb. 2014 – part 2 Requirements on (MB)SE-Tools •

Outcome of Gf. SE Workshop, Feb. 2014 – part 2 Requirements on (MB)SE-Tools • Requirements on (MB)SE-Tools from PDM/ PLM perspective: – Management of „Standard Model Libraries“ for Sys. ML; (subject to their availabilty ) – Versioning of models / partial models (incl. changecontrol) – Elaboration of a concept for model assemblies and reusability of models – Support for collaboration between modelers – Above mentioned model-managemant may require changes and / or extensions to the Sys. ML-language Uwe Kaufmann Model. Alchemy Consulting 2014 7

Outcome of Gf. SE Workshop, Feb. 2014 – part 3 Conclusion and further steps

Outcome of Gf. SE Workshop, Feb. 2014 – part 3 Conclusion and further steps • Solutions to the problem of versioning, collaboration, reusability exist for 3 DCAD (MCAD). • Suggestion to elaborate about the adoption of solutions from MCAD to SETools (eg. Team-Datamanager to enterprise PDM). • Elaborate on the question what functionality / information should be managed in PDM vs. the respective authoring systems (federative vs. central) • Development processes will change : -D Uwe Kaufmann Model. Alchemy Consulting 2014 8

SE – PLM integration, further aspects Thoughts about SEPLM integration Uwe Kaufmann Model. Alchemy

SE – PLM integration, further aspects Thoughts about SEPLM integration Uwe Kaufmann Model. Alchemy Consulting 2014 • Role of ALM (Application Lifecycle Managament) • Can OSLC fill the gap? • SE-Authoring tools (e. g. Sys. ML) be used as PLM configurator? 9

ROADMAP CONTRIBUTION Uwe Kaufmann Model. Alchemy Consulting 2014 Folie 10

ROADMAP CONTRIBUTION Uwe Kaufmann Model. Alchemy Consulting 2014 Folie 10

Next steps • Solicitation of contributors • Creation of a matrix putting categorized adoption

Next steps • Solicitation of contributors • Creation of a matrix putting categorized adoption issues in relation to stakeholders involved in the SE process • Elaboration of strategy paper on PLM / SE integration • 1 st milestone: – Boston OMG TC Meeting June 2014 – Draft roadmap Uwe Kaufmann Model. Alchemy Consulting 2014 11

Questions? Uwe Kaufmann Model. Alchemy Consulting 2014 12

Questions? Uwe Kaufmann Model. Alchemy Consulting 2014 12