Business Requirements for Matrix Data Corporation - Case Study Example

Business Requirements 1 Project Overview The business requirements outlined below will describe initiatives for a new project called “Depository” in which the IT department will implement a data repository system for Matrix Data Corporation as a result, the current information system infrastructure will be revised to support the new implementation. The business requirements will used to review and approve the deliverable and also provide a guide of the set up process, introduce team players, and discuss the risk and the new system applications. When implemented, the Matrix Corporation will utilize a more robust data warehouse system. 1.2 Background including current process The Matrix Data Corporation in Owings Mills, Maryland is a company that collects data and analyses web-based data for large clients using Web analytics software. They have decided to add a new data repository system to enhance the sales allowing the company to grow by 20% each year. In order to support the volume expected the IT’s role will be to upgrade the current data warehouse system from a ten (10) terabyte data warehouse to 60 terabyte allowing Matrix Data Corporation to collectdata beyond the standard relational databasesystems. This project goal is to provide guidance on the implementation process and how the changes will administered. The project is scheduled to begin on November 21, 2012 and the expected end date is December 23, 2012. The project will also identify what is needed to make the change and to accomplish these changes without interfering with current business production. 1.3 Scope 1.3.1 Scope of Project The scope of the will identify the procedures used to coordinate the project and the users, and stakeholders to ensure the needs are met. Applications –Will be implemented in phase 1 by November 15, 2012. Database – The application will use a MSSQL (SQL Server) database System Hardware –Data repository system is required. Matrix Corp. will provide the custom software. Applications will be implemented under the support Delivery framework and strategic alignment and the System Development Life Cycle (SDLC). Sites – The site(s) involved are: Matrix Corporation, 3800 McLean Blvd Owings Mills, MD 21117. ADP Transmission (vendor) 14454 Painters Mill Road, Owings Mills MD 21117 Conference calls will be held twice a week to start this process. Process Re-engineering will highlight four phases; 1) Initiation – Aimed at identifying and understanding the purpose 2) Analysis – An in depth analysis of the process tasks and process 3) Reengineering – Discuss and design features needed 4) Implementation and evaluation – Address stakeholders issues and concerns  (Carr and Johansson, 1995). Customization - customization can be applied throughout the different layers of the new project delivery process, from the network diagram level to the scope of work associated with specific activities. The SDLC methodology will be used to implement changes. Interfaces – Agile methods will be integratedto provide delivery engines (Griffith 1994) and new system hardware to be set up and will be implemented using the SDLC methodology. Architecture – The application and technical architecture is a formal description and representation of a system, organized in a way that supports reasoning about the structure of the system which comprises system components. Conversion –AdWords Conversion Tracking will begin importing the data from the Analytics account,  Testing – Testing will include testing on volume and capacity, and performance. Funding –Project funding is limited to $25,000.00 Training - Training will be held every Monday in conference room C, for 1 hour. e provided weekly Education – will include an in depth overview of the process and slides will be provided. 1.3.2 Constraints and Assumptions The following constraints have been identified: Restricted and limit project execution, budget limit of $10,000.00. The following assumptions have been made in defining the scope, objectives and approach: Need to modify the deliverable to meet schedule and budget. 1.3.3 Risks The following risks have been identified as possibly affecting the project during its progression: Technology and infrastructure uncertainty with use outdated system software. Use of unproven technology 1.3.4 Scope Control This process will be used to ensure changes to the system are introduced in a controlled and coordinated manner. It reduces the possibility that unnecessary changes will be introduced to a system without forethought, introducing faults into the system or undoing changes made by other users of software. (Griffith, 1994). The Change Control process will run continuously during the project, and potentially beyond that into live running. The Project Office team and the Project Manager will administer and control the process.(Griffith, 1994). The Change Control process will involve the following procedures, responsibilities and systems. on what basis changes should be approved, who does what,membership of the Change Control Board(s), the detailed procedures, forms, etc, protocols for levels of authority, eg what types of change can be approved without reference to the project's business owners, linkage to other management procedures, the issue management process, configuration management, which tools will be used to support and manage the process, how to communicate and promote the process and its importance to all participants. (Griffith, 1994). 1.3.5 Relationship to Other Systems/Projects -Systems Integration (Allen, Finfield 1995) ensures that businesses can begin to operate more holistically, with systems working together to build a corporate memory and much deeper relationships with customers and business partners. Getting the old and new systems working together opens the way for greater co-operation, speedier access to data and a much better grasp of resources. Methods of integration to be considered are: Vertical Integration is the process of integrating subsystems according to their functionality by creating functional entities also referred to as silos. Star Integration or also known as Spaghetti Integration is a process of integration of the systems where each system is interconnected to each of the remaining subsystems. Horizontal Integration or Enterprise Service Bus (ESB) is an integration method in which a specialized subsystem is dedicated to communication between other subsystems. This allows cutting the number of connections (interfaces) to only one per subsystem which will connect directly to the ESB. (Allen, Finfield 1995). 1.3.6 Staffing and resources needed are; Product Manager, responsible for short and long term projects. IT managers, responsible for monitoring operations, and researches strategies and solutions, Information systems manager, in charge of systems planning, Information technology director, maintains policies and procedures in security and risk management; Chief Information Security Officer, establishes and maintains security and risk management ; Technical managers, in charge of network and systems administrations.(Schneider, 2011). Bibliography Allen, D., &Fifield, N. (1999).Re-engineering change in higher education. Information Research, 4(3).http://informationr.net/ir/4-3/paper56.html Carr, David K. & Johansson, Henry J. (1995). Best Practices in Reengineering: What Works and What Doesn't in the Reengineering Process. New York, NY: McGraw-Hill, Inc. Griffith, M. (1994), Agile Interfaces, Leading answers typepad.com. Retrieved November 2, 2012 from: http://leadinganswers.typepad.com/leading_answers/files/agile_interfaces_pmo_integrati on.pdf Schneider, L. (2011) About.com, Tech Careers, Retrieved November 1, 2012 from: http://jobsearchtech.about.com/od/careersintechnology/a/CIO.htm Read More