2. Project Vision & Use Cases

Question 1

Product vision

Answer 1

What we ultimately want to accomplish
in order to achieve the business objectives

Question 2

Project scope

Answer 2

What portion of the vision
we will address in the
upcoming project/release

Question 3

Vision and Scope Document Template

Answer 3

1. Business requirements
2. Scope and limitations
3. Business context

Question 4

Business requirements includes

Answer 4

1. Background
2. Business opportunity
3. Business objectives
4. Success metrics
5. Vision statement
6. Business risks
7. Business assumptions and
   dependencies

Question 5

Scope and limitations inludes

Answer 5

1. Major features
2. Scope of initial release
3. Scope of subsequent releases
4. Limitations and exclusions

Question 6

Business context includes

Answer 6

1. Stakeholder profiles
2. Project priorities
3. Deployment considerations

Question 7

Business Requirements include

Answer 7

▪ 1.1 Background (“What triggered this?”)
▪ 1.2 Business opportunity (“Why does it look like we can be successful?”)
▪ 1.3 Business objectives (“Which benefits do we expect out of this?”)
▪ 1.4 Success metrics (“How can we tell whether we are successful?”)
▪ 1.5 Vision statement (“What will the product accomplish for whom?”)
▪ 1.6 Business risks (“What could jeopardize the product’s success?”)
▪ 1.7 Business assumptions/dependencies (“What are our plans based on?”)

Question 8

Scope and Limitations include

Answer 8

▪ 2.1 Major features (“What key things should the product be capable of?”)
▪ 2.2 Scope of initial release (“What should be rolled out first?”)
▪ 2.3 Scope of subsequent releases (“What can be rolled out later?”)
▪ 2.4 Limitations and exclusions (“What are we not going to do?”)

Question 9

Business Context

Answer 9

▪ 3.1 Stakeholder profiles (“Who has what interest in this project?”)
▪ 3.2 Project priorities (“What room is there for compromise?”)
▪ 3.3 Deployment considerations (“How will users obtain the product?”)

Question 10

Functional Requirements are

Answer 10

▪ Features
▪ Capabilities
▪ Business rules
▪ Security measures

Question 11

Quality (“non-functional”) Requirements are

Answer 11

▪Usability
▪Reliability
▪Performance
▪Supportability
▪Constraints

Question 12

What is a User Story ?

Answer 12

Very brief summary of a requirement

(e.g. “As a user, I want to create an account in order to save…”;

Question 13

What is a Use Case ?

Answer 13

▪ Brief format: Gives a precise idea of the interaction between user and system

(e.g. “The user enters a user name. The system checks… The user…”; → Slide 21)

▪ Casual format: Describes the user interaction in normal and exceptional circumstances

▪ Fully-dressed format: Provides explicit, detailed description of all aspects, alternatives and
constraints that developers need to understand for a high-quality implementation

Question 14

Use Case Terminology / Actor

Answer 14

Something with a behavior, e.g. a person (role), system or organization

Question 15

Use Case Terminology / Primary actor

Answer 15

Has user goals fulfilled through using services of system under development

Question 16

Use Case Supporting / Primary actor

Answer 16

Provides a service/information to the system under development

Question 17

Use Case Supporting / Offstage actor

Answer 17

Has interest in behavior of use case, but is not active in its execution

Question 18

Use Case Supporting / Scenario (or: use case instance)

Answer 18

▪ A specific sequence of (inter)actions between actors and the system
▪ One particular story of using a system, or one path through the use case

Question 19

Use Case Supporting / Use case

Answer 19

A collection of related success and failure scenarios
describing an actor using a system to support a goal

Question 20

Finding Use Cases

Answer 20

1. Choose the system boundary.
2. Identify the primary actors.
3. Identify the goals for each primary actor.
4. Define use cases that satisfy user goals.

Question 21

Use Case Writing Guideline: Black-Box Style

Answer 21

Do not describe the internal workings of the system, its components, or design.

Focus on describing the system’s responsibilities.

Describe what the system will do, but not how it will do it.

Question 22

Use Case Writing Guidelines:
Actor-Goal Perspective

Answer 22

Write requirements focusing on the users/actors of a system, asking about their goals and typical situations.

Question 23

Beware of Singular Up-Front
Requirements Elicitation

Answer 23

Software projects are exposed to 25%-
50% requirements change on average.