Page 56 - Software and Systems Requirements Engineering in Practice

e
n
m
r
e
E
n

t
s
i

2
d
r
e
q
u
e
:
R
f
a
i
r
t
M
o

c
t
A
e
e
n
g
i
g

n
r
i
e
h
a
p
g
n
i
l
t
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 29 29
FIGURE 2.8 Contains
Starting fragment Business Plan Business Goal
*
• Test cases
• System requirements
• Customer requirements
• Product design
• …
For creating the REAM, we first want to see how the products are
related. We expect, for example, that a business plan will contain
business goals (Figure 2.8). We can then model the artifacts and the
relationships between them. We know that the business goals will be
used as inputs to define the products. The products will be described
in a marketing brochure (Figure 2.9).
Various techniques are used to define the features that the
product needs to have in the marketplace to meet the business goals.
At this point, product features have to be tied to business goals. Since
the model is a simple construct, any drawing tool can be used to
create one. UML modeling tools work quite well, as do general-
purpose drawing tools such as Visio. However, it may be necessary
to trace between different artifacts. Furthermore, it is important to
have clear definitions of all the artifacts. This, in turn, may require
stakeholder involvement. Also, if there is a taxonomy, all the leaves
in the taxonomy should be in the artifact model. Since artifact models
can be quite comprehensive, we may start with a subset. Let’s say,
for example, that, given the artifacts described, we wind up with an
initial draft REAM as shown in Figure 2.10.
There are some things missing from this draft REAM that would
have to be added, including metrics, artifact reviews, project plans,
standards and procedures, and so forth. Here are some other important
things to consider that tend to be neglected until well into the project:
• Internal training standards and procedures
• Maintenance requirements (e.g., how will the product be
maintained, what are the artifacts that will be needed to
properly maintain the product after deployment?)
• Product documentation, including training manuals, marketing
literature, internal maintenance manuals, and so on
• Holistic tool support that works across organizational
boundaries (e.g., from the help desk to design)
FIGURE 2.9 Marketing Brochure Describes Product
Next model
fragment 1..*