UPDM and SysML for Systems Engineers.

Transcription

1 UPDM and SysML for Systems Engineers Graham Bleakley, IBM Copyright IBM Corporation 2010

2 Report Documentation Page Form Approved OMB No Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington VA Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. 1. REPORT DATE REPORT TYPE 3. DATES COVERED to TITLE AND SUBTITLE UPDM and SysML for Systems Engineers 5a. CONTRACT NUMBER 5b. GRANT NUMBER 5c. PROGRAM ELEMENT NUMBER 6. AUTHOR(S) 5d. PROJECT NUMBER 5e. TASK NUMBER 5f. WORK UNIT NUMBER 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) IBM Corporation,1 New Orchard Rd,Armonk,NY, PERFORMING ORGANIZATION REPORT NUMBER 9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR S ACRONYM(S) 12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release; distribution unlimited 11. SPONSOR/MONITOR S REPORT NUMBER(S) 13. SUPPLEMENTARY NOTES Presented at the 2012 DoD Enterprise Architecture Miami, Fl, April 30 - May 3, 2012, Government or Federal Purpose Rights License 14. ABSTRACT 15. SUBJECT TERMS 16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT a. REPORT unclassified b. ABSTRACT unclassified c. THIS PAGE unclassified Same as Report (SAR) 18. NUMBER OF PAGES 23 19a. NAME OF RESPONSIBLE PERSON Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18

3 Agenda This presentation will cover Describe how the views are related Identify the main viewpoints relevant for the Enterprise Architecture and Systems Engineering i phases of development Show the patterns across the views and s Discuss a generic workflow Points for discussion on UPDM/SysML modelling 2 Copyright IBM Corporation 2012

4 DoDAF 2.0 s Capability :- Capture the capabilities that the enterprise is expected to realise and shows how they are deployed to organizations (prefix CV) Operational :- Contains the views required to describe the Operational and high h level l functional aspects of the architecture t (prefix OV) Service :- Captures the views required to specify of the Services (i.e. interface, no implementation) required to support the Operational objectives of the architecture (prefix SvcV) ALL View wpoint Data an nd Inform ation Viewpoi int Standard s Viewpo oint Capability i Operational Service System Pro oject Viewp point 3 Copyright IBM Corporation 2012

5 DoDAF 2.0 s Systems :-Captures the specification of the Systems that are required to be implemented or that already exist that help achieve the operational objectives (prefix SV) Project P j t :- i Maps the enterprises to the projects and organisations that will realise the capabilities through the development of systems and services (prefix PV) AL LL Viewpo oint Data and Informatio on Sta andards Capability Operational Service System Projec ct Viewpoin nt 4 Copyright IBM Corporation 2012

6 DoDAF 2.0 s Standards :-Contains all the information relating to the standards that constrain the other 3 viewpoints (prefix by StdV) All :- Contains the summary information about the architecture being developed d including the data dictionary (prefix by AV) ALL Viewpoin nt Dat a and Inf formation View wpoint Stand dards Vie ewpoint Capability Operational Service System Project 5 Copyright IBM Corporation 2012

7 Model Element interaction Across Views Separation of Elements and Views/s Some elements seen in multiple views Some views ties the viewpoints together e.g. SV Copyright IBM Corporation 2012

8 View and interrelationshhips The s are not independent but are heavily interrelated Each face of Cube represents a viewpoint Each window a separate view or product Model Elements internal to cube used by multiple views Views can act as Filters on the information in the architecture (OV-3, SV-5) Diagrams allowing you to create the information that t populates the architecture (SV-1, OV-2) OV-1 Capability Views CV-6 OV-3 CV-2 OV-2 Operational Views OV-5 7 Copyright IBM Corporation 2012

9 relationships UPDM DoDAF is a set of traceability matrices Systems and Services support and implement Operational elements Services expose capabilities (service as an interface) Operational elements (activities) map to capabilities Capabilities are delivered by Projects Systems and Services are the realized by projects Everything constrained by standards These relationships are captured in the various matrix views Stand dards View wpoint Capability Maps to Implements Constrained by Operational Systems Delivered by Exposes Supports Project Services Data and Information, captures data models at different level of abstraction All, i encompasses summary information i and all data definitions in the architecture 8 Copyright IBM Corporation 2012

10 Enterprise View of UPDM DoDAF p p Used by Planning JCIDS Operations Portfolio management For Capability management Operations Planning Develop High level requirements for prime suppliers Still need the All view, Standards view Parts of the Data and Information view Stand dards View wpoint Capability Maps to Implements Constrained by Operational Systems Delivered by Exposes Supports Project Services Data and Information, captures data models at different level of abstraction All, i encompasses summary information i and all data definitions in the architecture 9 Copyright IBM Corporation 2012

11 The Systems Engineering View of UPDM DoDAF Used by Portfolio management Operations planning Defense Acquisition System Systems Engineering teams In forces Primes/Tier ones Provides requirements to engineering teams Still need the All view, Standards view Parts of the Data and Stand dards View wpoint Capability Maps to Implements Constrained by Operational Systems Delivered by Exposes Supports Project Services Data and Information, captures data models at different level of abstraction All, i encompasses summary information i and all data definitions in the architecture 10 Copyright IBM Corporation 2012

12 Key relationships for Systems Engineering Resources exchanged through information and data exchanges Resource is almost anything in the architecture EnterprisePhase Exhibits Capability Trace to Exposes Performer Performs Activity (Operational) Supports Service Interface Exchanges Resources Produces/ Consumes Implements Exchanges Performs Activity System (System) Activities 11 Copyright IBM Corporation 2012

