Requirement
Engineering
Lesson 05+06:
Requirements
Development and
Management
It’s not just a simple matter of
writing down what the customer
says he wants !!!
Lecturer: Nguyễn Ngọc Tú
Email:

Web: sites.google.com/site/kythuatthuthapyeucauphanmem/
Outline
 Rules
 Best practices
2012.08
Requirement Engineering
2
[1] chapter 06
Learning Outcomes
 Know about the best practices that RA could apply
2012.08
Requirement Engineering
3
Rules
 Developing a thorough understanding of the practice;
 Communicating its value to coworkers and managers;
 Gaining commitment to trying the practice (piloting it);
 Providing some training about the practice so that
others understand it and what we are attempting to

Project
Management
1 Develop a requirements plan. X X X
2
Write requirements that meet the criteria of a good
requirement.
X
3
Identify and involve all of the stakeholders in the task or
project.
X
4
Ensure that the objectives of the task or project have
been identified, documented, and agreed to by the
stakeholders.
X
5
Use requirements workshops to achieve a shared
vision, facilitate commitment, and gain the buy-in of all
stakeholders.
X
6
Provide requirements training for RAs, for members of
the project staff, and for stakeholders.
X X X
7
Identify the real requirements. Collaborate with
customers and users concerning the stated
requirements to identify the real requirements. Look at
the requirements from multiple viewpoints.

and experienced in the functional areas being
addressed by the technical effort.
X
16
Quantify the ROI to select the requirements
mechanisms, practices, methods, techniques, and
tools to be used.
X X
Best Practices
2012.08
Requirement Engineering
8
Num. Best practices
Requirements
Development
RM
Project
Management
17
Identify the minimum requirements that meet real
needs.
X X
18 Prioritize requirements early and often. X X X
19
Provide inspections of all requirements-related
documents.
X X
20
Limit changes to requirements and the addition of new
requirements consistently, with additional budget and

Use proven and familiar requirements mechanisms,
approaches, practices, methods, techniques, and
tools.
X X X
25
Establish an agreed-on goal, purpose, or mission for
the task or project. Write (and iterate) a task or project
vision and scope document.
X
26
Develop, implement, and enforce meeting rules that
describe how project staff members are to treat one
another.
X
27
Develop and apply a set of guidelines for effective
meetings and guidelines for effective e-mailing.
X
28
Perform a risk assessment of new and changing
requirements.
X X X
29 Learn how to manage teams effectively. X X X
30
Establish a quality improvement and process
improvement climate.
X X X
Q/A ?!
2012.08
Requirement Engineering

1
Why are requirements errors so devastating and how can RAs help address the
problem?
2 What does the RA need to know about CM?
3 What does the RA need to know about the Unified Modeling Language?
4
What if I’m supporting a small project? Does any of this stuff still apply? How can I
convince the PM and my coworkers to incorporate a degree of discipline and
process into our approach?
5
What is the difference between a requirements specification and specifying the
requirements?
6
I notice “impact estimation” on the requirements skills matrix—what is it, and how
can I learn more about it?
7
You seem to suggest that the RA should be a leader on the project. Why do I need
to be a leader? How can I be a leader? What should I lead?
8
You have stressed the role of the RA in facilitating discussions, presentations,
meetings, training sessions, and workshops. What can I do to become a better
facilitator?
9
You have emphasized that having a defect prevention (DP) process is advisable for
all projects, perhaps necessary. Can you provide a DP process that I can
implement easily?
Question list
2012.08
Requirement Engineering
15

Requirement Engineering
16