Page 205 - Software and Systems Requirements Engineering in Practice
P. 205
5
e
r
a
l
:
u
t
e
t
i
r
a
p
n
h
t
e
b
u
e
q
R
i
y
i
t
t
r
A
t
u
e
s
C C h a p t e r 5 : Q Q u a l i t y A t t r i b u t e R e q u i r e m e n t s 171 171
m
private list of attributes that you think will become important
later.
• Use quality attribute scenarios not just in workshops, but
whenever you are capturing stakeholder concerns.
• When conducting QAWs, ask stakeholders to capture their
QASs on their laptops and e-mail them to the workshop
facilitator.
• During a QAW, stakeholders should be encouraged to seek
clarifications on QASs, but any other issues for discussion
should be captured and e-mailed to the facilitator. Avoid side
discussions on QASs during a QAW.
• Manage factors, issues, and strategies using a general-purpose
requirements management tool, if your organization is
already using one.
• Address the top 5–10 concerns when defining the architecture
principles.
5.10 Summary
Following an integrated approach to requirements engineering and
architecture design provides the following major benefits:
1. Joint awareness and a shared understanding, among all
stakeholders, of the system context and its problem domain,
together with an overarching vision of the system to be
designed, helping to properly frame decisions
2. Clear traceability of requirements specification and
architecture design to business goals ensuring a higher
probability of delivering the “right” system
3. A shared project context that avoids costly duplication of
work across the requirements engineering and architecture
design disciplines
4. A clear focus on business goals making it easier to
communicate, to all concerned stakeholders, the vision of the
system being developed, its requirements specification, and
its architecture design
5. 11 Discussion Questions
1. Which requirements engineering artifacts are likely to be
used by both requirements engineers and software system
architects?
2. What kinds of practices can be used to elicit architecturally
significant requirements from stakeholders?