Requirement
Engineering
Lesson 02:
The Roles, Skills and
Characteritics of the RA
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
 Suggested Roles of the RA
 Skills of the RA
 Characteristics of an Effective RA
2012.08
Requirement Engineering
2
[1] chapter 02, 03
Learning Outcomes
 Understand the roles and characteristics of RA
2012.08
Requirement Engineering
3
Issues

2012.08
Requirement Engineering
4
[1] chapter 02, p030

Operations &
Supports
Work collaboratively to identify the real
requirements …
X X A A A A
Work effectively … to manage new and
changed requirements …
X X X X
Be alert to new technologies that may
help.
X X X
reusing artifacts and achieving
repeatability.
X X X X
Assist the project and its customers in
envisioning a growth path …
X X X X X X
Advise the project (and customer) of
methods, techniques, and automated
tools …
X X X
Use metrics to measure, track, and
control …
B X X X X X
Be able to facilitate discussions and to
mediate conflicts.
X X X X X X
Study the domain of the area … X X X
A—Continue to identify real requirements for subsequent releases and revisions, maintaining configuration control.
B—System initiation or “project or task startup” is a confusing time. The experienced RA will be able to lend assistance. For

 Involving system architects in requirements development.
Iterating the draft or proposed requirements will result in
a candidate architecture with better requirements and a
more robust architecture. For example, systems need to be
able to accommodate changing business needs. The
architecture should be designed and developed
accordingly, or else the delivered system soon will be
outdated.

 Utilizing an industry strength automated requirements
tool to support this work.

2012.08
Requirement Engineering
10
Roles: 2. effectively
 Work effectively with customers and users to manage
new and changed requirements so that the project stays
under control. Install a mechanism to control changes.
 It’s The next most serious problem .

 Critical requirements

have an impact on cost, schedule, or the development
effort if changed
 Non-critical requirements

such as a derived requirement that further defines the
system being built, but serves to clarify a higher-level
requirement and does not affect cost, schedule, or

Requirement Engineering
14
Roles: 2. effectively – actions
Roles: 3. Be alert to new technologies
 Be alert to new technologies that may help
 advising our customers concerning evolving technology

would be well advised to spend additional time and effort
learning about new technologies

 Decision Analysis Resolution (DAR) CMMi

 Keep the customer involved in these activities
2012.08
Requirement Engineering
15
Roles: 4. reuse
 2 meanings
 to take object X that was done by Y and use it directly
in another project
 to tailor a developed work product

2012.08
Requirement Engineering
16
Roles: 5. growth path
 helping customers to envision and evolve a series of
releases or versions of products
 is particularly appropriate in the situation in which
requirements are not well understood at the outset or

support of specific business objectives
2012.08
Requirement Engineering
19
Roles: 8. facilitate & mediate
 people skills (soft skills)
 negotiating skills, team building, communications,
relationships, and leading

 Two heads are better than one
 we get even better ideas and approaches! 2012.08
Requirement Engineering
20
Roles: 8. facilitate & mediate

2012.08
Requirement Engineering
21
Requirements
Verification
Requirements
Analysis
Requirements
Specification

Requirements Management
Requirements

Requirement Engineering
24
Skills of the RA
2012.08
Requirement Engineering
25