Beruflich Dokumente
Kultur Dokumente
Requirements (SoBR)
Version: 1.0
Version Date: July 9, 2009
Revisions
Project Name: Corporate Intranet Redesign Project (Mock Scenario)
Prepared By: Trice Johnson Document Version No.:
Reviewed By: ―The Client‖ Review Date
Revision History
Ver. No. Ver. Date Revised By Description
1.0 06.09.2009 T. Johnson Mock version of a project for the July 9, 2009 IIBA Houston Chapter meeting
Distribution List
From Date Phone/Fax/Email
Trice Johnson 06.09.2009 In Person
* Action Types: Approve, Review, Inform, File, Action Required, Attend Meeting, Other (please specify)
TABLE OF CONTENTS
Revision History ............................................................................................................ i
Distribution List ............................................................................................................. i
1. INTRODUCTION ................................................................................ 3
2. EXECUTIVE SUMMARY .................................................................... 4
2.1. Problem Statement ............................................. Error! Bookmark not defined.
2.2. Business Need ................................................................................................... 5
2.3. Key Objectives ................................................................................................... 5
2.4. Stakeholder Matrix ............................................................................................. 5
3. SCOPE MANAGEMENT .................................................................... 6
3.1. Scope Objectives ............................................................................................... 6
3.2. In Scope Requirements ...................................................................................... 6
3.3. Out of Scope Requirements ............................................................................... 7
4. CONSTRAINTS, ASSUMPTIONS, & RISKS ...................................... 7
4.1. Constraints ......................................................................................................... 7
4.2. Assumptions....................................................................................................... 7
4.4. Risks .................................................................................................................. 8
5. GAP ANALYSIS ................................................................................. 8
6. AS-IS PROCESS MAP ....................................................................... 9
7. TO-BE PROCESS MAP ................................................................... 10
8. TO BE REQUIREMENT LIST ........................................................... 11
9. HIGH LEVEL FUNCTIONAL REQUIREMENTS ............................... 12
10. USE CASE SCENARIOS ................................................................. 13
11. USE CASE DIAGRAMS ................................................................... 15
12. DOCUMENT ORGANIZATIONAL SIGNOFFS ................................. 17
1. INTRODUCTION
The ―THE CLIENT‖ Statement of Business Requirements (SoBR) is intended for use by the
business/project sponsor, Subject Matter Experts (SMEs) and, development team, and internal
business analysts. It is intended to capture relevant business objectives and requirements salient
to the project or program to be developed. Specifically, this document is intended to:
Establish and articulate the prioritized business objectives
Establish existing / as-is business process flows and business scenarios
Clearly document the vision and needs of key stakeholders and/or project sponsors, in
addition to inputs from the Project Manager, technical lead, and development team
Document constraints, assumptions, dependencies and risks related to capturing and
documenting business requirements
Provide the functional requirements based upon and aligned with the business
needs/requirements from the sponsor, stakeholders, and Subject Matter Experts (SMEs)
2. Executive Summary
This document has been prepared for ―The Client‖ and key staff for business and technology
planning and design purposes.
The purpose of this document is to present an overview of the current business processes involved
in and associated with the organization‘s existing Intranet system. This document presents a
business architecture view that supports ―The Client‘s‖ goal to implement improvements to the
enterprise Intranet environment.
The SoBR is divided into five major parts:
Part 1 – Executive Summary: Provides a concise description of the business issue, and
provides insight on how the business expects the problem to be solved.
Part 2 – Scope Management: Describes the process for managing the ―The Client‖
requirements process, and for maintaining requirements baselines.
Part 3 – Constraints, Assumptions, & Risks: Constraints describe a circumstance that
poses as a bottleneck or restricts a process or system from achieving its potential.
Assumptions describe circumstances and events that need to occur for the project to be
successful but are outside the total control of the project team. Risks are circumstances or
events that exist outside of the control of the project team and will have an adverse impact
on the project if they occur.
Part 4- Gap Analysis: The gap analysis describes the variance between an organization‘s
existing processes, business requirements and current capabilities and process or
technology areas that require improvements.
Part 5- Statement of Business Requirements: A description of the current business and
the key issues and pain-points that should be addressed in the To-Be solution. This includes
the As-Is and To-Be process maps, requirements list, high level functional requirements, use
case scenarios, and diagrams.
3. Scope Management
The purpose of the Scope Management section is to describe the process for managing the ―The
Client‖ requirements process, and for maintaining requirements baselines. Having a clearly defined
scope helps to set expectations, and ensures that requirement tasks are executed with precision.
In scope refers to business requirements that will be defined, collected, or managed in Phase I of
this project.
This section identifies project constraints including restrictions or limitations, either internal or
external to the project or company organizations (i.e. sales, provisioning, operations, financial,
functionality, etc.) that will affect the performance of the Corporate Intranet Redesign project.
Constraints inhibit or hinder action; restrict the freedom in designing and delivering a solution.
Constraint ID Constraint Description
CONS-1 Scope modifications could negatively impact the scheduled delivery date of this product
The tight resource pool may constrain the ability of the project manager to ‗crash‘ the
CONS-2 schedule should that become necessary. ‗Crashing‘ is a process of assigning additional
resources to the critical path activities to reduce the overall project schedule.
4.2. Assumptions
This section identifies the critical assumptions that apply to the Customer Request (CR).
Assumptions are the conditions and factors of the project, environment, or personnel that are
considered true, real, or certain without proof or demonstration. These may include best-guess
decisions.
Assumption ID Assumption Description
ASUM-1 All proposed scope changes will be managed via structured Change Control Processes
An initial level of availability has been established for personnel assigned either part or
ASUM-2 full time to this project, and will be used as the basis for developing the project schedule
Both the business and IT will make every reasonable effort to minimize changes to
ASUM-3 agreed upon scope
4.3. Risks
This section identifies the outcome of the risk assessment that applies to the Customer Request
(CR) from a business perspective. A risk is an uncertain circumstance or event that, should it occur,
would have an adverse effect on the program/project‘s objectives.
Risk Ranking
Risk ID Risk Description
(Low/Medium/High)
Risk management will be conducted throughout the
RISK-1 project based on a methodology that reflects ―The High
Client‘s‖ policies & procedures
5. Gap Analysis
8. To Be Requirement List
X-REF
REQ-ID To-Be Requirement Title
(To-Be)
FR-10 System will rank page results based on algorithm determined by the process owners
(details in supplementary artifact)
Process Title: Navigation Tracking (“Breadcrumbs”)
System shall provide breadcrumb navigation, displaying a dynamically generated set
FR-11 of links at the top of Web pages, to show users their current position in the site
hierarchy