Page 63 - Software and Systems Requirements Engineering in Practice

n
g
E
s

e
r
e
i
n
t
u
i
q
R
e
e
n
m
r
e
o
d
M
t

n
g
i
e
l
c

A
g
i
n
f
a
i
r
t
:
t
e
r
p
a
h

2
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 35 35
Project Artifact Prototyping Small Medium Large Small Plan Medium Large Government
Agile Agile Agile Driven Plan Plan Contract
Driven Driven
Stakeholder Requests in X X X X X X X X
Database
Requirements in Database X X X X X
Customer Requirement X X X X
Specification
Decision Gates X X X X
Business Goals X X X X X X
Feature Model X X X X
FIGURE 2.15 Sample table for tailoring RE processes
2.8 Creating a System Life Cycle Process
As was mentioned earlier, both a taxonomy and an artifact model are
useful in the creation of system life cycle processes. By adding
attributes to the artifacts that specify when they are needed (based on
the type and size of the project), a query will result in the production
of a list of all the appropriate artifacts. Project management can then
use this list for planning, including the definition of decision and
review points, work products needed, and quality artifacts needed to
measure project quality and efficiency. An example process creation
approach is illustrated in Figure 2.17.
Process creation to some extent can be automated, depending on
how much of an investment the organization is willing to make in
tooling. Automation of process creation can include
• Generation of selected project templates
• Assembly of standards and procedures from a library
Requirements Contains
Company Requirement
Specification 1 1..N
refine
System System
Requirements Contains Requirement
Organization Specification
Customer Contains Customer
Requirements Requirement
Specification 1 1..N
refine
Project
Automatically
Customer Contains RE generates Customer
Requirement 1..N 1 Database 1 1 Requirements
Specification
FIGURE 2.16 Organizational tailoring of an artifact model