Result

[Work on own experiences/completions]



E-71 Catalogue of non-functional requirements

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:

Collect all requirements, which couldn't be described by use cases and which do not concern external interfaces. The following list includes some examples for possible non-functional requirements:

  • general requirements on quality
  • usability, ergonomics
  • robustness
  • system security, requirements on data security
  • system availability
  • response mode
  • hardware requirements
  • requirements on the operation system and software
If there are non-functional requirements, which aren't necessary for the system to be created, mark them with "excluded" and describe them in the exclusion list.

Result contains:

Tools:



Possible status:

  • in process
  • okay

  • Producing or changing from:

    A-226 Requirement workshop
    A-235 Identify non-functional requirements
    A-275 Describe business requirements and rules

    Is needed for:

    A-235 Identify non-functional requirements
    A-15 Requirement specification
    A-228 Requirement workshop

    QS-Note:

    Patter/Example:

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