Mastering Non-Functional Requirements

Checklist

The checklist for capture of requirements is as follows:

• The application offers a mechanism to facilitate extension of core capabilities by the vendor or end organisation
• The system responsible for persistence is governed by an entity model. The entity models are extensible to allow the modification of entity types or the creation of new entity types to match business needs.
• The application accountable for data processing is governed by a engine or model. The engine is extensible to facilitate refinement of existing processing rules or creation of new rules to match business needs.
• The information processed, derived, stored, and leverage is documented in an model and also includes the relationships between information types.