re-use of integrated dictionary components for c4isr architectures

Re-Use of Integrated Dictionary Components for

C4ISR Architectures

Asma Ali George Mason University

OutlineOutlineC4ISR Architecture Framework Products C4ISR Architecture Framework Products Version 2.0Version 2.0

Problem IllustrationProblem Illustration

Research Objective Research Objective

Methodology AdoptedMethodology Adopted

Comparison of Integrated DictionariesComparison of Integrated Dictionaries

ConclusionConclusion

C4ISR Architecture Framework (CAF) C4ISR Architecture Framework (CAF) Products Version 2.0Products Version 2.0

CAF Version 2.0 provides architecture CAF Version 2.0 provides architecture specifications.specifications.

Objectives of CAF are to provide, Objectives of CAF are to provide, -- Rules, guidance and product Rules, guidance and product description for developing architectures.description for developing architectures.-- Common unifying approach for different Common unifying approach for different agencies for architecture development.agencies for architecture development.

Views of Architecture ProductsViews of Architecture Products

CAF describes a set of products to CAF describes a set of products to represent three views of architecturerepresent three views of architecture

-- Operational Architecture ViewOperational Architecture View-- System Architecture ViewSystem Architecture View-- Technical Architecture ViewTechnical Architecture View

However, no well defined or widely However, no well defined or widely accepted approach to produce these accepted approach to produce these products is provided.products is provided.

Approaches for Developing CAF Approaches for Developing CAF ProductsProducts

CAF Products

Object Oriented(OO) Products

Focused on entitiesand their

Interactions

Structured Analysis(SA) Products

Focused on Functions & Data

Problem Problem IllustrationIllustration

Existing C4ISR Products

(SA approach)

Existing C4ISR Products

(OO approach)

Not difficultNon-TrivialNot difficult

New Products(SA approach)

New Products(OO approach)

Research Research ObjectiveObjective

Integrated Dictionary(AV-2)

Containing definitionsfor C4ISR Products

developed using SA approach

Find out Possibility of Re-Using the definitions

Integrated Dictionary(AV-2)

Containing definitionsfor C4ISR Products

developed using OO approach

Methodology Adopted for ResearchMethodology Adopted for Research

C4ISR Products

SA approach

Integrated Dictionary

AV-2

C4ISR Products

OO approach

Integrated Dictionary

AV-2

OperationalConcept

CompareDictionary

Components

Mapping Between CAF/SA/OO Mapping Between CAF/SA/OO ProductsProducts

Node Connectivity Description

NCA

WOCArmyForces

JFC

JFACC

S&RSensors

MarineForces

MAW

JIC (Rear)

NavalForces

JFAACDerived from OV-1

& Functional decomposition

SA

Derived from theUML Class diagram

OO

ps

CommandRelationshipChart

Derivedfrom OV-1

SA Derivedfrom

Class/Objectdiagram

OO

OperationalConceptDiagram (OV-1)

DerivedFrom

DomainKnowledge

SA OO

Mapping Between CAF/SA/OO Mapping Between CAF/SA/OO Products (Contd..)Products (Contd..)

State Transition DiagramOV-6b

State Transition Diagram

SA State Transition Diagram for each

object

OOActivity Model

SA

IDEF0

OO

Activitydiagram

Logical Data ModelLogical Data ModelOVOV--7 7

Derived directly Derived directly from Data Modelfrom Data Model

SA

OOMay be derived from May be derived from

Class diagramClass diagram

Operational Event/TraceOperational Event/TraceDescription OVDescription OV--6C6C

To be consistent To be consistent OVOV--2 and OV2 and OV--5 5

SA UML Sequence diagramUML Sequence diagramCan be used directlyCan be used directly

OO

Mapping Between CAF/SA/OO Mapping Between CAF/SA/OO Products (Contd..)Products (Contd..)

System Interface diagram (SVSystem Interface diagram (SV--1) 1)

System nodes and linksSystem nodes and linksDerived from operational Derived from operational

conceptconcept

SADerivable from theDerivable from the

System class diagramSystem class diagram

OO

System communicationSystem communicationDiagram (SVDiagram (SV--2)2)

SADerived from Derived from

Operational concept Operational concept

Logically similar to Logically similar to SVSV--11

OO

System Functionality DescriptionSystem Functionality Description(SV(SV--4)4)

SAGraphically can beGraphically can be

represented as activity represented as activity Model as DFD Model as DFD

OOUML activity diagram forUML activity diagram forSystem classes can beSystem classes can be

used directlyused directly

FastPassFastPass System Operational Concept System Operational Concept (OV(OV--1)1)

Financial Institution

DriverDriver enters bayDrive Activates FastPass with deviceAfter Permission, driver selects grade of gas and fuels carDriver leaves

Gas Pump

LAN

WAN

Check credit informationAuthorize credit purchaseUpdate credit informatiion

Turn on FastPass Light to show process is workingIssue Permission to fuelPrint ReceiptTurn off FastPass Light

FastPass light

Gas Station Office

OilCo Central Data Base

Retrieve Driver Information

Comparison of Data Dictionaries Comparison of Data Dictionaries ComponentsComponents

Many definitions for two set of products match with Many definitions for two set of products match with other. For example,other. For example,

