Joint aar architecture development
Download
1 / 24

joint aar architecture development - PowerPoint PPT Presentation


  • 213 Views
  • Uploaded on

Joint AAR Architecture Development. Evolution of the OneSAF AAR Architecture. Evolving the Architecture. Baseline Architecture Receive Stakeholder Requirements Allocate Stakeholder Requirements Develop Use Case Scenarios Identify Extensions Define Extensions.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'joint aar architecture development' - Olivia


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Joint aar architecture development l.jpg

Joint AAR Architecture Development

Evolution of the OneSAF AAR Architecture


Evolving the architecture l.jpg
Evolving the Architecture

  • Baseline Architecture

  • Receive Stakeholder Requirements

  • Allocate Stakeholder Requirements

  • Develop Use Case Scenarios

  • Identify Extensions

  • Define Extensions


Slide3 l.jpg

Use Case Scenarios Use Case Scenarios represent threads providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

Use Case

One

Use Case

N

Products Specify a logical grouping of components along boundaries (applications, phases, tools, etc)

Capability or Phase

System Components Document modules of implementation that interact according to defined interfacing mechanisms called “Connectors”. These connectors are themselves Supporting Components of the architecture. For each Component, context-connector diagrams are documented one dependency deep.

Middleware Layer Middleware Components represent the layer that connects System Components to Technologies. The mechanisms used by the connectors are strongly driven by the stakeholder quality attributes.

Connector

Functional

Services

Sub-Component

Data

Model API

Technology & Standards Layer Service components represent the layer that abstracts the Components and Connectors of the Use Cases Scenarios from the underlying implementation details (HW/SW).

XML

Services

GUI

Services

File O/I

Services

ODBC/ADO

Services

Office

Services


Block c architecture baseline l.jpg

No Quality Attributes providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

PLRS specified

SRS specified

Use Case Scenarios identified, not well defined.

Components and Interfaces defined

Block C Architecture Baseline


Joint after action review l.jpg

Joint After Action Review providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

OneSAF AAR Extended


Jaar concept of development integration l.jpg

Joint Experimentation providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

and Testing

Service Simulation,

Training and

Testing Centers

and Ranges

Global Simulation, Training and Testing Capabilities

Command &

Control Data

Simulation Data (HLA)

Simulation Data (DIS)

IntellData

Live Data

Comms. Data

Site/Service Data Collection/AAR Systems

Distributed Heterogeneous data bases

Joint AAR

Associated Information

Automated measures

COCOM Joint Training

Service Joint

Training Programs

Joint Center for

Operational Analysis

JFCOM J 7 Capabilities

Group DOTMLPF

Joint Training & Assessment

Audience MOE/MOPs

JKDDC

Lessons Learned

J7 Joint Training

System Assessment

Multiple Users

Multiple Applications

JAAR Concept of Development & Integration


Receive stakeholder requirements l.jpg
Receive Stakeholder Requirements providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

  • Capture Stakeholder Quality Attributes

    • If the sponsor of a system cannot tell you what any of the quality goals are for the system, then any architecture will do.

    • Quality attributes are used in context to architectural evaluation techniques

  • Allocate Requirements

    • Allocate to Components

    • Identify Specification Level


Jaar system requirements l.jpg
JAAR System Requirements providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.


Adopt use case scenarios l.jpg
Adopt Use Case Scenarios providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

  • Use Case Scenarios represent the threads by which to evaluate an architecture in context to its quality attributes

    • Use Case Scenarios provide first impressions for any architecture

      • Not the same as software (UML) use cases

    • These threads represent methods of evaluating the architecture in context to a stakeholder’s quality attributes

      • Joint AAR Operational Activities


Operational activities dodaf l.jpg

Training Support Package providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

Operational Activities

Planning

MOP/MOE

Joint Task Articles

Take Home Package

Exercise

Architecture

Operator

Interface

Analysis

Data

Products

Data

Products

Data

Products

RD3 Scenarios

Data

Products

Comms.

Function

Reports

JAAR (Site) Users

AAR Analyst

Real-Time

Feedback

Replay

Site After

Action Review

Exercise

Control

Data Fusion

Collaboration

Site Instrumentation

Data

Retrieval

Data

Distribution

Network

LVC TADSS

Exercise

& Site Data

C4I Devices

Operational Activities (DODAF)


Allocate requirements l.jpg
Allocate Requirements providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

  • Allocate to Components

    • For each component ask what this stakeholder’s requirement means in the component's context

  • Identify Specification Level

    • Identify the specification level of each requirement; for example:

      0 = No Allocation

      1 = Specified

      2 = Designed

      3 = Implementation (Partial)

      4 = Complete


Identify extensions l.jpg
Identify Extensions providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

  • Analyze Requirements

    • Identify how implementation falls short of providing for quality attributes in context to the requirements

  • Develop Integration Alternatives

    • Ensure each alternative is distinguishable from the others

  • Analyze Alternatives

    • Weigh alternatives by quality attributes and other common criteria

  • Select Alternatives

    • This process is representative of a trade-off or decision analysis and resolution study


Operational integration view l.jpg

Exercise providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

Control

Observer

Controller

AAR

Analyst

Exercise

Networks

C3I

White Cell

C3I White

C3I

Blue Cell

C3I Blue

Data

base

Server

OC

Tools

JAAR

Analyst WS

JAAR Data

Collector WS

Agents

JAAR

Analyst WS

DIS/HLA

M&S