13 Patterns in the Framework Capability Operational Systems Services Core Views OV-2 SV-1/2 SvcV-1/2 Structure (IBDs) OV-5 SV-4 SvcV-4 Behaviour (activity based) OV-3 SV-3/6 SvcV-3/6 Data exchange Summarys (Table/Matrix views) CV-6/7 SV-5a/b SvcV-5a Traceability matrices Supporting Views OV-6b SV-10b SvcV-10b Behaviour (statemachines) OV-6c SV-10c SvcV-10c Behaviour (sequence diagrams) 12 Copyright IBM Corporation 2012

14 Key View dependencies for systems engineering Source where element is shown Target where the element is referenced from Dashed lines show trace references CV-1 Traceability matrices CV-6, CV-7, SV- 5a/b, SvcV 5 CV-2 Environment Structure OV-2, SV-1, SVCV-1 Behaviour OV-5,SV-4,ScvV-4 5SV4S V4 CV-4 Sequence Diagrams, OV6, SV- 10c,SvcV-10c Info exchanges OV-3,SV-3/6,SvcV-3/6 3/6 SvcV 3/6 CV-6 Trace matrices CV-7 SV-4 SV-5a/b OV-5 SvcV-5 SvcV-1 SV-3/6 OV-3 SvcV-3/6 SV-10c SV-1/2 OV-6c OV- 2/4 SvcV- 10c SvcV-4 13 Copyright IBM Corporation 2012

15 High level workflow (core) Develop capability views Develop Capability views, CV-1, CV-2, CV-3 Enterprise visions Capability hierarchy and dependencies Develop Operational views Behavior, structure, Derive data exchange matrices Trace back to capabilities Develop systems/service views Develop Operational views, OV-2, OV-3, OV-4, OV-5 Trace back Activities (Operational) to Capabilities (CV-6) Develop System View Develop System View SV-1/2, SV-3, SV-4s, ScvV-1 1, ScvV-4s 4s, Behavior, structure, SV-6 Derive data exchange matrices Trace back t Systems to operations that they Trace back Systems Trace back implement and Activities(ServiceFuncti Trace back Services to the Activities(SystemFucnti ons) to Operational Operations they support ons) to Operational Views (SvcV-5) and Views (SV-5a/b) Capabilities (CV-7) Capabilities they expose 14 Copyright IBM Corporation 2012

16 The generic workflow applied to the OVs Step-1 BlackBox behavior Step-3 Allocate behavior to structure (WhiteBox) OV-5 OV-3 Step-2 Define Structu OV- 2/4 OV- 6c 15 Copyright IBM Corporation 2012

17 The generic workflow applied to the OVs Step-3 Allocate behaviour to structure (WhiteBox) Step-6 generate OV-3 Information exchange summary OV- 6c OV- 2/4 OV-5 OV-3 Step-4 4Define Scenarios Optional Step-5 Define Information Exchanges 16 Copyright IBM Corporation 2012

18 Specifier:DoD/ MOD/Agencies/Tier 1 CV/StV PV/Acv Views Views Architecture and Implementation workflow Operational Views System Views Actual Delivery Timescales Expected Delivery Timescales Implementers: Tier1/Tier2 Systems/Software Engineering Systems Systems Engineering System Architecture Baseline Requirements Analysis System Analysis & Design Test Scenarios System Acceptance (Sub-)System Integration & Test SW Analysis & Design Module Integration & Test Software Engineering SW Implementation &U Unit itt Test 17 Copyright IBM Corporation 2012

19 Relating UPDM and SysML models Discussion Handling requirements In UPDM requirements driven from the level above Non functional requirements captured as constraints Also work with Parametric diagrams It is possible to import requirements into UPDM models and tie them to Capabilities 3 main options Keep SysML models as part of UPDM models Import parts of UPDM models directly into a SysML model Reference UPDM elements from SysML models Options as part of these are Embed SysML elements directly in the UPDM elements Ties the elements too closely into UPDM but I think there will be issues Separate out SysML models and trace to UPDM elements Keep to the patterns in UPDM re traceability to the upper levels 4 th option Separate UPDM and SysML models and trace through third party tool (i.e. DOORS) 18 Copyright IBM Corporation 2012

20 Relating UPDM and SysML models Discussion Keep SysML models as part of UPDM models Models become very large and monolithic Hard to maintain and manage 19 Copyright IBM Corporation 2012

21 Relating UPDM and SysML models Discussion Import parts of UPDM models directly into a SysML model Evolve the model with SysML elements End up with separate models Disconnect between the high level specification of a System in the UPDM model and the SysML Issues with the need to maintain consistency between the views Issues with pushing more detail up into the UPDM views as there will then be inconsistency in the detail and you may lose relations/dependencies to the elements at the higher level Interchange issue as you are replacing elements you may lose ownership of relationships (might be OK in the same tool, but XMI?) Need Diff-Merge capability for XMI? 20 Copyright IBM Corporation 2012

22 Relating UPDM and SysML models Discussion Reference UPDM elements from SysML models SV-1/2 SV-10c Maintain the consistency of the UPDM model Maintain the patterns of the UPDM structure in the SysML model Trace between SysML and UPDM easily End up with a number of Branch SysML models that reflect the lower level system structure Cannot use the UPDM elements as they are read only (Advantage) Initial proposal Combination of taking UPDM models by reference and importing the lower levels of the UPDM architecture and removing UPDM stereotypes Change to SysML elements Trace back to reference elements Gives the possibility of reuse and also shows the reference to original elements UPDM Systems Reference model SysML Systems Model Sequence/Stat emachines SV-3/6 SV-4 (Activity) Activity Tables/ma trix views IBDs/BDD s 21 Copyright IBM Corporation 2012

23 Summary Brief review of s How elements are related across the viewpoints Identification of patterns in the view points Generic Workflow UPDM and SysML 22 Copyright IBM Corporation 2012