Interoperability, Architecture And Architectural Frameworks. Rob Dobson Rob Dobson & Associates Pty Ltd

Transcription

1 Interoperability, Architecture And Architectural Frameworks Rob Dobson Rob Dobson & Associates Pty Ltd 1

2 Large Interoperability Late 1980s Large systems evolved independently not designed to be integrated with each other Soldiers using pay phones to communicate 1991 Gulf war large systems not working with each other No way to compare architectures with each other no standard lexicon or architectural representation No practical way to integrate large systems 1996 C4ISR Architectural Framework released. 2

3 DoD Architectural Framework The original intent of the DoDAF was to encourage the use of system engineering methodologies to develop architectures Steven Dam - original C4ISR AF development team member that Engineering is the key to developing architectures and that DoDAF is only serves as a means of comparison The DoDAF was developed to compare architectures. It is not an architecture or methodology to develop architectures 3

4 The Situation 4

5 I Have No Equal (fact) I Prefer Sugar What do the words actually mean? 5

6 Design Definition The process of defining the architecture, components, interfaces, and other characteristics of a system or component; and the result of the process (IEEE ). Software architecture represents the embodiment of the earliest set of design decisions about a system Software Architecture: An Executive Overview Technical Report CMU/SEI-96-TR-003 ESC-TR February

7 Architecture Definition Consistency The structure of components, their relationships, and the principles and guidelines governing their design and evolution over time. (DoD Integrated Architecture Panel, 1995) Architecture is the fundamental organisation of a system embodied in its components, their relationship to each other, and to the environment, and the principles guiding its design and evolution. IEEE Standard (IEEE Recommended Practice for Architectural Description of Software- Intensive s) Both of these definitions cover the design and evolution for both the present and the future. They are suitable for of s architectures. 7

8 Architecture Definition Consistency The software architecture of a program or computing system is the structure or structures of the system, which comprise the software elements, the externally visible properties of those elements, and the relationships among them. (Bass, L.; Clements; P. & Kazman, R. Software Architecture in Practice, Second Edition. Boston, MA: Addison-Wesley 2003.) This definition does not explicitly bring out the principles and guidelines for design and evolution. See and Software Architecture Reconciliation Mark W. Maier 8

9 Conceptual Model of Architectural Description (IEEE ) fulfills 1..* Mission Environment influences inhabits has an Architecture has 1..* is important to 1..* identifies 1..* used to cover 1..* is addressed to 1..* has 1..* Stakeholder selects 1..* described by 1 conforms to Architectural Description Concern Viewpoint View Library Viewpoint provides participates in organised by 1..* Rationale 9 Model

10 Architecture Documentation Compliance Documenting the architecture of each system in the same manner will not in itself achieve interoperability Rules Rules Rules 10

11 Hierarchical Views of Architecture External Rules of s Rules Rules SOS Rules For all systems In SoS Determines Interoperability Rules Subsystem Components must comply with: Rules SoS Rules External Rules 11

12 A May Belong to a Number of Domains Each system must comply with the architectural rules for every Domain of which it is a member Air Tactical Comms Domain Maritime Tactical Comms Domain Link-11 Domain ADF Tactical Comms Domain Link-16 Domain 12

13 Architectural Compliance Each system must comply with the architectural rules for every domain of which it is a member Determine which domains the system is a member of Determine the architectural rules from each domain that impact on the system Ensure compliance with these architectural rules 13

14 SoS NCW Capability C2 C2 AD N AD Network Architecture Description Deconfliction Enablers Enablers ISR AD Multi Sensor Trackers E AD ISR Sensors Effectors 14

15 Information Exchanges OCD/FPS for Self Propelled Gun Performance of vehicle. Speed, terrain, range, etc Performance of gun. Range, accuracy, rate of fire etc Performance of projectiles Re supply Refuel etc Support for human habitation etc 15

16 Architecture Compliance Impact on /Product OCD/FPS Communications complies with Effector Domain (and Network) communications architectures LAN Command & Control complies with C2 Domain architecture 16

17 Interoperability, Architecture And Architectural Frameworks Rob Dobson Rob Dobson & Associates Pty Ltd PO Box 9113 Deakin ACT 2600 Mobile: