1. Copyright © 2011 by Lockheed Martin Corporation INCOSE – MBSE Model Management Workshop 01/29/2011 John C. Watson Principal Member of Engineering Staff Lockheed Martin, MS2 Moorestown john.watson@lmco.com

2. P-11-0012 Watson – 2 Copyright © 2011 by Lockheed Martin Corporation Topics Environment Characteristics Information Characteristics Sharing Information Managing Change Model Integrity

3. P-11-0012 Watson – 3 Copyright © 2011 by Lockheed Martin Corporation What is MBSD? – Scope Formalizes the practice of systems development through the use of models Broad in scope –Includes multiple modeling domains across life cycle from SOS to component Results in quality/productivity improvements & lower risk –Rigor and precision –Communications among development team and customer –Management of complexity Life Cycle Support Vertical Integration Concept System Development Production Operations & Support

4. P-11-0012 Watson – 4 Copyright © 2011 by Lockheed Martin Corporation Software Models Hardware Models Q Q SET CLR S R Verification Models Performance, RMA, SWaP, Cost, etc.  G(s)U(s) Analytical Models The MBSE Information Base System Architectural Model MBSE Test Plan Analysis Spec

5. P-11-0012 Watson – 5 Copyright © 2011 by Lockheed Martin Corporation A Program SE Model Environment S/W … SoS Level → System Specification System Level → Subsystem Specification Subsystem Level → Component Specification Component Domain Model 1 H/W S/W … Component Domain Model 2 Spec 1 Spec n Spec 1 Spec 3 Spec n Spec 2Spec 1 Spec 6Spec 5Spec 4 …. Control Subsystem Model Weapon Subsystem Model Sensor Subsystem Model Spec 2Spec 1Spec n Combat System Model Spec S1 System of Systems Model... Component Level → Design → Implementation

6. P-11-0012 Watson – 6 Copyright © 2011 by Lockheed Martin Corporation Component Model Information Content of a Model Model Captures –Needs Analysis –Derived Architectural solution(s) –Design Rationale –Requirement Flow Down –Analytical Analysis Results –Test Results –Component Specifications Requirements Behavior Structure Parametric Component Spec n Component Spec 1 …. A System Architectural Descriptive Model Needs and Constraint Specifications Verification Models Analytical Models

7. P-11-0012 Watson – 7 Copyright © 2011 by Lockheed Martin Corporation Topics Environment Characteristics Information Characteristics Sharing Information Managing Change Model Integrity

8. P-11-0012 Watson – 8 Copyright © 2011 by Lockheed Martin Corporation Model Information Characteristics Large Complex Systems –Accessed by many engineers –Teams can be geographically dispersed –Often involves external contractors Legacy Systems –Legacy systems are document based 1st step is to re-establish in MBSD –The transition to MBSD is incremental –Need to support a hybrid MBSD and document based paradigms during transition

9. P-11-0012 Watson – 9 Copyright © 2011 by Lockheed Martin Corporation Model Information Characteristics Information Metadata –Discipline owner –Development maturity level –Classification level –Intellectual property –Baseline –List of associated change requests

10. P-11-0012 Watson – 10 Copyright © 2011 by Lockheed Martin Corporation Information Maturity Levels Creation –Changes frequently, minimal impact to external groups, check-in and out by individual Engineering Controlled –Supports collaboration across engineering disciplines –Peer reviews –Often establishes internal baselines Program Change Control –Formal company/program process –Driven from formal change requests –Release baselines impact company departments and customers Creation Engineering Controlled Program Change Control

11. P-11-0012 Watson – 11 Copyright © 2011 by Lockheed Martin Corporation Topics Environment Characteristics Information Characteristics Sharing Information Managing Change Model Integrity

12. P-11-0012 Watson – 12 Copyright © 2011 by Lockheed Martin Corporation Information Sharing and Security Information Classification Levels –Unclassified, Confidential, Secret, Top Secret –Sharing becomes difficult Isolated development environments Scrubbing and exporting unclassified information is risky Ensuring audience has appropriate clearance –US Citizens vs. Foreign Nationals –Is there a “Need to Know” Marking of Classified or Proprietary Information –Standards for documents, not for models –Includes diagrams, tables, text and model elements –What are model equivalents: Each paragraph is assigned a classification level Highest classification level on document page, marks page Highest classification level in document, marks document –E.g. – Multiplicities, value properties contained in a block

