1 / 24

Joint AAR Architecture Development

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.

Olivia
Télécharger la présentation

Joint AAR Architecture Development

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Joint AAR Architecture Development Evolution of the OneSAF AAR Architecture

  2. Evolving the Architecture • Baseline Architecture • Receive Stakeholder Requirements • Allocate Stakeholder Requirements • Develop Use Case Scenarios • Identify Extensions • Define Extensions

  3. 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

  4. No Quality Attributes PLRS specified SRS specified Use Case Scenarios identified, not well defined. Components and Interfaces defined Block C Architecture Baseline

  5. Joint After Action Review OneSAF AAR Extended

  6. Joint Experimentation 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

  7. Receive Stakeholder Requirements • 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

  8. JAAR System Requirements

  9. Adopt Use Case Scenarios • 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

  10. Training Support Package 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)

  11. Allocate Requirements • 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

  12. Identify Extensions • 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

  13. Exercise 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

  14. User 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

  15. Data 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

  16. Integration Architecture • 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

  17. Operational Layer 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

  18. Integration Approach • 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

  19. Domain Data Providers 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)

  20. Data Collection Manager plans and manages Data Collection 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

  21. Gateways 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.

  22. Technical Standards (TV-1)

  23. Questions ISBN: 020170482X ISBN: 0201703726 ISBN: 0201703327

  24. Questions

More Related