TENA

T&E

Data

Collectors

JAAR Network

Operational Integration View


System integration view l.jpg

User providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

Functions

Folder

Shared

Drive

Take Home Package

AAR

Products

Exercise

DC Manifest

Reports &

Map Products

Replay

Media

Reports

Chart, Table, Map Products

10

8

JAAR Functions

DDST

SIMDIS

Auto

Report

Presentation

Builder

2/5

AAR Analysis,

Hot Wash, &

Production

7

AAR Components

Data

Collector

Manager

JAAR

Analyst

WS

6/9

1/3

Data Collectors

Data Collection

Management &

Synchronization

4

TENA

HLA

DIS

GCCS

LINK16

Exercise

Functions

Exercise Network & Architecture

Exercise

Gateways

TENA

HLA

DIS

C4I

LINK16

System Integration View


Technology integration view l.jpg

Data providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

Providers

Relational

Databases

SQL

Queries

Product

Generation

Media

(Product)

C4I

Data

Collector

Data

Processor

Media

Media

DIS

Product

(Generator)

Product

(Generators)

Agents

Methods of

Evaluation

HLA

MOP

MOE

RDBMS

XSD

Query

TENA

XSD

Query

1 Data Collection

2 Data Base

3 Query

4 Product/Media

Data Fusion

1 Integrate Data Providers for Data Collection.

2 Integrate Relational Databases Using Standard ANSI SQL.

3 Integrate Product Generation Capabilities with ODBC Queries.

4 Integrate Media or other Product Formats for AAR.

Technology Integration View


Integration architecture l.jpg
Integration Architecture providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

  • Based on DODAF

    • Operational Level

      • This is how the AAR systems is delivered and integrated with Joint training sites

    • Systems Level

      • This is how Service tool sets are integrated seamlessly with JAAR Core Components

    • Technology Level

      • This is how AAR components interoperate based on technology standards


Dodaf alignment l.jpg

Operational Layer providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

Planning

Operator

Interface

Communications

Real-Time

Feedback

Data Fusion

Product (Operator Interface) Layer

Data

Collectors

Database

Server

Data Collector

Workstation

OC

Tools

Analyst

Workstation

Visualization

& Misc Tools

System (Service Tool Sets) Layer

GCCS

(Tracks)

Oracle

Data

Collection GUI

CAPT

AAR Analyst

GUI

SIMDIS

WARSIM

(HLA)

PostgreSQL

JAAR PDA

DDST

CPAS

(JDocs)

MS Access

JAAR Agents

Presentation

Builder

Chat

Auto-Reports

Technical Support (Middleware) Layer

DIS-HLA

Gateway

RTI (HLA)

Client

TENA Client

(Middleware)

C4I

Gateway

Voyager

(Agents)

AAR

Data Source

Technical Standards Layer

DIS

TENA

C4I Protocols

XML

HLA

SQL

DODAF Alignment


Integration approach l.jpg
Integration Approach providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

  • Evaluate & Rate tool sets in context to Operational Activities

  • Select tool sets are a central context of integration by Rating.

  • Integration by loose coupling through a Service Oriented Architecture

    • Agents, and Agent Frameworks


Aar planning activity ov 5 l.jpg

Domain Data Providers providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

Data Subscriber

Data Persistence

MOP/MOE Data

Discussion Points

Tasks to be Trained

Agents &

External Systems

Data Collector

Relational

Database

Query

(Product

Content Model)

Product

(Measures)

JTA/JTT

Content Model

5

4

3

2

1

Planning for AAR Data Collection (MOP/MOE) Flows Backwards

From the JTA and JTT content models to the systems providing content data

Data

Control

Analysis

1 Selected JTA/JTTs Identify the Products and Methods of Evaluation.

2 Products are Associated with the Queries (Product Content).

3 Product Content (Queries) map to Databases Content.

4 Databases Content is Provided by Data Collectors.

5 Data Collectors collect data from Agents and External Systems.

AAR Planning Activity (OV-5)


Oc tools sv 2 l.jpg

Data Collection Manager plans and manages Data Collection providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

Documents and templates provided to observer controllers.

Observer Controllers and annotate observations in context Joint tasks, and measures.

Real-time feedback is passed on for data collection.

Observations are published

JAAR

DC WS

Collaboration

3

4

2

5

1

N

6

Data

Collector

OC Tools (SV-2)

OC Tool (PDA) Federation

PDA

Controller

4

Data

Fusion

2

3

5

1

Documents

& Templates

Relational

Database

Technical

Control


Gateways l.jpg
Gateways providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

Exercise

Middleware

Layer

Gateway

Application

Data Collector

Middleware

Layer

JAAR

Data Collector

JAAR

Database

C4I

C4I

DIS

DIS

Relational

Database

Data

Collector

Gateway

HLA

HLA

TENA

TENA

1 Translation

  • Publication

3 Collection

4 Publication

1 Translates from an exercise protocol to a JAAR data collection protocol

2 Publishes the translated protocol through middleware to a JAAR Data Collector.

3 Collects the data through a middleware component.

4 Publishes the translated data through ODBC to other JAAR Components.


Technical standards tv 1 l.jpg
Technical Standards (TV-1) providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.


Questions l.jpg
Questions providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.

ISBN: 020170482X

ISBN: 0201703726

ISBN: 0201703327


Questions24 l.jpg
Questions providing context in which the architecture is quantitatively evaluated by stakeholder quality attributes.


ad