Database and Programming Design
favericw
Business_Requirement_Document_LaDerickClayton.docMoving to AWS
Business Requirements
Reference number: 01
Document Control
Change Record
|
Date |
Author |
Version |
Change Reference |
|
01/25/2019 |
Clayton |
1 |
original |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reviewers
|
Name |
Position |
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
2Document Control
1 Business Requirements 4
1.1 Project Overview 4
1.2 Background including current process 4
1.3 Scope 4
1.3.1 Scope of Project 4
1.3.2 Constraints and Assumptions 5
1.3.3 Risks 5
1.3.4 Scope Control 5
1.3.5 Relationship to Other Systems/Projects 5
1.3.6 Definition of Terms (if applicable) 5
1 Business Requirements
1.1 Project Overview
Move all datacenter systems to from onsite to AWS.
1.2 Background including current process
Move old servers and network equipment from our server room data to new systems hosted by Amazon.
This project is needed to move the company into the future
The project goal is to save the company money while still being able to use cutting edge systems.
The IT role for this project is lower overall cost but still improving the overall experience for the user.
1.3 Scope
1.3.1 Scope of Project
The scope of this project includes the following scopes. Each will be an overall breakdown of our current systems and what we hope to use going forward.
Applications SharePoint Microsoft Office, SAP Portal, Ordering Application, Mobile Application:
Sites www.cloudmove.com www.cloudmove.com/customer www.cloudmove.com/SAP www.portal.cloudmove.com :
Process Re-engineering Re-engineering will allow the company to decommission our onsite servers and begin using top of the line AWS servers.
Customization Customizations will be limited to what it takes to integrate our legacy application into AWS.
Interfaces The users interfaces will not change in most cases. They will still be accessing their tools from a web based client.
Architecture Application and Technical Architecture will change drastically. Everything will be hosted and served from an AWS datacenter and no longer from the current location.
Conversion Obsolete and unutilized systems will be decommissioned and not moved:
Testing Testing will include both the data center team and the users:
Funding Project funding is limited to the budget proposed by the PM and approved by the board
Training Training will be done onsite as by the design team for any outfacing changes.
Education Education will include both online training and in person onsite people.
1.3.2 Constraints and Assumptions
The following constraints have been identified:
· Old legacy systems must remain online and up until the final checkoff has been given by each user of that system.
· Must maintain Blue/Green scenario until final checklist is done.
The following assumptions have been made in defining the scope, objectives and approach:
· Users doing the testing know what to test for using real life work conditions.
1.3.3 Risks
The following risks have been identified as possibly affecting the project during its progression:
· Moving Legacy Applications designed on older equipment on to new servers
· Unexpected issues giving the move of old applications to the cloud.
· Cost of having to come up with rewriting or buying new applications to replace any that cannot be ported over to the new equipment.
· Having to train users on new applications, which comes with a learning curve.
1.3.4 Scope Control
To control time and cost no changes will be made to the scope unless approved by the Change Control Board as well and each department approver. Any approved changes will need to be approved by all departments just in case their change affects others areas.
1.3.5 Relationship to Other Systems/Projects
It is the responsibility of the different departments to keep an eye on the schedule of change and to notify the board of any times where the risk of downtime is not acceptable to the customer.
1.3.6 Definition of Terms (if applicable)
AWS – Amazon Web Services
AWS Route 53- Amazon’s web hosting
AWS RDS- Relational Database System
Blue/Green – Both old and new systems online at the same time
Project overview
The overall goal of this project is to move our current datacenter location at our headquarters building on to AWS’s cloud base datacenter. This will allow the company to same money as well as modernizing our systems for the future. This will also lower energy cost as well as total cost of ownership since we will only be paying for just what we use and nothing more.
Background including current process
The current datacenter is located on the ground floor taking up nearly the entire ground floor. We currently have to maintain enough power and cooling to run the older power hungry systems. We have to keep a backup generator on standby just in case the power goes out. We also have to maintain all the licenses for the Windows base systems some of which are end of life. Replacing and maintaining this old equipment requires upfront cost and people and space to maintain them.
S cope of Project
Applications:
There are many Applications and Databases that will have to be moved, upgraded and in some cases replaced.
· SharePoint Server
· Customer SQL Database
· Ordering Application
· Mobile Application
Sites:
There are 4 critical websites that are critical to keep the business flowing and cannot be down at all.
These sites are currently hosted internal using Microsoft IIS and will need to be moved to AWS Route 53 hosting using Nginx. This will require the old sites to be rewritten by the developers.
Process Re-engineering
In order to re-engineer the data center we must first survey our current usage and see if we are over or underutilizing our resources. This will allow us to design the new network to only use what we need. This will also allow us to create redundancy for critical systems such as the SAP database as well as secure them with firewall roles as ACLs.
Customization
There will not be much customizing of old resources. We will only do what is necessary to move to AWS. So far we have identified only 2 things that will need to be customized and those are the websites and the databases.
Architecture
The entire network architecture will be redesigned to reduce latency and efficacy for every application. We will design the web applications to no longer use resource heavy Microsoft SQL instead use Amazon’s RDS. This will save on license cost as well as resource cost since.
Conversion
We will need to convert all apps that are currently running on Microsoft Windows to use Linux in of all possible. This may mean upgrading the version or in some case finding alternatives.
Testing
When it comes to making sure things are ready to go for example when it’s time to move from the on-primase web hosting to AWS we must a real work load test done by accrual users. It must be real world tests. If all are good the old hardware can be moved to standby scenarios but still be in place for a set period of time just in case something unexpected comes up. All system must be check this way before the go ahead is given to power off the old systems.
Funding
Funding has been approved by the board with little room to spare. Since the goal of this project is to same money there will be little toleration for waste. If a team is found to be wasting resources the cost of said resources will be deducted from that teams yearly budget.
Training
User training should not be need much, only on the systems that are both forward facing and have been changed to fit the new environment. This could change if there are many new application put into place due to them being unable to move to the new platform.
Education
Our onsite trainer will need to go for training on any new applications that the end users will be needing. Allowing the onsite trainers to become experts at any new systems will same time getting the users up to speed.
1
