Home • Transform the Business • Grow the Business • Run the Business • A PMO Implementation Path • Training Programs • About Us • Contact Us
Objective
Surveys have shown that poor
requirements processes are a major factor in software project failures.
Requirements form the foundation for all the software work that follows.
Arriving at a shared vision of the product to be developed is one of the
greatest challenges facing the software project team, and customer involvement
is among the most critical factors in software quality. The objective of this
seminar is to give attendees a tool kit of practices, reinforced with practice
sessions and group discussions that they can begin applying to improve the
quality of the requirements development and requirements management processes in
their organizations.
Many organizations are adopting
A Guide to the Business Analysis Body of Knowledge (IIBA BOK),
from the International Institute
of Business Analysis, and the related Certified Business Analysis Professional (CBAP)
certification, as the primary sources of competency in the field of Business
Analysis. This seminar is based, in part, on Karl Wieger’s textbooks,
Software Requirements and More About Software Requirements, that are
referenced in the IIBA BOK.
Who Should Attend?
Requirements and business analysts,
project and product managers, user representatives, software engineers,
marketers, and anyone else engaged in eliciting, documenting, analyzing, or
managing customer requirements for software applications.
Course Outline:
(Practice
activities are shown in italics)
I. Introduction to Requirements Engineering
-
Introduction
to seminar, objectives, participant expectations
-
Define three
levels of software requirements: business, user, and functional
-
Describe
characteristics of high-quality requirements
-
Requirements
development vs. requirements management
II. Practice session: Small group discussions on requirements problems in
their projects
III. Software Requirements Development
-
A
requirements development process
-
The role of
the requirements analyst
-
The
customer-development partnership
-
The vision
and scope document
-
Practice
session: Drawing a context diagram
-
Sources of
requirements
-
Classifying
requirements into categories
-
User classes
-
Customer
involvement in the requirements process: the product champion model
-
Eliciting
user requirements through use cases
-
Practice
session: Describing a use case for an airline reservation kiosk
-
Business
rules
-
Practice
session: Writing business rules
-
Documenting
requirements: the software requirements specification
-
L.
Requirements management tools
-
M. Practice
session and discussion: Reviewing a portion of an SRS
-
N. Practice
session: Examining requirements for problems and rewriting them
-
O.
Prioritizing requirements
-
P. Software
quality attributes
-
Practice
session: Writing quality attributes
-
Q. Using
analysis models to represent requirements graphically
-
R. Modeling
user interfaces with dialog maps
-
Practice
session: Drawing a dialog map from use cases
-
S. Reducing
the expectation gap through prototyping
-
T.
Requirements validation practices
IV. The Capability Maturity Model for Software (optional module)
-
Intent and
structure of the CMM
-
Requirements
and the CMM
-
Some process
improvement principles
V. Software Requirements Management
-
Requirements
management goals and practices
-
Version and
change management
-
Requirements
change impact analysis
-
Requirements
traceability
-
Requirements
and software risk management
VI. Practice session: Designing a requirements change control process
VII. Practice session: Small group discussions on solving requirements
problems
VIII. Improving Your Requirements Practices
-
The process
improvement change cycle
-
Practice
session: Writing a requirements process improvement action plan
IX. Wrap-up
Copyright © 2008 PMO To Go LLC. All
rights reserved.
Questions or comments about the web site? Please
email
us.
Revised:
02/06/08.