1 Object Oriented Development For DoDAF System of Systems Stanley P. Stanilka The Boeing Company...

1

Object Oriented Development Object Oriented Development For DoDAF System of SystemsFor DoDAF System of Systems

Stanley P. StanilkaStanley P. Stanilka

The Boeing CompanyThe Boeing Company

Integrated Defense SystemsIntegrated Defense Systems

[email protected]@boeing.com

2

DoDAF System of SystemsDoDAF System of Systems

The Department of Defense Architecture Framework The Department of Defense Architecture Framework (DoDAF) provides architecture examples for modeling (DoDAF) provides architecture examples for modeling complex system of systems within the network centric complex system of systems within the network centric global battlespace theater.global battlespace theater.

DoD Architecture Framework, Version 1.0, United States DoD, 9 February 2004

BackgroundBackground

3

An architecture description is a representation of a defined domain, as of a current or future point in time, in terms of its constituent parts, what those parts do, how the parts relate to each other and to the environment, and the rules and constraints governing them.

An architecture description is a representation of a defined domain, as of a current or future point in time, in terms of its constituent parts, what those parts do, how the parts relate to each other and to the environment, and the rules and constraints governing them.


DoDAF Architecture Framework states that:DoDAF Architecture Framework states that:

4

DoDAF Architecture Framework ViewsDoDAF Architecture Framework Views


5

Complex System Of SystemsComplex System Of Systems

Satellite

CityEth

ern

et

Satellite Satellite

Comm. Tower

Radar Tower

6

Government Political ProcessesGovernment Political Processes

Complex Communications SystemsComplex Communications SystemsComplex Hardware & SoftwareComplex Hardware & Software

Complex Security SystemsComplex Security Systems

Complex Computing SystemsComplex Computing Systems

Many CorporationsMany Corporations

Complex Military HardwareComplex Military Hardware

Many UsersMany UsersMany SuppliersMany Suppliers

Demographic ChallengesDemographic ChallengesGeographic ChallengesGeographic Challenges

Complex System Of SystemsComplex System Of Systems

Airframe

Hydraulic System

Electrical System & Wiring

Fuel & Powerplant

Avionics Systems

Rotor System

Dynamic Drive System

Flight Control System

Avionics Components & Mission Equipment Components

ComplexityComplexity

4+ Million Lines of Code

48,000 parts

Satellite

CityEth

ern

et

Satellite Satellite

Comm. Tower

Radar Tower


10

DoDAF FrameworkDoDAF Framework- Proposes Structural Analysis - Proposes Structural Analysis - Contains Mostly Static Constructs- Contains Mostly Static Constructs

Unified Modeling / Object Oriented Methods Unified Modeling / Object Oriented Methods- Proposes Structural & Behavioral Analysis- Proposes Structural & Behavioral Analysis- Is Process Regimented- Is Process Regimented

The Two Most Common Methods That The Two Most Common Methods That Systems Engineers Will Use To Model Systems Engineers Will Use To Model Complex SystemsComplex Systems

Many INCOSE Papers have been published on Many INCOSE Papers have been published on Object Oriented Systems Engineering MethodsObject Oriented Systems Engineering Methods

11

The models mandated by the DoDAF do not always The models mandated by the DoDAF do not always align with hardware & software development align with hardware & software development methods and associated production processes utilized methods and associated production processes utilized in commercial enterprises (industry) who position in commercial enterprises (industry) who position their products for acquisition into the network centric their products for acquisition into the network centric military markets. military markets.

This is especially true for software development This is especially true for software development where object oriented analysis and design methods where object oriented analysis and design methods have become entrenched as an industry standard.have become entrenched as an industry standard.

DilemmaDilemma

12

Object Oriented Development For Object Oriented Development For DoDAF Centric Systems of SystemsDoDAF Centric Systems of Systems

Problem SummaryProblem Summary

When applied to the analysis and design of network When applied to the analysis and design of network centric systems of systems, object oriented techniques centric systems of systems, object oriented techniques do not typically support architectural modeling or do not typically support architectural modeling or integration analysis at the system level.integration analysis at the system level.

Rather, OO techniques tend to focus on lower level Rather, OO techniques tend to focus on lower level modular software development at the component level.modular software development at the component level.

ThereforeTherefore

How might OO techniques integrate with the DoDAF How might OO techniques integrate with the DoDAF for the design and development of network centric for the design and development of network centric systems of systems?systems of systems?

13

The Land Warrior SystemThe Land Warrior System The Land Warrior System was utilized in this case study.The Land Warrior System was utilized in this case study.

– The Land Warrior described in this case study is a hypothetical The Land Warrior described in this case study is a hypothetical rendition of a network centric battlespace situation. rendition of a network centric battlespace situation.

