Report to OMG by MDSD on A Review of SysML Submissions to OMG Sponsored by INCOSE MDSD- WG David Oliver, editor 2/8/06

History Initiated by MDSD; approved by Tech Board MOU approved; D-SIG for Systems Engineering voted by OMG (D. Oliver Liaison) D-SIG Co-chairs Sandy Friedenthal & Cris Kobryn Joint development of an underlying concept model by SysML, MDSD, & AP233 Teams Six reviews of SysML development sponsored by MDSD-WG

MDSD Language Goals Integrated Language – Graphic views are a projection of an integrated underlying schema or meta model. Not like Visio! Captures the concepts and relationships used by systems engineers Non-redundant ; 1 concept, 1 entity, 1 symbol (KISS) Compatible with the models in use for 35 years in Systems Engineering Bridge to Software Engineering

Review Results Review produced 35 major issues with 10 commentaries. Some reviewer issues favored SST submission; some favored SP submission Nine issues concluded that neither submission supported a fully integrated language. Examples of Problems: Concepts missing - Redundancy Weak Allocation - Defined Diagram Types Requirements Linking - Math Expression Definitions

A Missing Concept, “Build from” Pen Assemble Emergent Characteristics C From parts Pen Cap Pen Body Take Apart C C Plastic Cap Ring Top Base Cartridge Plastic Cap C C Receiver Slide Ink Tip Container Cap

Allocation Allocation supports Alternatives for Trade Studies! Environment Electric Power System Energy C-Waste G-Waste C Work Electricity Consumer Generator Generate Electricity Consume Electricity Allocate Electric Power System Allocate The Allocation defines all the information needed for a Block Interconnection Diagram or a Swim Lane Diagram Allocation supports Alternatives for Trade Studies!

Redundancy Block Diagram With Interconnection Consumer Generator Electricity Identical Allocate Allocate Electricity Generate Electricity Consume Electricity Activity or Behavior diagram

Defined Diagram Types Whole C Contradictory Part C Part A Part B It is necessary to place restrictions on Diagram Types or provide well formedness rules to prevent Contradictions and Nonsense Diagrams

Where from Here? Prove SysML by work on small projects with expert modelers Use Stakeholder Expertise in Evolving SysML, (see list of reviewers) Continue Interaction with INCOSE MDSD-WG Develop environments for Collaboration based on quantitative standards (Vivace Project in Europe)

Backup Slides Follow

Examples of Integration Problems The black diamond for decomposition says: when whole disappears then the parts disappear and when the parts disappear there is something left behind We need: build the whole from the parts; disassemble the whole into its parts Input/output has one name and symbol on activity diagrams and different name and symbol on block diagrams. We need activity allocated to blocks; then I/O (one name only) is what flows on interconnect

Examples of Integration Problems 3. Allocation merely labels or points to a relationship. We need allocation to cause the receiving entity to have new properties and relationships as recorded in the schema or meta-model. Allocation of activity onto blocks defines a new diagram, block diagram, with interfaces and flows established by the allocation.

Backup Slide

Vivace Collaborative Hub for Heterogeneous Enterprise Business and general drivers: Multiple Prime Businesses Heterogeneous business network environment Accessibility and traceability Cross functional development Ownership of data, methods and knowledge Methods Data Knowledge Tools (Software) Hardware Communication formats for context and content Products Processes (workflow) Business Models Work Package Objectives: Operational Environment for the Virtual Enterprise concept Supporting captured product use-cases with basic hub services Standards based information structures for content and context Prt. D Prt. E Prt. C OEM Prt. A SME Prt. B Collaboration Hub Virtual Enterprise Concept