Page 52 - Software and Systems Requirements Engineering in Practice

g
i
E
n
n
r
i
e
e

r
e
u
i
m
t
s
e
n
n
o
d

M
e
n
g
l
i
t
A
r
g

t
a
c
i
f
q
p
a
h
r
e
t
:
R
e

C C h a p t e r 2 : R e q u i r e m e n t s E n g i n e e r i n g A r t i f a c t M o d e l i n g 25 25
2
• Categorize by grouping and create a draft taxonomy. For
example, network performance requirements, UI performance
(response time), query response times, etc., might all be
grouped under Performance Requirements.
• Make sure that complete, agreed-upon definitions are
available for every term that will be in the requirements
taxonomy, including parent terms.
• Create a draft taxonomy and circulate to stakeholders for
comments.
• Revise and publish (usually to the web).
• Provide feedback and maintenance mechanisms (including
processes and identified roles) for keeping the taxonomy up-
to-date.
Other Types of Taxonomies Useful in RE
In addition to a “generic” RE taxonomy covering the classification of
requirements, there are other artifact taxonomies that may be useful.
For example, a document classification taxonomy can be used to identify
common templates, assist with planning processes such as version
control and baselining, and aid in the training of staff. The leaves of
such a document classification taxonomy should all be real documents
that are created by the organization or project staff. A partial
requirements document classification taxonomy can be seen in
Figure 2.4.
Requirements
Document
Requirements
Requirement Process Engineering
Specification Specification Management
Plan
Market Product Customer System
Requirement Feature Requirement Requirement
Specification Specification Specification Specification
Product
Marketing
Literature
Feature Model
FIGURE 2.4 Sample partial taxonomy of requirement documents