WRITING THE

REQUIREMENT
JUST THE BASICS, PLEASE
JOHANN LOHRMANN

THE REQUIREMENT PROCESS

Functional
Requirements

Software
Requirement
Specification

UAT (User
Acceptance
Testing)

Change
Management

THE BASIC STRUCTURE

Theme
Epic
Story
3

THE BASIC DEFINITIONS

Theme
Epic

User Story
Use Case

Collection of User Stories

A big user story

Something the end user wants

The detailed requirement
4

USER STORY VS. USE CASE

A user story is the What

and Why.
a use case is the How.
5

A User Story is part of the

play in front of
the black curtain.
6

A Use case is everything

that happens behind the
black curtain.
7

WORKING WITH
USER STORIES
THE BASICS

FROM THEME TO USER STORIES.

Theme
Work toward
a goal.
Georgia
Lottery
Corporation
provides a
secure system
for end users.

Epic
User Stories
Big user story. Something the
user wants.
As an end
As a salesperson,
user, I'd like to I want to be able
set my
to edit my profile,
password, so I so I can set my
can log into
password.
the system.

USER STORY FORMULA

As a(n) ______ (actor) I

want to ______ (do
something) so that I can
_____ (end result).
10

USER STORY: RELATED TO THE

BUSINESS UNITS
Finance

Legal

Operations

Technical

11

USER STORY PRACTICE

Finance user story

Legal user story
Technical user story
Operations user story
12

USER STORY RESULTS

As an administrator, I'd like to ensure that all
salespeople's passwords meet corporate strength
requirements, so I can harden access to the system.
As an administrator, I'd like to send an email to a new
salesperson containing a tokenized access link, so they
can temporarily access the system in order to set their
password.
13

USER STORY RESULTS

As an administrator, I want to send an email to a new
salesperson containing a tokenized access link, so that
the salesperson can temporarily access the system in
order to set their password.
As an administrator, I want to ensure that all
salespeople's passwords meet corporate strength
requirements, so that I can harden access to the system.
14

WORKING WITH
USE CASES
THE BASICS

15

USE CASES: THE MAIN PARTS

Use Case Number
Application
Use Case Name

Use Case Description

Primary Actor
Precondition
Trigger
Basic Flow
Alternate Flow

16

USE CASES: INSIDE THE DOCUMENT

Current Functionality
Limitations
Risks

Assumptions
Requirements
Business Rules

Vendor Tasks and Assumptions

Impact

17

USE CASE TERMS

Basic Terms
Basic flow

Definition
Most common implementation. Assumes
no errors or alternatives exist.
Alternate Flow Alternative implementations. Describes
error conditions.
Constraint
Limitation or state. Example: data range of
values, behavior of the application. Required
state at particular point in time.
18

USE CASE TERMS

Basic Terms Definition
Precondition A constraint that must be true when a
use case is invoked.
Postcondition A constraint that must be true when a
use case has ended.
Relationship A semantic connection between
model elements. Examples include
associations, dependencies, and
generalizations, extend, and include.
19

USE CASE TERMS

Basic Terms
Unified Modeling
Language
Use Case
Diagram
Use Case Model

Definition
Visualize the design of a system.

A UML diagram that shows actors,

use cases, and their relationships.
A model that describes a systems
functional requirements in terms of
use cases.
20

BASIC MODELS
21

EXAMPLE: UNIFIED MODELING

LANGUAGE (UML)

22

EXAMPLE: USE CASE DIAGRAM

23

EXAMPLE: USE CASE MODEL

24

WRITING THE
REQUIREMENT
JUST THE BASICS, PLEASE
JOHANN LOHRMANN