90 likes | 106 Views
SWIM Architecture Alternatives. Duncan Thomson 6 May 2010.
E N D
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
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
Reference Case (No SWIM Beyond Segment 1) B-C Interface A-B Interface A-C Interface
Reference Case (No SWIM Beyond Segment 1) NAS System D, E, … A-C Interface B-C Interface A-D Interface B-D Interface C-D Interface A-B Interface For N systems there are on the order of N2 potentially unique interfaces
Option 1 - Federated Architecture(Continue and Expand Segment 1 Approach) Standardized interface logic
Option 1 - Federated Architecture(Continue and Expand Segment 1 Approach) NAS Information Layer (logical) N2standardizedinterfaces
Option 2 – Enterprise Messaging Backbone SWIM Core backbone replaces interconnected message brokers provided by individual programs Ninterfaces to messaging backbone, N2 information interfaces
Option 3 - SWIM Core SWIM Core ESB provides a platform to host new NAS common info services Consolidated management of common NAS information – “One Stop Shopping” for information consumers N information interfaces