Result

[Work on own experiences/completions]



E-7 Glossary

Belong to:

Requirement-analysis-results

Is part of:

E-20 Requirement specification
E-136 System documentation
E-69 Architecture- and program description

Description:

A glossary defines all important technical terms of the application domain. When formulating the definitions, remember that the dictionary is designed only to prevent any possible misunderstandings, confusions and misinterpretations.

All terms are sorted alphabetically and include short descriptions (2 - 10 sentences) or refer to another term.

If different meanings exist for one term, mark each term with the necessary context, e.g. customer [sales] ..., customer [marketing].

If you use synonyms with different contexts note the relevant context to each term, e.g. customer [sales] see member.

The glossary is specific for the project and should contain all important functional terms. Abbreviations have to be described in the glossary, too.

Result contains:

Tools:



Possible status:

Producing or changing from:

A-7 Identify and Classify System Interfaces
A-71 Check and update the glossary
A-26 Specify a dialog
A-228 Requirement workshop
A-204 Set up a glossary
A-226 Requirement workshop
A-248 Modeling business use case sequences
A-240 Identify active business partners
A-290 Check and update the glossary
A-28 Identify reference models

Is needed for:

A-7 Identify and Classify System Interfaces
A-71 Check and update the glossary
A-229 Detail system use case
A-228 Requirement workshop
A-246 Develop a Sub System Model and a first draft of the business class model, if necessary
A-274 Define State Models for State Relevant Business Classes
A-290 Check and update the glossary
A-260 Develop a domain architecture model
A-28 Identify reference models

QS-Note:

Are important synonyms also defined in the dictionary?

Patter/Example:

: :



OEP - Object Engineering Process, v2.0, 06.11.2006 11:08:59, Copyright © 2003 by oose.de eG