-- Operational Nodes/ClassesOperational Nodes/Classes-- Information ExchangeInformation Exchange-- Organizational UnitsOrganizational Units-- Operational ActivitiesOperational Activities-- Object StateObject State-- ICOM/Message FlowICOM/Message Flow

Reason being, products for both sets were Reason being, products for both sets were produced using same operational concept.produced using same operational concept.

Mapping between Operational Concept, Operational Node Connectivity Description and UML Class Diagram

DriverAttributes+A11+A12

Show IDPump GasTake Receipt

Class

Attributes

Operations

FP_ID

Attributes

Operational Class DiagramOV-2, Operational Node Connectivity Description

Class Attributes

Operations

Ass Class

Attributes

Ass Class

Attributes

Ass Class

Attributes

AssociationClass

Attributes

Op Node

Driver OP Node

Show FP_IDPump GasTake Receipt

OperationalActivities

FP_IDAss Class

Operational Activities

FastPassFastPassSystemSystem

Op ConceptOp Concept

Ass Class

Ass Class

Ass Class

Mapping Between Activity Model, Operational Node Connectivity and UML Activity Diagram

Show FP_ID

Op Activity

FP_ID

Ass Class

Ass Class

Ass Class Ass Class

Op ActivityAss Class

OP Node

Driver OP Node



FP_IDAss Class

Ass Class


Ass Class

Ass Class

OV-2, Operational Node Connectivity DescriptionOV-5, Child Diagram

Show FP_ID

Driver Class 2 Class 3Ass Class

Pump Gas

Ass Class

Ass Class

Ass ClassAss Class

Take Receipt Ass Class

UML Class Diagram

Comparison of Data Dictionaries Comparison of Data Dictionaries Components (Contd..)Components (Contd..)

However, certain definitions did not match.However, certain definitions did not match.

NoneNoneRelationships between Relationships between entities in the Logical data entities in the Logical data model model

ICOM/Message Flow at ICOM/Message Flow at Decision point in UML Decision point in UML Activity diagramActivity diagram

NoneNone

NoneNoneOp activities for AOp activities for A00, A1, , A1, AA22, and A, and A33

Definitions in OO Definitions in OO dictionarydictionary

Definitions in SA Definitions in SA dictionary dictionary


For System Architecture view products many For System Architecture view products many definitions match with each other. For example,definitions match with each other. For example,

-- System NodesSystem Nodes-- System Data ExchangeSystem Data Exchange-- System ElementsSystem Elements-- Communication NodesCommunication Nodes-- System Functions/Operations of the classesSystem Functions/Operations of the classes-- Data Stores/Aggregate ClassesData Stores/Aggregate Classes

Mapping Between System Interface Description (SV-2) and UML Class Diagram for Systems Classes

DriverAttributes+A11+A12


Class Attributes

Operations

FP_ID

Attributes

Systems Class Diagram

Class 3Attributes

Operations

Ass Class

Attributes

Ass Class

Attributes

Ass Class

Attributes

Ass Class

Attributes

AggregateClass

Attributes

OperationsAGOP

AggregateClass

AttributesOperationsAGOP

Driver Database

Driver Info

Provide Driver Info

Aggregate Class

Attributes

OperationsAGOP

Driver

AggregateClass

AggregateClass

Driver Database

AggregateClass

Systems Node 2

Systems Node 3

Ass Class Ass Class

Ass Class

Ass Class

FP_ID

SV-1, System Interface Description

Mapping Between UML Activity Diagram and the Data Flow Diagram

Show FP_IDAGOP

Ass Class

Pump Gas

Ass Class

AGOP

AGOPAGOP

Ass ClassAss Class

Ass Class

Take ReceiptAss Class

Aggregate Class

Aggregate Class

Aggregate Class

Driver DatabaseClass 1

External AGOPAss Class

AGOP

AGOP

Driver Database

Ass Class

Ass Class

Ass Class AGOP

AGOP

Ass Class

Ass Class Ass Class

Ass Class

UML Activity Diagram for System Nodes

Data Flow Diagram


However, no definitions of systems functions for However, no definitions of systems functions for external entities in DFD diagram, like,external entities in DFD diagram, like,

-- Functions for DriverFunctions for Driver-- Functions for Financial InstitutionFunctions for Financial Institution

In SA approach Information provided by “Data In SA approach Information provided by “Data stores” in DFD match with information contained stores” in DFD match with information contained by the aggregate classes in OO approach.by the aggregate classes in OO approach.

Summary & ConclusionSummary & ConclusionReRe--Use of definitions contained by Integrated Use of definitions contained by Integrated dictionary was discussed.dictionary was discussed.CAF products were developed using SA and OO CAF products were developed using SA and OO

approach.approach.Components of the two dictionaries were Components of the two dictionaries were compared.compared.Results showed that most of the terms were Results showed that most of the terms were identical and can be reused.identical and can be reused.Certain differences in definitions were due to the Certain differences in definitions were due to the difference of product development techniques.difference of product development techniques.Hence, use experience and domain knowledge to Hence, use experience and domain knowledge to “fill in the blanks” for reusing definitions from one “fill in the blanks” for reusing definitions from one architecture into another.architecture into another.

QuestionsQuestions

re-use of integrated dictionary components for c4isr architectures

Documents