RUNNING HEAD: BUSINESS REQUIREMENTS

Business Requirements Lisa Schell Dr. Greg Hart CIS590 Directed Research Project May 2, 2013

Business Requirements

BUSINESS REQUIREMENTS

Reference number:

1234

Document Control

Business Requirements Change Record Date 5/1/13 Author Lisa Schell Version 1 Change Reference 1234

Reviewers Name Rich Tex Sally Smarts Scott Fortify Keith Hopewell Ryan Guarantee Position CEO, Co-Owner ISW CFO, Co-Owner ISW CIO, ISW CEO, Web Books CIO, Web Books

Business Requirements

Table of Contents
Document Control...........................................................................................................................................2 1 Business Requirements..................................................................................................................................5 1.1 Project Overview....................................................................................................................................5 1.2 Background including current process...................................................................................................5 1.3 Scope.......................................................................................................................................................6 1.3.1 Scope of Project.............................................................................................................................................6 1.3.2 Constraints and Assumptions.........................................................................................................................8 1.3.3 Risks...............................................................................................................................................................9 1.3.4 Scope Control.................................................................................................................................................9 1.3.5 Relationship to Other Systems/Projects.........................................................................................................9 1.3.6 Definition of Terms......................................................................................................................................10

Business Requirements

1
1.1

Business Requirements
Project Overview This project encompasses the IT integration of the two merging companies Internet

Shopping Warehouse (ISW) and Web Books. This project will be led by a newly hired Project Manager and ISW staff. The project will include the merger of software, hardware, network, and move of Web Books staff into the ISW building. The project will encompass all the research, setup, programming, installation, training, and post project follow-up needed for the IT integration of the merger. 1.2 Background including current process This project is a merger of IT infrastructure and employees between Internet Shopping Warehouse (ISW) and Web Books. ISW is online retailer providing a web based store front for its over 600 partnered businesses. Web Books is an online retailer that sells both electronic and hard copies of books. This merger will include Web Books products being sold through ISWs website and the closure of the Web Books website. All software, hardware and employee base from each company will be analyzed for use and optimization. The project goal is to complete this project with minimal impact to either companys employees and customers in addition to merging software and hardware to achieve the best results and prevent redundancy. The IT role for this project will be with direct leadership and buy in from CIOs of each company to complete the merger of systems including software, databases and equipment into ISWs infrastructure. ISWs analysts will be the leads in research, development and

Business Requirements implementation to complete this. Anything necessary needing to be done outside of scope or the agreed upon project plan will be taken to the ISW CIO for approval.

1.3 1.3.1

Scope Scope of Project The scope of the project is the IT merger of the companies Internet Shopping Warehouse

(ISW) and Web Books which includes databases, infrastructure and employees. This project will also consist of moving of Web Books employees into the same building as ISW employees. The project will occur over a 6 month period. A project manager will be hired to gather all resources required for the project, develop the proposed budget With the use of ISW application, network, and server analysts along with the project manager the plan will be to recognize, modify, and implement existing or new applications and infrastructure necessary for this merger. The project manager will also work with the Merger and Acquisitions team to plan any construction needed on the ISW office building and move of Web Books staff into the building and any budget required. Scope will also be to perform this as seamless as possible to not impact employees or customers along with minimal impact to operations and profitability. The primary applications that will be implemented will be any application that needs to be in place for customer information and ordering. Ideally human resources and payroll applications will be implemented or integrated as well if they do put the project completion date at risk. ISWs main location in Seattle, WA will be expanded to include Web Books employees. The building is three floors, with ISW currently renting one floor but the other two floors will be rented and remodeled to incorporate all staff within one building.

Business Requirements Web Books customers and distributors information will be incorporated into ISWs databases and managed under current ISW processes. ISW customer service will be the point of contact for previous Web Book customers and this information will be sent to those customers accordingly. If the implementation of the merger of human resources and/or payroll software does not occur within the project scope, these departments will continue to manage their employees separately until they can be incorporated. All security and network policies will remain under ISW policies. Customizations will be assessed for need by the analyst and only implemented if they

