Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved Characterization Framework and Design Patterns for the Disadvantaged User Presenter: Dr. Fatma Dandashi

Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved 2 Agenda n Problem statement and motivation for work n Technical Approach n Characterization Framework & Common Vocabulary n SOA and Service Design Patterns n Recommendations, conclusion, and future work

Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved 3 How do SOAs enable solutions for disadvantaged users? Challenge Intermittent Connectivity Limited Bandwidth Heterogeneous Devices Limited Local Resources High Latency Warfighter Disaster Relief

Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved 4 Others With Similar Problems First Responders Health Care Symptoms, Treatments, Diagnosis info. Field/First Responder Symptoms, Treatments, Diagnosis info. Analysis Info from other areas/ responders

Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved 5 For DOD n It is worse than you might expect: –Often severely constrained environments, n e.g., Baud Rate = 2400 bps –Potentially bigger impact for getting it wrong n e.g., Latency of time critical data: > 1 sec –Bigger scale and less controlled environment n Globally distributed, with no controlled/regular synchronization

Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved 6 Technical Approach

Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved 7 Edge Framework Environments n Edge not effectively described by a single environment, but instead by a set of environments –Each describes “layer” of edge further from the GIG core (infrastructure) –Framework defines these layers with emphasis on data and services

Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved Edge Framework 8

Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved 9 Design Patterns From: Tactical Edge Characterization Framework, Vol 2: Design Patterns for Edge Environments

Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved 10 Edge Computing and Caching Data Synchronization Data Compression Rich Internet Apps (e.g. offline apps) Intermittent Connectivity Limited Bandwidth High Latency Heterogeneous Devices Limited Local Resources Dimensions Design Patterns Applicable Design Patterns DoD implementations need to leverage commercial solutions to the extent possible

Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved 11 Conclusion n The common vocabulary can be used to describe various environments such that one can look across multiple use cases and identify commonality in the type of constraints introduced in each use case. Subsequently, this allows for sharing of design patterns and implementation solutions across these use cases. n The framework provides the basis for a process to assess the readiness of a particular existing system for the tactical edge, comparing the implementation against appropriate design patterns and infrastructure requirements for particular classes of environments. n The use of design patterns particular to disadvantaged environments provides an ability to make investment decisions on infrastructure requirements as part of infrastructure upgrades and resource prioritizations.

Approved for Public Release; Distribution Unlimited. Case Number: , © 2006 The MITRE Corporation. All rights reserved 12 Future Work n Applying the framework to additional use cases to validate the classes of environments and associated attributes n Focus on identifying non-DoD use cases to validate the adoption of this approach for non-DoD disadvantaged users