RT 24 - Architecture, Modeling & Simulation, and Software Design

RT 24 - Architecture, Modeling & Simulation, and Software Design Dennis Barnabe, Department of Defense Michael zur Muehlen & Anne Carrigy, Stevens Institute of Technology Drew Hamilton, Auburn University Russell Peak, Georgia Tech 1

Context The client is producing software-intensive, distributed systems in short development cycles (90 day increment spins) The DoD JCIDS process requires the documentation of systems in the form of certain DODAF products Occasionally this documentation is created after the fact and not as a basis for Modeling & Simulation or software development (notion: coding is faster than architecting) Effort spent on architecture development is essentially wasted, since architecture products are not used for value-added delivery, and architecture models and code evolve separate from each other 2

Req. Mgmt. Environment Development Environment 5 1 Architecture Environment 6 2 Coding Environment Simulation Environment 8 4 3 Execution Environment 7 Runtime Environment 3

Challenge Investigate the integration of Architecture models in the Modeling & Simulation and Software Design and Development Process Develop a methodology that: Identifies those architecture products that are relevant for the design of softwareintensive systems Provides guidance as to the sequence in which these models should be created Provides guidance as to the methods that should be used when creating these models Provides guidance as to the use of the recommended methods Evaluate the methodology against tool capabilities available to the client Particular focus on tool extensions (UPDM, SysML, SoaML, BPMN) Leverage best of breed architecture methodologies Provide tooling to support the methodology 4

DoDAF 2.0 Modeling Language captures Information used to describe matches DoDAF View DoDAF 2 MetaModel Elements captures/ represents 5

How Good is a Language? Language Quality improved by Ontological Clarity improved by Ontological Completeness reduced by reduced by reduced by reduced by Construct Overload Construct Redundancy Construct Excess Construct Deficit 6

Benchmarking a Language ML redundancy Key deficit BWW ML Set of constructs described in the BWW model Set of constructs comprising the Modelling Language overload Construct described in the BWW model Modelling language construct BWW Baseline Ontology excess Modeling Language! 7

Mapping Options Modeling Language (i.e. Type) to DoDAF View Coarse-grained Good for initial assessment Modeling Language Construct to DoDAF 2.0 MetaModel Entry Fine-grained May help in tailoring language 8

DM2 Concepts 9

Example: DoDAF 2.0 10

Example: BPMN BPMN MetaModel DoDAF 2.0 MetaModel 11

Mapping SysML to DoDAF 2.0 DoDAF V2.0 Models OV-1 OV-2 OV-3 OV-4 OV-5a SysML s Requirement State Machine Use Case Block Definition Internal Block Parametric Package OV-5b Activity OV-6c Sequence 12

Mapping SysML to DoDAF 2.0 DoDAF V2.0 Models SV-3 SV-2 SV-1 SV-4 SV-5a SV-5b SV-6 SysML s Requirement Activity Sequence State Machine Use Case Block Definition Internal Block Parametric Package 13

Understanding JCIDS 14

DoDAF 2.0 Product Initial (ICD) Development (CDD) Production (CPD) OV-1 (Concept of Operations) X X X AV-1 (Project Overview) X X AV-2 (Integrated Dictionary) X X OV-2 (Operational Resource Flow Description) X X OV-3 (Operational Resource Flow Matrix) X X OV-4 (Organizational Relationship Chart) X X OV-5a (Operational Activity Decomposition Tree) X X OV-5b (Operational Activity Model) X X OV-6c (Event-Trace Description) X X SV-2 (Systems Resource Flow Description) X X SV-4 (Systems Functionality Description) X X SV-5a (Operational Activity to Systems Function Matrix) X X SV-5b (Operational Activity to Systems Matrix) X X SV-6 (Systems Resource Flow Matrix) X X StdV-1 (Standards Profile) X X StdV-2 (Standards Forecast) X X DIV-2 (Conceptual Data Model) DIV-3 (Conceptual Data Model) X X 15

Dependencies (DoDAF 2.0 Spec) NOTE 1: Developed iteratively as the Architecture Description is developed. NOTE 2: The AV-2 presents all the metadata used in an architecture. An AV-2 shows elements from the DoDAF Meta-model that have been described in the Architectural Description and new elements (i.e., not in the DM2) that have been introduced by the Architectural Description. parallel relationship completion order Viewpoint may/may not be required NOT a JCIDS Requirement SvcV- 10c SvcV- 10b SV- 10c SV- 10b DIV- 3 SvcV- 6 CVx SV- 6 SvcV- 4 SvcV- 9 DIV- 1 SV- 9 PV- 1 OV- 4 DIV- 2 StdV- 2 OV- 6c SV- 4 SvcV- 8 AV- 2 OV- 3 OV- 2 SV- 8 SvcV- 2 NOTE 2 NOTE 1 AV- 1 OV- 1 OV- 6a OV- 6b OV- 5b CV- 6 OV- 5a SV- 5a SV- 5b SV- 1 SV- 2 SvcV- 1 StdV- 1 SV- 3 16

Modeling & Simulation 17

Modeling & Simulation Simulation Model Shared Conecepts Implement 18

Core Description realized through Activity/ Process/ Function performed by Resource (Person/ System) input/output Resource (Data) 19

Big Picture Objective captured in Core Description used for Review influences aligns with Design captured in sets criteria for Implementation results in used for Detailed Model used for Simulation 20