AMS AO - Rewrite TCS Proposal
AMS AO - Rewrite TCS Proposal
TCS Proposal
May, 2017
AMS Application Roadmap
2
AMS Application Challenges
3
AMS Application Roadmap
4
Need for Re-Architect
Shared Infrastructure
5
Proposed AMS Technical Architecture
Documentum
Print Shop
AO DB
Read stations
Dependability points
6
Proposed AMS Deployment Architecture
Clients Metor.js
NDC OPC
(Disaster Recovery)
Load Balance Load Balance
Node Js
Web Server Web Server Web Server Web Server
AMS Interface
EDW
8
TCS Recommendation
Advantages of Re-Architecture:
New architecture completely separates UI with Business layer for better maintainability and performance
improvement
WebSphere is Robust App Server that provides clustering to scale with future business demands
Angular JS gives light weight UI with better Look & Feel and response time is very low as compared to any other
architectural solution
Business layer using JEE 6, RESTful WS & Spring frameworks can run independently and removes all the
external dependencies such as change in app server/versions, databases, front-end implementations AngularJS
9
TCS – Additional features proposed
Add New screen for Letter Configuration to provide self serviceability to users ts to AMS
Remove hardcoded license key of certificate used in AMS and configure key value in DB.
Audit trail
Audit crucial functions of AMS , Occurrences, Roll on, Letters, Work history, Recalculation.
Enable new screen in AMS to view audit details.
10
3 Tier Architecture Comparison - As-Is and To-Be
Web &
Application Tier API are hosted in Jboss Server API are hosted in WebSphere Server
11
Proposed AMS NFR Components
Authentication United Airlines Single Sign On Services will be used for User Authentication
Audit Trail Admin User action will be logged in the database for selected transactions.
12
Implementation Strategy
New Architecture
13
Recommended Hardware and Software Requirements
1 Node JS 4.4.3
2 AngularJS 2
14
Assumptions and Key Asks
Assumptions
• Requirements finalized during Analysis and Design phase will not change during build and execution phase
• Timeline will be revisited post Analysis and Design phase
• Nature of testing needs to be discussed and finalized prior to the Build phase
• User Role mapping or User Role Matrix for security enforcements will be provided by United
Key Asks
• Required SME’s from United business would be available for requirement / design discussion
• Sign off provided on deliverables at the end of each phase
• Requirement for new reports will be shared by United during analysis phase
• Infrastructure support and Release management will be provided by United team
• Infrastructure sizing will be done by United team
15
Program - Proposed schedule
AMS AO Re-Architect
16
Proposed resource mix
Tech-group Role Location Development Track
17
Commercials
Costing assumptions:
All phases from planning to implementation will be Fixed price engagement.
The EQA team’s test activities are expected to be on the schedule as mentioned in the proposed schedule work Plan.
Audit trail estimates would be revisited if change of scope.
18
THANK YOU