SAL
Designing & Evaluating Agile C2 Systems Based on Service Oriented
Architectures*
6/29/2009 1
Ashraf M. Abusharekh <[email protected]>Lee W. Wagenhals <[email protected]>
Alexander H. Levis <[email protected]>
14th International Command and Control Research and Technology Symposium
Washington, DCJun 15-17, 2009
* This work was supported by the Office of Naval Research under grant N00014-06-1-0081
Paper # 157_S
System Architectures Laboratory
SALOutline
• Introduction & Background• SOA Environment• SOA Federation Structure• Architecting Process
– Architecture Design– Analysis & Evaluation– Architecture Deployment
• Case Study– Airborne Theater Ballistic Missile Interceptor System (ATIS)
• Conclusions & Future Work
6/29/2009 2System Architectures Laboratory
SALIntroduction & Background (1)
• A key to Command and Control (C2) agility is EFFECTIVE information sharing.
• DoD defined a set of concepts, objectives and strategies to achieve Net- Centric Operations (NCO)
– Concepts• Populate Net-Centric Environment (NCE).• Utilize the Net-Centric Environment.• Accommodate un-anticipated users.• Promote the use of Communities of Interest (COI).• Support shared infrastructure.
– Strategies• Net-Centric Data Strategy.• Net-Centric Services Strategy.
• DoD views architectures as the mechanism for designing solutions to transform to NCO
• DoDAF v.1.5 is focused on data centricity and uses the Service Oriented Architecture (SOA) paradigm as a key enabler for implementing NCO.
6/29/2009 3System Architectures Laboratory
SALIntroduction & Background (2)
• DoDAF v.1.5: All View (AV), Operational View (OV), Systems & Services View and Technical View
• How to construct an Event Driven Service Oriented Architecture compliant to DoDAF v1.5 ?
• The architecture (SOA) should:– Net-Centric Concepts
• Populate NCE with new capabilities• Utilize existing NCE capabilities• Accommodate un-anticipated users• Promote the use of COI• Support shared infrastructure
– Net-Centric Data Strategy• Make data visible, accessible, understandable, and trusted
– Net-Centric Services Strategy• Provide and consume services from the NCE, govern these services
and their infrastructure, and monitor and manage them
6/29/2009 System Architectures Lab. 4
SOA Federation
SALSOA Federation Environment
6/29/2009 System Architectures Laboratory 5
Operational Layer
Service
Service
ServiceService Service
Business Process nBusiness Process 2
Business Process 1
Service Layer
SOA Federation
SALSOA Federation Structure
• The concept of Communities of Interest (COI) will be used to enable dynamic federation with pre-defined or un-anticipated users
6/29/2009 System Architectures Lab. 6
NCE
COI<2>
Service<2>
COI<1>
Service<1>COI<3>
Service<4>
Service<3>
SOA<1>
Service<1>
Service<4>
SOA<2>
Service<1>
Service<3>
SOA<3>
Service<4>
Service<2>
SOA<4>
Service<3>
Service<2>
Subscribe
Subscribe
Publish: Service<3>/Subscribe
NCE Registry
SOA<5>
Service<2>
Service<3>
Service<1>
Service<4>
NCE Registry
COIs
COI<1>COI<3> COI<2>
COI Service Description
COI<2>.Service<1> COI<2>.Service<2>
Service Implementations
SOA<1>.Service<a> SOA<2>.Service<b> SOA<1>.Service<c>
SALArchitecting Process
6/29/2009 System Architectures Lab. 7
ArchitectureDeployment
ArchitectureDesign
Analysis &Evaluation
Deploy
Static Views (OVs, SVs)
Changes/Errors
New Business ProcessNew Application
Static Views (OVs, SVs)
EvaluationResults
CONOPS
NCES
DARS
COIs
• Architecture Design phase: Produce DoDAF v.1.5 products
• Analysis & Evaluation phase:– Synthesize the executable
model (EM).– Use it to evaluate and verify
the architecture.– Reflect corrections or
changes back in the DoDAF products
– Compute Measures of Performance and Measures of Effectiveness of the architecture.
• Architecture Deployment phase: new processes will trigger the design process again
SALArchitecture Design
6/29/2009 System Architectures Lab. 8
Stage 0 Stage 1 Stage 2 Stage 3 Stage 4 Stage 5
MissionCONOPS
Organizations & Relationships
Systems & Services
Descriptions
System Functions
Comm. Systems Description
Systems Performance Parameters
Evolving Technology &
Systems
DARS
NCES
Define Operational
ConceptSelect
Organizations & Relationships
Define Operational
Nodes
Select Systems/Services & Define System
Nodes
Develop OO Structural & Behavioral
Descriptions
Map Activities To Functions
UJTL
Doctrine & TTPs
Scenario Events
Information Exchanges
OV-5 OV-6AOV-6B OV-6C
OV-7OV-1OV-4
SV-5
Derive & Characterize
Operational Info. Exchanges
Develop OO Structural & Behavioral
Descriptions Based on
System/Service Functions
SV-10CSV-10BSV-11 SV-10ASV-4
OV-2OV-3
Derive System/Service Data Exchange
Define System/Service
Interfaces
Define Comm. Links & Networks
Interfaces
Define System/Service
Performance
Define Evolution of Systems & Technology
SV-6
SV-1 SV-3
SV-2
SV-7
SV-8
SV-9
COIsOperational View
Systems & Services View
• Based on the OO approach introduced by Wagenhals et. al
• Additional sources of information needed:
1) Information about existing COIs and the services they expose
2) Information about architectures of systems implementing capabilities that might be leveraged by the new architecture
3) Access to existing Net-Centric Enterprise Services (NCES) currently available through the Net- Centric Environment
SALAnalysis & Evaluation (1)
6/29/2009 System Architectures Lab. 9
• A dynamic model of the business services and processes is built using CPN Tools
• Scenarios are defined to evaluate the logical and behavioral aspects of the architecture
• Formal analysis of system properties (Reachability, Boundedness, Liveness, etc…) is conducted
• State Space analysis to detect errors and unwanted behavior is carried out• Corrections and changes are reflected back to the architecture description
SALAnalysis & Evaluation (2)
6/29/2009 System Architectures Lab. 10
Performance Prediction & Evaluation
SALArchitecture Deployment
• Deployment phase: the architecture is instantiated and deployed to accomplish its missions and business objectives
• New business processes or changes to existing ones as a result of a SOA instance being deployed should trigger an architecture review
• This requires maintaining and calibrating the executable model of the architecture after deployment to support such exploration
6/29/2009 System Architectures Lab. 11
SALCase Study: Airborne Theater Ballistic Missile Interceptor System (ATIS)
6/29/2009 System Architectures Lab. 12
NCE Ballistic Missile Response COI
1. ATI Service2. GBMW Service
ISR COI1. Track Blue Service2. Track Red Service
NCES Topics•ATIS Tactical Picture•GBMW System Tactical Picture
• Operational Concept graphic (OV-1): shows main operational nodes and Net-Centric Environment (NCE) support
SALCase Study (2)
• Main objectives– Determine if the operational concept can be made to work.– Assess the impact of evolving this system into a federated SOA,– Determine how to make its business services or their composition*
(business processes) accessible by anticipated and un-anticipated users
• Assumptions:– Two COIs:
• Ballistic Missile Response COI• Intelligence, Surveillance, and Reconnaissance (ISR) COI
– A Global Ballistic Missile Warning (GBMW) Service is deployed and is published through the Ballistic Missile Response COI
– Net-Centric Enterprise Services (NCES) and capabilities are available and accessible. “e.g. Discovery, Messaging, Mediation Services“
* Business processes are composed of multiple business services
6/29/2009 System Architectures Lab. 13
SALATIS Business Services & Processes
6/29/2009 System Architectures Lab. 14
Services System NodeBusiness Process
Name
External Anticipated
User
ExternalUn-anticipated
UserEngageOrder
ATIS Command
- - -
DetectThreat DetectThreatBP - -
EngageThreat EngageThreatBP - -
KillThreat KillThreatBP - -
SD - - -
ATIService ATISBP GBMWS BMR COI
TrackRed
ATIS Radar
- - ISR COI
TrackBlue - - ISR COI
AssessKill - - -
TPReport - - -
Control ATIS Control - - -
SALATIS CPN Top Page
6/29/2009 System Architectures Lab. 15
SD_REQUEST
SD_DIRECTIVE
TP_REPORT
TP_REPORTTP_REPORT
TP_REPORTTP_REPORT
TP_REPORT
SD_REQUEST
TP_REPORT
ORDER
SD_REQUESTDB
SD_DIRECTIVE
TP_DATA
TP_DATA
SD_DIRECTIVE
Command
CommandCommand
ISR
ISRISR
RequestDetectThreat
RequestTrackRed
ResponseTrackRed
ResponseTPReport
ResponseTrackBlue
RequestTrackBlue
RequestSD
TP_DATA
RequestOrder
ResponseSD
ResponseATISOutOut
ResponseOrder
RequestControlService
Control
ControlControl
ResponseDetectThreat
ResponseEngageThreat
ResponseKillThreat
ResponseControlService
ORDER
RequestATISInIn
SD_REQUEST
TP_DATA RequestEngageThreat
RequestKillThreart
RequestTPReport
TP_REPORTResponseAssesskill
RequestAccessKill
SD_DIRECTIVE
SALATIS Scenario Profile
6/29/2009 System Architectures Lab. 16
Input Variables (Parameters)Name Description Values
Number of TBMs Total number of TBMs launched by adversary (fixed). 10
TBM Inter-arrival Time interval between TBM arrivals. 0, 25,50,75,100 (seconds)
Number of Interceptors Total number of ATIS Interceptors. 3, 4, 5
Output Variables (Measures of Performance – MOPs)Name Description Requirement
Average Response Time
The average time between the ATIS detecting the TBM until the TBM is engaged.
<= 400 seconds
Number of Leakers Total number of TBMs not destroyed within 400 seconds of being detected by ATIS. <=2
SALResults
• 3 interceptors can handle the 10 threats (with a max of four leakers) if they arrive at a rate slower than 1 in 25 seconds
• 4 interceptors can handle the 10 threats (with a max of two leakers) if they arrive at a rate slower than 1 in 25 seconds
• 5 interceptors can handle the 10 threat with no leakers
6/29/2009 System Architectures Lab. 17
Number of Interceptors TBM Inter-arrival Average Response Time Number of Leakers
3
0 347.1 425 270.1 150 180.6 075 159 0100 159 0
4
0 283.9 225 212.9 050 159 075 159 0100 159 0
5
0 245.5 025 180 050 159 075 159 0100 159 0
MOE = 93%
SALConclusion & Future Work
• A formal dynamic model of federated SOAs suitable for analysis and evaluation– Dynamically federate with NCE systems through COI registries and
by utilizing the NCES to share enterprise-level information• An approach for constructing an event driven SOA compliant to
DoDAF v1.5• Behavioral and Logical evaluation of business service and
processes , and baseline performance measures of SOA using Colored Petri Nets
• Future work– Extend the analysis and evaluation to capture SOA infrastructure
6/29/2009 System Architectures Lab. 18
SAL
QUESTIONS?
6/29/2009 System Architectures Lab. 19