– The Land Warrior system was described and analyzed using UML The Land Warrior system was described and analyzed using UML techniques and compared to all DoDAF views.techniques and compared to all DoDAF views.

UMLUML DoDAF ViewsDoDAF Views

Requirements Use Case AnalysisRequirements Use Case Analysis All Views AV-1 & AV-2All Views AV-1 & AV-2

Operational Views OV-1 through OV-7Operational Views OV-1 through OV-7

Requirements Noun Parse and Object Class Requirements Noun Parse and Object Class IdentificationIdentification

Systems Views SV-1 through SV-11Systems Views SV-1 through SV-11

Technical Views TV-1, TV-2Technical Views TV-1, TV-2

Domain ModelsDomain Models

Sequence & Collaboration DiagramsSequence & Collaboration Diagrams

StatechartsStatecharts

14

Object OrientedAnalysis

UMLCollaboration& Sequence

Diagrams

DoDAFFramework and

Guidelines

Use Case /Requirements

Analysis

ObjectOrientedSystems

EngineeringMethods(OOSEM)

Behavioral &FunctionalModeling

DesignPatterns

DomainModeling

LogicalArchitecture

Views

Object Oriented Network CentricSystems Of Systems

GAP Analysis Is Needed To BetterGAP Analysis Is Needed To BetterUnderstand How OO Techniques Can Be Understand How OO Techniques Can Be Applied Within The DoDAF FrameworkApplied Within The DoDAF Framework

15

UML Iterative Process In Contrast To DoDAF ConstructsUML Iterative Process In Contrast To DoDAF ConstructsFinding No. 1Finding No. 1

Grady Booch states “good people with a good process will Grady Booch states “good people with a good process will outperform good people with no process every timeoutperform good people with no process every time¹¹.”.”– UML emphasizes an iterative development process.UML emphasizes an iterative development process.

– The iterations stop when all system functions are captured in The iterations stop when all system functions are captured in cohesive object classes. System design can commence at this point.cohesive object classes. System design can commence at this point.

¹Larman, C., “Applying UML and Patterns” Prentice Hall PTR, Upper Saddle River, NJ, 2002

16

Within the DoDAF, a hierarchy of operational and systems Within the DoDAF, a hierarchy of operational and systems views of the system are provided.views of the system are provided.

– Although this is an architectural approach known as system Although this is an architectural approach known as system decomposition, a process is not described. decomposition, a process is not described.

– In general, each system and operational level in the DoDAF In general, each system and operational level in the DoDAF provides a static context or domain description that is inherited by provides a static context or domain description that is inherited by lower levels in the hierarchy. lower levels in the hierarchy.

UML Iterative Process In Contrast To DoDAF ConstructsUML Iterative Process In Contrast To DoDAF ConstructsFinding No. 1Finding No. 1

17

Object Class IdentificationObject Class IdentificationFinding No. 2Finding No. 2

A noun parse of the UML formatted use cases typically yields the class A noun parse of the UML formatted use cases typically yields the class objects necessary to describe the domain model.objects necessary to describe the domain model.

– UML process requires a substantial amount of system decomposition, UML process requires a substantial amount of system decomposition, from the high system of systems level described by the Land Warrior from the high system of systems level described by the Land Warrior use case to the functional requirements level at each node.use case to the functional requirements level at each node.

– The DoDAF appears to provide a less painful approach to modeling The DoDAF appears to provide a less painful approach to modeling systems of systems by decomposing the system only to the system systems of systems by decomposing the system only to the system node levels and avoiding the identification of functional capabilities. node levels and avoiding the identification of functional capabilities.

– DoDAF provides better architectural views.DoDAF provides better architectural views.

– UML / OO provides better descriptions of class responsibilities.UML / OO provides better descriptions of class responsibilities.

18

Object Classes / Operational NodesObject Classes / Operational NodesFinding No. 2Finding No. 2

V ideo D isp lay(O n H e lm et)

Sa te ll iteP hone

Pe rsona l D ig ita lA ssis tan t (PD A )

C ellu lar P hone

W a lk ie -T a lk ie C am eras S enso rsC om m unica tion

T ow ers

Land lines M icrow aveD ish

S witches ,R oute rs, H ubs

C om pu te rs

A irc ra ft G PS Etherne t S ate ll i te

There is a high degree of similarity between object classes described by OO and operational nodes described by DoDAF

19

Object Classes / Object Classes / Operational NodesOperational Nodes

Finding No. 2Finding No. 2

Digital PersonalAssistant

Real T im e V ideo,M ulti-cast D isplay

Cellular Voice

Radio W alkie Tallkie

Radio S ignalTransm itting

Dev ice / Tower

M ulti-cast cam era andrelated hardware

Cellu lar S ignalT ransm itting Towers