13. P-11-0012 Watson – 13 Copyright © 2011 by Lockheed Martin Corporation Inter-department Sharing Mechanics Did the change Impact another Department? Interdepartmental transformations –Determine if change warrants cross-department notification –Normalize information to destination environment –Within and outside engineering Use standard interchange language –Limit to selected items –Including diagrams Standard schema needed for information storage –Avoid vendor unique

14. P-11-0012 Watson – 14 Copyright © 2011 by Lockheed Martin Corporation Topics Environment Characteristics Information Characteristics Sharing Information Managing Change Model Integrity

15. P-11-0012 Watson – 15 Copyright © 2011 by Lockheed Martin Corporation The Change Management Environment Configuration Management (CM) software controls file access and change Models consist of one or more files –Guidelines for organizing high level directory structure Users are grouped and assigned access rights Users select files to check-out, modify and check-in Much like managing software data Usually avoid branching with models –Unlike software – textual and diagrams –Too difficult to merge diagrams –If two change requests touch the same data, Merge the two tasks

16. P-11-0012 Watson – 16 Copyright © 2011 by Lockheed Martin Corporation Program Change Control Process Supporting the Change Control Process –Evaluate change requests –Estimate cost of change –Isolate information involved in the change –Implement change –Conduct a review and adjudicate issues –Merge changes into existing baseline –Re-baseline A snapshot of the CM environment creates a baseline (entire or partial) Baselines are named and managed A baseline defines the revision level of each file at a point in time Collect and access Change Requests Implement Changes Review Change Merge Change into Current Baseline Baseline

17. P-11-0012 Watson – 17 Copyright © 2011 by Lockheed Martin Corporation Views A View supports a perspective for a set of stakeholders –E.g. – Requirement View Deliverable Document View –Model the document content Modelers can now see the target deliverables Removes dependencies between document and model organization Quicker document generation –Leveraged previous work and our own experiences Telescope systems modeling by SE^2 –Collaboration between the European Southern Observatory and the German Chapter of INCOSE –Subset of DocBook Defined a profile Should be an industry standard? –Observation – applicable to any desired view definition

18. P-11-0012 Watson – 18 Copyright © 2011 by Lockheed Martin Corporation Document Model Definition Define a package to contain the document Add packages that reflect the headings and organization of the document; e.g. chapters, section, TOC, etc. In each section add content; Local text Content from within the model Content external to the model Tables Drill into Scope Identify subsection Ordering of all elements can be explicitly specified with a «next» dependency element

19. P-11-0012 Watson – 19 Copyright © 2011 by Lockheed Martin Corporation Managing Change Day-to-Day Need to quickly examine changes relative to other baselines; –Both textual and diagram changes –Highlight only what has changed –Examine on the fly and for formal reviews

20. P-11-0012 Watson – 20 Copyright © 2011 by Lockheed Martin Corporation Example: Model Change Query 3 ← Hub-C 3100 ← 160 ← =120 ← Compare Query Baseline Compare: Starting at 3.4 To Now Included Change Requests: 445566 445567 445569 may

21. P-11-0012 Watson – 21 Copyright © 2011 by Lockheed Martin Corporation Changing Tools – Replacements and Upgrades Tools come and go –Protect investment by using standards –Avoid proprietary add-ins Tool upgrades can be difficult –Inter-tool compatibility –Script forward compatibility –If the tool is not backward compatible Upgrading a large team simultaneously Upgrading external contractors Upgrading customers

22. P-11-0012 Watson – 22 Copyright © 2011 by Lockheed Martin Corporation Topics Environment Characteristics Information Characteristics Sharing Information Change Management Model Integrity

23. P-11-0012 Watson – 23 Copyright © 2011 by Lockheed Martin Corporation Model Information Validation Large complex systems = large volumes of information Ripe for human error Needs to be scrubbed, validated and verified often What to validate? –Completeness –Correctness –Classification markings applied –Modeling guidelines are being followed –Missing data, large changes, etc. –Language compliance

