0% found this document useful (0 votes)
98 views19 pages

AMS AO - Rewrite TCS Proposal

The document proposes re-architecting the AMS application to address scalability, maintainability, security and outdated technology challenges. It recommends a new 3-tier architecture with AngularJS for the UI, JEE6 and RESTful web services for the business layer, and WebSphere application servers. The new architecture would provide a more robust, scalable and maintainable platform aligned with enterprise standards.

Uploaded by

rkodadi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
98 views19 pages

AMS AO - Rewrite TCS Proposal

The document proposes re-architecting the AMS application to address scalability, maintainability, security and outdated technology challenges. It recommends a new 3-tier architecture with AngularJS for the UI, JEE6 and RESTful web services for the business layer, and WebSphere application servers. The new architecture would provide a more robust, scalable and maintainable platform aligned with enterprise standards.

Uploaded by

rkodadi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

AMS AO - Rewrite

TCS Proposal
May, 2017
AMS Application Roadmap

RE-ARCHITECT ON NEW TECHNOLOGY

2
AMS Application Challenges

AMS Application Developed in 2004


Scalability & Maintainability
Security Vulnerability Existed

Outdated Technology Stack

Non- multiple Tier Architecture

Away from Enterprise Standards

Non Optimized Database Design

3
AMS Application Roadmap

Future expansion – in visibility (Not in project scope)


 On Boarding Additional User Groups like Tech Ops & Catering

 Move Application to New Data Center (NDC )

 Future dependency Points Expansions Potential implicit expectations in


 Security vulnerability remediation future (Not in project scope)
 Mobile Enabled
 Extend User Base for Flight Attendant ( Both sUA & sCO )
 New Cloud enabled Technology Stack
 Multi fold User Data Records
 Automated Unit & Regression test cases

 Dev Ops Adoption

 Split AMS database from Mars database

4
Need for Re-Architect

Potential scalability & performance issues

Outdated Technology Stack

Shared Infrastructure

Reliability & Availability Challenges

5
Proposed AMS Technical Architecture

Documentum

Print Shop

Email

AO DB

Read stations

Dependability points

6
Proposed AMS Deployment Architecture

Clients Metor.js

NDC OPC
(Disaster Recovery)
Load Balance Load Balance

Active Directory Active Directory

Node Js
Web Server Web Server Web Server Web Server

AMS Interface
EDW

MARS Web Sphere


PeopleSoft App Server App Server App Server App Server
JDBC
eTA
Reports Data HTTP
SAW Case Creation Data
Oracle Reports Data REST
Master Data : Role Case Creation Data
LDAP
Master Data : Role etc.
AMS DB AMS DB HTTPS
Indicative architecture. Requires discussion with Infra team to finalize
7
Pros & Cons

Highly Scalable Architecture


Disaster Recovery Infrastructure
Tier Architecture Deployment
Better SLA Monitoring

Additional Hardware is required


DR Datacenter is located in the Same location
Additional Software license cost

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

 Angular JS is cross browser compatible

 Java 1.8 is recommended to remove all the security vulnerabilities

 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

 Enable/Restrict the transmission of letters based on recipient employee/station/union.

 Upload and configure new letter type.

Process Improvement changes/Value add

 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

As-Is System To-Be System

Data Tier Existing Jobs were created in Jars Control M

Web &
Application Tier API are hosted in Jboss Server API are hosted in WebSphere Server

User Interface HTML Screens Angular JS

Shared infrastructure with other


Infrastructure Dedicated Infrastructure for AO Application
Applications

11
Proposed AMS NFR Components

Authentication United Airlines Single Sign On Services will be used for User Authentication

User authorization is managed in the application database – Role based access.


Authorization
Role based privileges are granted to users.

Session Management Session state will be managed In-Proc

Exception Handling JEE/AngularJS will be used

Logging Log 4J Block will be used

Data Access HIBERNATE will be used.

Audit Trail Admin User action will be logged in the database for selected transactions.

Configuration Management Configuration Settings will be maintained in the database

12
Implementation Strategy

New Technology Stack

• Develop fresh SPA (Single-Page-Application) with Angular JS


• Develop business layer with JEE 6
• WebSphere Server
• Provide Mobile website

New Architecture

• New dedicated Infrastructure build up for New Data Center

AO Code Base Consolidation

• In the incremental builds, AO application code will be ported to


new infrastructure

13
Recommended Hardware and Software Requirements

S.No Hardware Details Specification

1 Web Server : 2 GB RAM, 100 GB HDD

2 Application Server : 8 GB RAM & 100 GB HDD

S.No Software Details Version

1 Node JS 4.4.3

2 AngularJS 2

3 Web Sphere 8.5.5

4 Database Server: Oracle 11g


5 Spring 4.0.1
6 RESTful Webservices in JEE 6
7 Java SDK 1.8

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

ETL ETL Architect Onsite AMS AO

ETL ETL Developer Offshore AMS AO

Angular UI Developer Offshore AMS AO

Java Tech Lead Onsite & Offshore AMS AO

Java Sr. Developer Offshore AMS AO

Java Jr. Developer Offshore AMS AO

Java Test Lead Offshore AMS AO

Java Application Tester Offshore AMS AO

Angular UI developer Offshore AMS AO

Project management Project Manager Onsite & Offshore AMS AO

Business Analysis Business Analyst Offshore AMS AO

User Interface UI Developer Offshore AMS AO

17
Commercials

Analysis and Total Duration


Projected Cost
Development Track Build Duration (+ EQA,
[approx.]
[approx.] Warranty)

AMS AO Development (Rewrite) 5 months 8.5 months $461,705

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

You might also like