and Base S tations

Com puter W orkstations

Hubs, Routers

E thernet BackboneW AN

LAN

Satellite / M icrowav eTransm ission D ishes

Satellite / G lobalPosition ing D isplay Satellite / G lobal

Positioning D isplays

Cellular Voice M onitors

Satellite / G lobalPositioning Satellites

A irship and Satellitebased m ulti-cast

cam eras

Satellite / M icrowav eReceiv er D ishes &

Routers

TerrestrialTelecom m unication

Lines

TerrestrialTelecom m unication Hubs &

Routers & Teleohones

Sate llite Phone

LEO Satellites ForSate llite Phone

Operational Node Connectivity (OV-2)

There is a high degree of similarity between object classes described by OO and operational nodes described by DoDAF

20

Collaboration and System Sequence DiagramsCollaboration and System Sequence DiagramsFinding No. 3Finding No. 3

In UML, Collaboration and System Sequence diagrams are produced to In UML, Collaboration and System Sequence diagrams are produced to simulate the behavior of class objects within a system when stimulated simulate the behavior of class objects within a system when stimulated by an event.by an event.

– These two types of interaction diagrams are interchangeable and can These two types of interaction diagrams are interchangeable and can serve to benefit both the architect and the developer.serve to benefit both the architect and the developer.

Sequence diagrams are also provided as architectural modeling artifacts Sequence diagrams are also provided as architectural modeling artifacts within the DoDAF.within the DoDAF.

– Specifically, the DoDAF describes operational view OV-6c as an Specifically, the DoDAF describes operational view OV-6c as an operational event trace diagram. Similarly, systems view SV-10c is operational event trace diagram. Similarly, systems view SV-10c is described as a systems event trace diagram.described as a systems event trace diagram.

21


OO Sequence Diagram for The Land WarriorNote: OO Sequence Diagram format is very similar to the DoDAF view OV-6c & SV-10c

PDA LandlineCommunication

TowerSwitches,

Routers, Hubs

Enter typedmessage

Computer(Command &

Control Center)

1: SendMessage()

2: TransferMessage()

3: TransferMessage()

4: TransferMessage() 5: ReplyMessage()

Sequence diagram that conveys a messaging sequence when the Land Warrior communicates with the Command & Control Center through the Personal Digital Assistant

22

An object-oriented software producer might question this high level of refinement An object-oriented software producer might question this high level of refinement with respect to his or her charter.with respect to his or her charter.

– They are certain to criticize these examples in accordance with their object-They are certain to criticize these examples in accordance with their object-oriented paradigm that focuses purely on software development and leaves oriented paradigm that focuses purely on software development and leaves architectural modeling to some other organization. architectural modeling to some other organization.

– It is likely that they will cite these figures as being drawn incorrectly since It is likely that they will cite these figures as being drawn incorrectly since conventional UML sequence diagrams recommend that object instances, not conventional UML sequence diagrams recommend that object instances, not classes, be modeled to represent system behaviorclasses, be modeled to represent system behavior

– The UML use cases that were utilized to produce these sequence diagrams The UML use cases that were utilized to produce these sequence diagrams described system level features, not expected functionality. In order for described system level features, not expected functionality. In order for conventional UML sequence diagrams to be produced, the use cases would need conventional UML sequence diagrams to be produced, the use cases would need to be sufficiently refined to a lower level of abstraction and partitioned to the to be sufficiently refined to a lower level of abstraction and partitioned to the node level or possibly at levels below each node in order to convey functionalitynode level or possibly at levels below each node in order to convey functionality


23

Summary Comparison For All DoDAF Views Summary Comparison For All DoDAF Views versus OO/UML Is Provided In My Paperversus OO/UML Is Provided In My Paper

DoDAF Artifact Comparison Analysis To OO/UML Method

AV-1 Overview and Summary Information

AV-1 is a managerial summary that documents the purpose, scope and goals of the project. It behooves object-oriented practitioners to adopt this ‘cover letter of sorts’ since it is good project management technique.

AV-2 Integrated Dictionary The UML suggests that glossaries, data dictionaries and supplemental specifications be added to the requirements analysis. Additionally, UML techniques emphasize that data labels be applied directly to the UML diagrams, as does the DoDAF.

OV-1 High-level Operational Concept Graphic

OV-1 depicts the system level hardware or nodes in a system of systems. UML class diagrams can be utilized to model these hardware components even though the conventional OO application of domain class diagrams in intended for software classes within a software operating system.

24

QuestionsQuestions

1 Object Oriented Development For DoDAF System of Systems Stanley P. Stanilka The Boeing Company...

Documents

Transcript of 1 Object Oriented Development For DoDAF System of Systems Stanley P. Stanilka The Boeing Company...