Requirements Engineering

Review of Requirements
Management

Review Requirements Management

Always continually assess your requirements
engineering practices once the requirement
process begins, by periodically stopping your
work to examine practices and deliverables to
indentify improvement opportunities.
Ask team members which requirements practices
work and which ones do not work, making
modifications to the process.
Conduct a requirements process review at the
end of each iteration to ensure quality work and
additional improvement opportunities.
Review is the time to acquire and use lessons
learned to improve.
RED SUN Inc.

BIM Is A Risky Business

RED SUN Inc.

The Effect On Business

RED SUN Inc.

Root Causes

RED SUN Inc.

Primary Root Cause - 1

RED SUN Inc.

Primary Root Cause - 2

RED SUN Inc.

A Team Efforts

RED SUN Inc.

Requirements Models
Requirements models can:
Facilitate better communication between
technical and non-technical people.
Allow stakeholders to view different aspects of
the requirements.
Uncover missing, erroneous and vague
requirements.
Make requirements more interesting by using
textual description and visual models to clarify
requirements.
Improve stakeholders involvement.

RED SUN Inc.

Model Progression

Product

RED SUN Inc.

10

Model Progression

Product

RED SUN Inc.

11

Analyze System Behavior

RED SUN Inc.

12

Analysis & Design - 1

Model

RED SUN Inc.

13

Analysis & Design - 2

RED SUN Inc.

14

Model Progression: Test

RED SUN Inc.

15

Requirements Engineering
A systematic approach to eliciting,
organizing, and documenting the
requirements of the system, and a process
that manages the changing requirements
of the system.

RED SUN Inc.

16

What Are We Managing?

RED SUN Inc.

17

What Do We Need?
In order to manage requirements we
need:
Skills to elicit requirements from users and
stakeholders of the system.
Tools and methods to organize the
requirements.
Documentation to support communication of
the requirements.

RED SUN Inc.

18

Skills

RED SUN Inc.

19

Methods & Tools

Defining a Process
Organizing Requirements
Establishing Requirements Traceability
Change History
Tools and Tools Integration

RED SUN Inc.

20

Defining A Process

RED SUN Inc.

21

Organizing Requirements

RED SUN Inc.

22

Establishing Requirements Traceability

RED SUN Inc.

23

Change History
As requirements evolve, understand what
changed, when and why.
Version requirements and their associated
design and implementation artifacts.
Allow for change to be managed
incrementally.

RED SUN Inc.

24

Tools & Tool Integration

Organizing and establishing traceability
links requires some form of tool support.
Tools may be as simple as Excel
spreadsheets and Word documents.
But, projects of medium and large size will
be better served by more integrated tool
support.

RED SUN Inc.

25

Documenting Requirements
Use Case
Models
Supplementary Specifications
A Use Case describes the sequence of
actions a system performed that yields
observable results of value to a particular
actor.

RED SUN Inc.

26

Use Case

RED SUN Inc.

27

Models

RED SUN Inc.

28

Supplementary Specification
Capture the system requirements that are
not readily captured in behavioral
requirements artifacts, such as use cases.
For example:
Quality attributes
Legal requirements
Regulatory requirements
Design constraints
Implementation constraints

RED SUN Inc.

29

To Sum Up: The Problem

RED SUN Inc.

30

To Sum Up: The Opportunity

When your BIM requirements are complete
and accurate and you catch requirements
errors and omissions early in the project
then you have:
Much better chance to deliver BIM on time and
within budget.
Significant cost savings by avoiding rework.
More new system benefits can be realized.
Satisfied customers and users.

RED SUN Inc.

31

Questions & Answers

RED SUN Inc.

32