Result

[Work on own experiences/completions]



E-75 Catalogue of outputs

Belong to:

Requirement-analysis-results

Is part of:

E-20 Requirement specification
E-78 Preliminary study
E-83 Software development schedule
E-69 Architecture- and program description

Description:

The catalogue is structured like that. Describe for each output (letter, report, etc.):

  • name of the output (e.g. "monthly invoice")
  • short description (1-20 lines of text)
  • receiver of the output (e.g. "customer")
  • frequency of activation, distribution by time of day and quantity (e.g. "regularly at the beginning of the new month")
  • some notes about the aim
  • examples, pattern
  • change frequency
  • notes about historization, versionization, etc.
  • list of contact partners
  • who is responsible for the output
  • who uses the generated output
  • output medium (paper, posting, fax, e-mail, chip card, etc.)

Result contains:

Tools:



Possible status:

Producing or changing from:

A-226 Requirement workshop
A-231 Identify and describe output (artifact)

Is needed for:

A-15 Requirement specification
A-228 Requirement workshop
A-231 Identify and describe output (artifact)
A-70 Develop and Test Reports and Evaluations

QS-Note:

Patter/Example:

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