adversely will affect the project or the seamless transition of the merger. If there is customization that cannot be agreed upon for this need the project manager will take to one or both CIOs for approval. There will be no interfaces changed as all interfaced systems will remain those currently interfaced by ISW. There will be new VPN accounts and connections set up for Web Books distributors to access the customer and order databases. Current architecture will be analyzed to incorporate the most optimal merger of both companys applications. Technical architecture will be based off of ISWs current architecture following current network setup and security policies. Any technical changes found that may but any security at risk must be taken directly to the ISW CIO. All Web Books customer, order history and distributor information will be converted into ISW data formats and save to ISW databases. It will be decided after analysis if both ISW or Web Books human resources and payroll information are converted depending on the merger of those applications.

Business Requirements Testing will include any applications that are new to the current ISW infrastructure. The web site will be tested to make sure Web Books products are accessible. VPN connections

created for any new vendors or distributors will be tested for accessibility and security. Any new employee accounts created will be tested for accessibility and usability. The budget for this project will be projected by the project manager with possible use of outside expert resources and must approved by both companys CIOs. Any requests that would increase this budget must be escalated and approved by both CIOs. Training will be provided to all end users for any software that maybe new to them or contains new information. Any Web Book employee selected to be part of the server or networking teams will receive training of ISW infrastructure and network. Any of these employees that do not have current certifications in their respected fields will also be given paid training to achieve these certifications as deemed required by current ISW job descriptions.

1.3.2

Constraints and Assumptions The largest constraint will be the timeline of the project. There are many pieces that need

to be analyzed before decisions on the best route to take can be made. The project manager will be solely in charge of making sure project deadlines are made. The following assumptions have been made in defining the scope, objectives and approach: Besides the project manager all other project members will be current ISW staff.

All staff from both companies will be retained and allocated to different positions if found to be optimal.

Business Requirements

Until the merger is complete both CIOs will retain equal decision making rights. Any risk will be taken and decided between the two of them.

1.3.3

Risks

The following risks have been identified as possibly affecting the project during its progression: The timeline of the project has been identified as a possible risk. If the timeline is not met or deadlines cause project tasks to not be complete this adds the risk of not having a seamless merger as identified in the scope. The budge of the project is at risk as it will not be decided until after the project actually starts. Loss of Web Books customers is a risk due to them being transitioned to ISW customer support.

1.3.4

Scope Control The control of changes to the scope identified in this document will be managed through

the Project Manager and both CIOs for approval for any changes that affect cost, security or timeline for the project.

1.3.5

Relationship to Other Systems/Projects All databases and data warehousing of customer, order history, vendor and distributor information from Web Books will be integrated into ISW databases. Due to the increase

Business Requirements

10

of data server virtualization will be utilized as needed as deemed by the analyst to merge both companys data and software. Network infrastructure and security will be incorporated into ISW current infrastructure and security policies. The human capital needed to complete the project will be a network analyst, systems analyst, server/database team requiring analysts to represent each or both, a merger and acquisitions team made up of building managers and accounting personnel, testers, trainers, deployment personnel if analysts deem necessary, technical communicators, a externally hired project manager, a human resources representative, and management to assist in the personnel to be assigned to these positions. Future options of outsourcing are staffing for the 24/7 customer support center, staff to support the move and maintenance of an offsite data center possibly including a separate disaster recovery site. Cost projections for staffing, infrastructure, and other resources will be projected by the project manager as part of the projected budget for the project.

1.3.6

Definition of Terms VPN - A private network that is configured within a public network (the Internet or a

carrier's network) in order to take advantage of the economies of scale and management facilities of large networks. Virtual private networks (VPNs) are used by enterprises to create wide area networks (WANs) in order to provide site-to-site connections to branch offices and to allow mobile users access to the company LAN (PC World, 2013).

Business Requirements

11

References PC Mag. (2013). Definition of: virtual private network. Retrieved from http://www.pcmag.com/encyclopedia/term/53942/virtual-private-network Tee, C.B. (2002). Building a secure internet data center network infrastructure. SANS Institute InfoSec Reading Room. Retrieved from http://www.sans.org/reading_room/whitepapers/modeling/building-secure-internet-datacenter-network-infrastructure_73