Page 65 - Software and Systems Requirements Engineering in Practice

r
e
t
n
t
s
M
o
d

E
p
e
u
q
e
e
r
i
t

m
:
2

e
g

A
n
e
r
i
r
a
c
C C h a p t e r 2 : R 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 37 37
g
t
i
f
g
i
n
l
a
n
e
n
h
i
• Communicate project roles to all team members and the
artifacts they are responsible for as defined in the RE Artifact
Model.
• Use templates to define RE artifacts.
• For scaling projects, provide tailoring information in the RE
Artifact Model; e.g., a specific artifact may be mandatory,
optional, or not used, depending on the project size.
• Tailor the RE Artifact Model for a specific project from any
corporate-level models, if they exist.
• Create a system life cycle process by adding needed timing to
the defined artifacts.
2.10 Summary
We have seen in this chapter how taxonomies are used to define and
classify work products that are referenced, created, or modified
during the requirements engineering process. A taxonomy is typically
the starting point for the creation of a project glossary and a
Requirements Engineering Artifact Model. An artifact model for an
organization is essential for the definition of requirements engineering
processes; however, the same techniques can be extended to defining
the entire life cycle model. Organizations that have different types of
projects need to be flexible in their approach to process definition, so
that small projects will not be burdened with excessive bureaucracy
and paperwork, while larger projects will have the infrastructure and
tools necessary to succeed.
2.11 Discussion Questions
1. Where are taxonomies used outside of requirements
engineering?
2. What are the differences between a taxonomy and a glossary?
3. What are some project roles, and which artifacts do they use?
4. Must each project create its own artifact model? Are there
tailoring techniques to help select artifacts for different
projects?
References
Berenbach, B., “The Evaluation of Large, Complex UML Analysis and Design
Models,” Proceedings of the 26th International Conference on Software Engineering,
ICSE 2004, Edinburgh.
Firesmith, D., “A Taxonomy of Security Related Requirements,” SEI, International
Workshop on High Assurance Systems (RHAS’05 – Paris), August 29–30, 2005,
www.sei.cmu.edu/programs/acquisition-support/publications/taxonomy
.pdf.