MoDAF Update INCOSE. Martin Owen, VP Enterprise Architecture 28 September Telelogic AB

Transcription

1 MoDAF Update INCOSE Martin Owen, VP Enterprise Architecture 28 September

2 Agenda Telelogic and Defence Architectural Frameworks MoDAF - Key Issues Different Stakeholders for MoDAF Implementing MoDAF The Road Ahead 2

3 Telelogic and Defence Architectural Frameworks 1997 MoD commence use of DOORS for requirements Management 2001 Popkin launch C4ISR solution for System Architect 2004 Telelogic launch DoDAF solution for TAU 2005 Telelogic acquire Popkin DOORS formally integrated with System Architect MoDAF Solution developed across all Telelogic products MoD adopt DOORS for Requirements management First C4ISR Modeling Tool (System Architect) ue q i Un System Architect DoD deal! 2003 Corporate agreement for Telelogic tools across MoD community 2004 UML DoDAF (TAU) Telelogic Acquire Popkin and FocalPoint! ue q i Un 2005

4 MoDAF key issues MOD Architectural Framework modelling using six Viewpoint sets Strategic and Acquisition views support MOD processes and lifecycles MODAF extends existing best practice DoDAF It is being tailored to MOD processes and lifecycles Recognises different user communities (COIs) It will take a pragmatic approach Model all appropriate views Only model what is needed (based upon a core mandated set) 4

5 Different Stakeholders STRATEGIC OPERATIONAL TECHNICAL 5

6 Implementing MoDAF 6

7 Implementation issues Different users will have different information needs Different types of information, e.g. structural models, project data, capability data, etc. Different levels of abstraction Different presentation formats Different tools have different Sweet Spots MoDAF defines 40 architecture products there is no one size fits all solution All products are based on the same underlying architecture data model 7

8 The right capabilities DOORS Traceability tools allow auto-generation of many views Traceability from architecture to other requirements documents, e.g. URD, SRD, etc. Dedicated data capture and view generation facilities System Architect High level of abstraction for executive and operational community Collaborative and good for communication and operational level simulation Provides a path to implementation through links to TAU and UML TAU Detailed System View of World for technical community Comprehensive consistency and correctness checking Integrated dynamic simulation capabilities Provides implementation through UML2.0 notation All tools Template and profile support for the MoDAF meta-model enabling the toolset to speak the language of MODAF 8

9 Industry-proven tools for MoDAF DOORS Strategic (capability) and Acquisition views Traceability and matrix based OV and SV views Technical views System Architect Currently supports DoDAF Operational Views, System Views and Technical Views MoDAF support planned for 2006 TAU Diagrammatic Operational Views, System Views Generation of OV-3, SV-6 data exchange matrices Import of OV-3 matrix 9

10 System Architect for MODAF (Specification) 10

11 11

12 TAU for MODAF (Implementation) 12

13 MODAF Relationship to Operational Processes 13

14 MODAF Relationship to Acquisition Processes 14

15 Telelogic MODAF 3 Tier Architecture Enterprise MOD Framework View ERM view Telelogic Architecture Repository View DARS/CADM Repository s view of its information Local Tool Views Web/Office UML/Structured Tool s view of its data Simulation 15 Code

16 The Road Ahead 16

17 Telelogic MoDAF Solution Now Ongoing development around current draft MoDAF specifications Pilots underway December 2005 Telelogic MoDAF version 1.0 DOORS and TAU supporting MoDAF April 2006 Telelogic MoDAF version 2.0 System Architect supporting MoDAF Including Guidebooks FocalPoint support for Feature Analysis 17

18 Guidebooks Provide a visual path through using MoDAF Interacts with Telelogic Technology Provides Samples Best Practices Help Links to industry bodies 18

19 DOORS and TAU tool support for MoDAF 19

20 20