CIS Project Deliverable 3
Project Deliverable 2: Business Requirements
Strayer University
CIS498
May 1, 2017
Table of Contents
1Business Requirements 3
1.1Project Overview 3
1.2Background including current process 3
1.3Scope 4
1.3.1Scope of Project 4
1.3.2Constraints and Assumptions 6
1.3.3Risks 7
1.3.4Scope Control 7
1.3.5Relationship to Other Systems/Projects 8
1.3.6Definition of Terms (if applicable) 8
1.4References 8
- Business Requirements
- Project Overview
This project is aimed at deploying a new and improved information system to Knight Inc as it prepares to merge with Krypton Corporation. The company will also be moving into new premises where the information system infrastructure will be installed. The information system is expected to be capable of handling not only the current data requirements, but also the increased growth in the next few years.
- Background including current process
This project will be supervised by the company’s chief information officer (CIO) who will not only ensure that the technical requirements are met but also the company own business objectives. The overriding goal of this project is to make sure that Knight Inc has been provided with the capabilities to handle its operations in the smoothest way possible with little to no downtime. The project team will also be expected to adhere to the highest levels of professionalism on the work and make efficient use of the available resources. The IT personnel of Knight will play a central role in the success or not of this project. As the people responsible for delivering this project, they will conduct most of the necessary tasks for this project. The current process of the company includes an e-commerce site that is used to serve the customers of the company.
- Scope
- Scope of Project
- Scope
The database, cloud technology, network security and productivity tools will be the main applications to be developed with project. These will be responsible for the whole breadth of the company’s operations. The successful implementation of the applications should ensure smooth data processing and security for the network while that is being done. (Peltier, 2013).
The company will be moving to new premises and these will be the central site of the implementation of the project. As the place where the company’s employees will be located, it will be important that the information system be placed there for them to conduct their duties without problems.
With process re-engineering, the company will have to change how it conducts its operations. These will have to be aligned to the new information system. These changes will range from mild to complete turnarounds. The purpose of process re-engineering will be to ensure that the company can fully experience the new information system and its benefits. (Baltzan, 2012).
Even with the above process re-engineering, there will be some aspects of the new information system that will require a different approach. For the e-commerce site, it will be customized to keep with the current way it is to avoid confusing customers. Other customizations might include employee systems so as to reduce the need for too much training of the employees on the new system.
Interfaces will not change much. To maintain a sense of familiarity, they will be kept as they are save a few changes for efficiency purposes. The interfaces for both employees and the storefront for customers will require different approaches but will otherwise largely remain as they are. (Baltzan, 2012).
Application and architecture will have to be merged in such a way that they not only smoothly work together, but also ensure that they are able to meet future demands and requirements. This is because any changes to one of them might necessitate changes in the other and that would not be cost effective. As such, they should both be implemented in a way that allows them to be fully compatible with future developments.
The data to be converted will be the one currently held in the company’s relational database as it seeks to migrate to the more dependable and efficient data warehousing model. Most of the data being converted will be the operational data required for the smooth functioning of the e-commerce site. (Baltzan, 2012).
Testing will include only most user oriented aspects of the information system. Given that this will be the most visible aspect of it, it will require thorough testing before it can be deployed. This is to make sure that no problems arise later that would lead to the entire network being shut down and inconveniencing users.
Project funding is limited to the company’s own resources. This then places pressure on the project team to prudently utilize the resources put at their disposal. The budget will also dictate the duration of the project and this too must be kept within the required timelines.
Training and education will depend on the outcome of the project. While entirely new systems will require that employees be taught from scratch on how to use them, others will simply involve short-term training for improved systems. Security will form a vital part of the training and education to safeguard the information system. (Baltzan, 2012).
- Constraints and Assumptions
The constraints of this project have been identified as the deciding on the size company’s data operations in the future. This could change in whichever way within the period planned upon. It could higher or it could remain constant or experience unexpectedly low growth. These constraints mean that there be unused capabilities as a result of slow growth or non-available capabilities should the growth surpass expectations.
With the assumptions, the team will make reasonable estimates of the growth. This will take into account the current state of the company’s operations, market factors and the company’s own growth strategy over that period. They will however be made to be flexible enough to accommodate changes in future. (Lock, 2013).
- Risks
Information breach has been identified as the biggest risk during this project duration. This is because the activities of the project are likely to make the data vulnerable. An external party could attack and steal data or a member of the project team might inadvertently jeopardize the data. Ample security measures will be required throughout the project. (Peltier, 2013). The project could also face the risk of budget shortfalls and unmet deadlines. These are actually very plausible and will therefore to be checked on. The project could be disrupted by power and system failures which could also derail the project.
- Scope Control
To ensure the success of the project and fulfillment of the requirements as set out, change control will be used during the project. The project will need to be in constant communication with the company’s management. They will need to communicate to the any changes they wish to make to the project terms and come to an agreement before the changes are implemented. The company’s management will need to ensure that they do not make changes to the project midway that would affect the nature of the project or its delivery. Any changes to the scope will need to be carefully and thoroughly documented. (Lock, 2013).
- Relationship to Other Systems/Projects
The project team will be responsible for informing the other business units of the impact of the project on their operations. The business units will also need to do the same and inform the IT team of developments in their units that might affect the project. Business initiatives that are being considered include an expansion of the product line which might require to be considered when developing the database. Other initiatives include use of different accounting software by the finance department. All these varying business initiatives will have a bearing on the project and it is important that they be considered exhaustively. (Laudon, & Traver, 2016).
- Definition of Terms (if applicable)
The following terms will be used during the project and to avoid ambiguity, their meanings are as follows.
The company – this will mean Knight Inc.
Employees – these are the people working for Knight Inc.
Customers – these are the individuals that make purchase from the site of Knight Inc.
- References
Lock, D. (2013). Project management.
Peltier, T. R. (2013). Information security fundamentals. CRC Press.
Laudon, K. C., & Traver, C. (2016). E-Commerce 2016: Business, Technology, Society. Pearson Higher Ed.
Baltzan, P. (2012). Business driven technology. McGraw-Hill/Irwin.
9
