Page 64 - Software and Systems Requirements Engineering in Practice

36 S o f t w a r e & S y s t e m s R e q u i r e m e n t s E n g i n e e r i n g : I n P r a c t i c e

Create
Taxonomy

Create
Artifact
Create Artifact Model
Information Sheets

Define Process Levels Define
Processes

Define Process Create
Primary
Activity Rule Sets Workflows
for
Processes
Supporting
Activity
Included activity
FIGURE 2.17 RE activities for process creation

• Drawing of a filtered, domain, and project-specific artifact
model
• Population of a rule set for a workflow engine

In general, it is much better to have an “active” rather than
a “passive” process. An active process is one where rules are used to
prompt and inform staff about activities and provide templates for
documents that have already been tailored based on the project type.
A passive process is where documents (e.g., standards, procedures,
templates) are stored containing process information, and the project
staff has to download and read the relevant information.

2.9 Tips for Requirements Engineering Artifact Modeling
Some suggested practices for modeling requirements engineering
artifacts are summarized below:
• Define a Glossary of Terms for your project or product.
• Create an RE Taxonomy while keeping in mind what tools
will be used to maintain it and how it will be communicated
to the project team (e.g., publish to a project web site).
• Develop an RE Artifact Model specific to your project.