Chapter Summary

Chapter 5:

Establishing the Business Requirement

1

5.1 Business Requirements

 Top level of abstraction ◦ User requirements, system functional

requirements are subordinate ◦ Don’t include any that don’t address business

objectives

 Project participants shouldn’t work against each other

 All stakeholders need to have the same understanding of business objectives

2

Defining the Vision & Scope

 Product vision ◦ Ultimate long-term goal ◦ Changes slowly

 Project scope ◦ Short-term objective (shows which part of

the vision is addressed) ◦ Covers one release of product ◦ Adapts to constraints (cost, schedule,

resources, quality)

3

Requirements Will Conflict

 Customer wants simplicity  User wants convenience, features  Developer wants high-tech excitement  Manager wants predictability (and profit)  Sponsor must resolve conflicts involving

business stakeholders; not all can be pleased

4

Business Requirements and Use Cases

 Business requirements determine: ◦ How many use cases are included ◦ How extensively each use case is

implemented ◦ The priority of each use case

5

5.2 Vision and Scope Document

 Always a single document, even when multiple systems will be developed

 Always owned by project sponsor (executive, funding authority,…)

 Input comes from various sources ◦ Stakeholders ◦ Subject-matter experts

6

Document Outline

7

1. Business Requirements

1.1 Background (decision to build product) 1.2 Business Opportunity 1.3 Business Objectives 1.4 Success Metric 1.5 Vision Statement 1.6 Business Risks 1.7 Business Assumptions and

Dependencies

8

2. Scope and Limitation

2.1 Major Features 2.2 Scope and Initial Release 2.3 Scope and subsequent releases 2.4 Limitations and Exclusions

9

3. Business Context

3.1 Stakeholder Profiles (value from product, attitude, features of interest)

3.2 Project Priorities (constraints, drivers, degrees of freedom)

3.3 Deployment Considerations (locations, times, performance, reliability, integrity)

10

5.3 Scope representation Techniques

1. Context Diagram

11

The System

Interface

Interface

Interface

Interface

Interface Information

Flows

Information Flows

Information Flows

Information Flows

Information Flows

12

2. Ecosystem Map

13

3.Feature Tree

14

Keeping the Scope in Focus

 Prevent scope creep (or gallop, or warp speed)

 Accommodate evolving needs  Three decisions for a proposed

requirement: ◦ In scope, keep it ◦ Out of scope, discard it ◦ Out of scope but really good idea, change

scope

15

E N D

16