Upload
augusta-flowers
View
215
Download
0
Tags:
Embed Size (px)
Citation preview
© 2010 The MITRE Corporation. All rights reserved.
SWIM Architecture Alternatives
Duncan Thomson
6 May 2010
The contents of this material reflect the views of the author and/or the Director of the Center for Advanced Aviation System Development. Neither the Federal Aviation Administration nor the Department of Transportation makes any warranty or guarantee, or promise, expressed or implied, concerning the content or accuracy of the views expressed herein.
Approved for Public Release: Case number 10-1902. Distribution Unlimited
© 2010 The MITRE Corporation. All rights reserved.
Overview
• Four different architecture alternatives are presented:– Reference Case (no SWIM beyond Segment 1)
– Federated Architecture
– Enterprise Messaging Backbone Architecture
– SWIM Core Architecture
• We will discuss the benefits associated with each architecture alternative
© 2010 The MITRE Corporation. All rights reserved.
Reference Case (No SWIM Beyond Segment 1)
A-CInterface
A-BInterface B-C
Interface
© 2010 The MITRE Corporation. All rights reserved.
A-CInterface
A-BInterface B-C
Interface
NAS System D, E, …
A-DInterface
B-DInterface
C-DInterface
For N systems there are on the order of N2 potentially unique interfaces
Reference Case (No SWIM Beyond Segment 1)
© 2010 The MITRE Corporation. All rights reserved.
Option 1 - Federated Architecture(Continue and Expand Segment 1 Approach)
Standardized interface logic
© 2010 The MITRE Corporation. All rights reserved.
Option 1 - Federated Architecture(Continue and Expand Segment 1 Approach)
NAS Information Layer (logical)
N2 standardized interfaces
© 2010 The MITRE Corporation. All rights reserved.
Option 2 – Enterprise Messaging Backbone
SWIM Core backbone replaces interconnected
message brokers provided by individual
programs
N interfaces to messaging backbone, N2 information interfaces