Project Plan
Project Deliverable 2: Business Requirements
By: Justin M. Blazejewski
CIS 499
Professor Dr. Janet Durgin
4 November 2012
Document Control
Change Record
|
Date |
Author |
Version |
Change Reference |
|
11/4/2012 |
JMB |
7.1 |
First attempt at Project Del. 2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reviewers
|
Name |
Position |
|
Justin Blazejewski |
Chief Information Officer |
|
|
|
|
|
|
|
|
|
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
A data collection and analysis company aims at upgrading the information system infrastructure and establishing new components of information system.
1.2 Background including current process
This project is to ensure that new upgraded information system infrastructure must support the expected company’s growth i.e. 60%, in next 18 months.
The project goal is to Goal – The project aims at upgrading the company’s information system infrastructure which provides data collection and analysis services.
The IT role for this project - IT plays a very important role. Right from data collection to data analysis, at every step IT is being deployed. Data collection tools, data analysis tools and data warehouse are heavily used by the company in accompanying its business goals.
1.3 Scope
1.3.1 Scope of Project
Applications - In order to achieve its goals, company uses following tools:
a) Data collection tools
b) Web Analytics tool
c) Resource tracking application
Information System specialist will be responsible for carrying out these tasks.
Sites - At offshore, data collection is being carried. Data processing and analysis is done at onsite. Project managers at both sites will prepare the project plan for their respective sites.
Process Re-engineering - IT Re-engineering implementation can be divided into three phases: before the process is defined, during process designing and after the process is designed. Re-engineering will include defining new business opportunities by re-defining the processes, proficient database utilization and data mining. Information System Specialist will be responsible for it.
Customization - Customizations will be limited to improvement of old hardware with new infrastructure. Network engineer along with Information System Specialist will be responsible for this task.
Interfaces - The company’s IS has interfaces for evaluating data i.e. reports defined by users with MS Office (Excel and Microsoft word), standard components of software like Crystal reports and Business Objects. Licensed software will deal by the human resource team.
Architecture – Application and technical architecture will be designed once the requirements are approved by the senior management.
Application architecture:
Presentation Layer
(Web User-Interface)
Query Processor
Persistence Layer
Technical architecture:
Windows GUIInternet BrowserWindows DevicesCustom MacrosInterfaces
Common Business Logic Interface (API, XAPI)
Distributed Process Server
Common Database Server Interface (API)
MySQL
Conversion - Since company is not very old, so all of the online data will need to be converted in new format as per the upgraded infrastructure.
Testing - It will include integration testing, load testing, tuning and network testing
Funding - It is limited to $1million
Training - It will be include sessions on using new hardwares, softwares, and technologies. Functional lead will lay down the training plan.
Education - It will include Bachelors of Engineering and certification in information systems.
1.3.2 Constraints and Assumptions
The following assumptions have been identified:
· Finance & Marketing activities for the training organization are out of scope of this engagement
· Signoff for the various project artifacts happen within 4 working days to ensure the project is complete on time. And if there are any recommended changes in the artifacts then those are been notified
· 100% funding has been from sponsors
· Economic conditions like land & infrastructure prices are relatively stable
· Availability of minimum skilled labor is there to start the project
· Government Rules and Regulations would be stable.
· Functional lead, technical lead, database administrator are already been recruited.
The following constraints have been identified:
· The upper limit for the expected budget should not be exceeded by 10%. In case of overshooting of budget within 10% range, the additional capital will be raised through loans or VC funding.
· The upper limit for the expected time should not be exceeded by 45 days. The assumptions of stable government policies, economic conditions may not hold true after 45 days.
1.3.3 Risks
The following risks have been identified as possibly affecting the project during its progression:
|
# |
Risk Area |
Project Impact-Mitigation Plan |
|
1 |
Economic Downturns |
Unmet budgetary constraints – Identify locations within company’s location area which are cheap and have less fluctuations |
|
2 |
Technology Changes |
Obsolete IT Infrastructure – Take correct sizing decisions by studying the market |
|
3 |
Technology Changes |
Increased Opportunity Cost – Need to purchase the right configuration at the right time, only possible by a proper market study |
|
4 |
Project Schedule |
Milestones not achieved & Budget may be exceeded – Use another vendor and have constant follow-ups to decrease delay |
|
|
|
|
|
# |
Risk Area |
Risk |
Probability** |
Impact** |
Probability*Impact |
|
1 |
Economic Downturns |
Fluctuating real estate prices |
Low |
High |
High |
|
2 |
Technology Changes |
Hardware & Software Upgrades |
High |
High |
Critical |
|
3 |
Technology Changes |
Decreasing IT Infra Cost |
Med |
High |
High |
|
4 |
Government Processes |
Delay in Company Registration |
High |
Med |
Medium |
|
5 |
Project Schedule |
Vendors not meeting deadlines |
Low |
High |
High |
1.3.4 Scope Control
· If budget changes, then look out for new sources of funds.
· If project schedule changes it may require fast tracking, crashing or re-base lining of the schedule depending on the significance of the impact.
1.3.5 Relationship to Other Systems/Projects
Client business will need to notify about the up gradation such as if the company is serving healthcare domain then probable delay in transferring information.
1.3.6 Definition of Terms (if applicable)
NA
1
_1412180285.vsd
�
Presentation Layer (Web User-Interface)
Query Processor
Persistence Layer
_1412180348.vsd
�
�
Windows GUI
Internet Browser
Windows Devices
Custom Macros
Interfaces
Common Business Logic Interface (API, XAPI)
Distributed Process Server
Common Database Server Interface (API)
MySQL