Business_RequirementsReference_numberDocument_ControlChange

Business Requirements

Reference number:

Document Control

Change Record

Date	Author	Version	Change Reference

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

Provide a short, yet complete, overview of the project.

1.2 Background including current process

Describe the background to the project, (same section may be reused in the Quality Plan) include:

This project is

The project goal is to

The IT role for this project is

1.3 Scope

1.3.1 Scope of Project

The scope of this project includes a number of areas. For each area, there should be a corresponding strategy for incorporating these areas into the overall project.

Applications In order to meet the target production date, only these applications will be implemented:

Sites These sites are considered part of the implementation:

Process Re-engineering Re-engineering will

Customization Customizations will be limited to

Interfaces the interfaces included are:

Architecture Application and Technical Architecture will

Conversion Only the following data and volume will be considered for conversion:

Testing Testing will include only

Funding Project funding is limited to

Training Training will be

Education Education will include

1.3.2 Constraints and Assumptions

The following constraints have been identified:

The following assumptions have been made in defining the scope, objectives and approach:

1.3.3 Risks

The following risks have been identified as possibly affecting the project during its progression:

1.3.4 Scope Control

The control of changes to the scope identified in this document will be managed through the Change Control, with business owner representative approval for any changes that affect cost or timeline for the project.

1.3.5 Relationship to Other Systems/Projects

It is the responsibility of the business unit to inform IT of other business initiatives that may impact the project. The following are known business initiatives:

1.3.6 Definition of Terms (if applicable)

List any definitions that will be used throughout the duration of the project.

●

Project Deliverable 2: Business Requirements Due Week 4 and worth 150 points This assignment consists of two (2) sections: a business requirements document and a Gantt chart or project plan. You must submit both sections as separate files for the completion of this assignment. Label each file name according to the section of the assignment for which it is written. Additionally, you may create and / or assume all necessary assumptions needed for the completion of this assignment. Procuring quality business requirements is an important step toward the design of quality information systems. Completion of a quality requirements document allows user needs and expectations to be captured so that infrastructure and information systems can be designed properly. Using the requirements document provided in the course shell, you are to speculate on the needs of the company. You must consider current and future requirements; however, assumptions should be realistic and carefully considered. Section 1: Business Requirements Document

1. Write an eight to ten (8-10) page original business requirements document for the project plan using the template provided. Note: The template can be found in the Student Center of the online course shell.

a. Describe the project including the following: i. Describe the scope and analyze how to control the scope. ii. Identify possible risks, constraints, and assumptions. iii. Describe the integration with other systems and infrastructure. Note: Database and interface design, security, and networking should be considered. iv. Define relevant terms that will be used throughout project.

b. Use at least two (2) quality resources in this assignment. Note: Wikipedia and similar Websites do not qualify as quality resources.

Your assignment must follow these formatting requirements: This course requires use of Strayer Writing Standards (SWS). The format is different than other Strayer University courses. Please take a moment to review the SWS documentation for details. Include a cover page containing the title of the assignment, the studentʼs name, the professorʼs name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length.

Section 2: Revised Gantt Chart / Project Plan Use Microsoft Project or an open source alternative, such as Open Project, to:

2. Update the Gantt chart or project plan (summary and detail) template, from Project Deliverable 1: Project Plan Inception, with all the project tasks.

https://blackboard.strayer.edu/bbcswebdav/institution/STANDARDIZED/StrayerWritingStandards/Strayer_Writing_Standards.pdf

●

The specific course learning outcomes associated with this assignment are: Apply integrative information technology solutions with project management tools to solve business problems. Use technology and information resources to research issues in information technology. Write clearly and concisely about strategic issues and practices in the information technology domain using proper writing mechanics and technical style conventions.

blog6