24. P-11-0012 Watson – 24 Copyright © 2011 by Lockheed Martin Corporation Model Information Validation How to validate? –Model execution –Tool model check or custom scripts SysML provides a consistent well formed Information schema –Validate as you model –Validated periodically Daily, before check-in, before a review, before baseline –Collect metrics and trended

25. P-11-0012 Watson – 25 Copyright © 2011 by Lockheed Martin Corporation If You Can’t Measure It, You Can’t Manage It Model Metrics – The Need to Count To support Program and Engineering Management Metrics –To measure progress –To measure quality –To measure complexity –To support day to day model maintenance Collect, Track and Trend

26. P-11-0012 Watson – 26 Copyright © 2011 by Lockheed Martin Corporation Model Metrics How does an Architectural Models Contribute? –Contains the most current behavior, structure, requirements and parametric model elements –Provides objective evidence of Architecture and Design Artifacts Not just subjective data from human driven assessments –Provides an environment for “Continuous Assessment” Not just at the design maturity gates

27. P-11-0012 Watson – 27 Copyright © 2011 by Lockheed Martin Corporation Conclusion Large complex systems means we have large volumes of interrelated information How to manage large amounts of Information –Understanding the characteristics of the environment and the information –Knowing how to manage change –Effectively share information within engineering and across other departments –Maintain integrity via continuous validation

29. P-11-0012 Watson – 29 Copyright © 2011 by Lockheed Martin Corporation Layers –Applied to a diagram –Filters from a diagram what is not pertinent to the need –Simplifies diagram for the need –Enables maintaining fewer unique diagrams

30. P-11-0012 Watson – 30 Copyright © 2011 by Lockheed Martin Corporation Support Engineering Reviews Can’t expect all reviewers to access and navigate through the model –Export Review Package to common format, pdf, Word, html –Limit information to what is changing and supporting information One Solution used; –Identify and export review information to Word before and after change Use Compare feature two documents with change tracking turned on –Advantages – Everyone has Word Word has support to track comments and adjudicate changes – Disadvantages – Time consuming

31. P-11-0012 Watson – 31 Copyright © 2011 by Lockheed Martin Corporation Sharable SE Model Information Architectural Descriptions Interface Specifications System/Subsystem/Component Specifications Operational Behavior System Glossary Data Definitions Test Data and Results Analysis Tasks and Results Metrics To the models – BOM, design references, design test results SW Design SW Design Mechanical Design Mechanical Design Electrical Design Electrical Design Manufacturing Program Management Program Management Proposal Development Product Documentation Product Documentation Product Support Product Support

32. P-11-0012 Watson – 32 Copyright © 2011 by Lockheed Martin Corporation Working with External Contractors Large Programs often Collaborate with External Contractors Sometimes they are also competitors Expose only “Need to Know” Information Solutions: –Isolated a Model per contractor group –Shares only necessary Files –Use change control process to integrate internally

33. P-11-0012 Watson – 33 Copyright © 2011 by Lockheed Martin Corporation Sharing MBSE Information Base Across Disciplines System Architecture Information Base Test Data and Results Analysis Data and Results Operational Behavior Glossary of Terminology Data Definitions Architecture Description Interface Specifications Component Specifications SW Design SW Design Mechanical Design Mechanical Design Electrical Design Electrical Design Manufacturing Program Management Program Management Proposal Development Product Documentation Product Documentation Product Support Product Support Metrics To the model – BOM, design references, design test results

34. P-11-0012 Watson – 34 Copyright © 2011 by Lockheed Martin Corporation Measuring Change Impact S/W … Component Domain Model 1 H/W S/W … Component Domain Model 2 Spec 1 Spec n Spec 1 Spec 3 Spec n Spec 2Spec 1 Spec 6Spec 5Spec 4 …. Control Subsystem Model Weapon Subsystem Model Sensor Subsystem Model Spec 2Spec 1Spec n Combat System Model Spec S1 System of Systems Model... Verification Models Analytical Models Manufacturing Product Support Product Support Customer Program Management Program Management