In all models of the software life-cycle, the requirements specification phase, i.e., the phase when the user requirements are elicited and expressed formally, plays a critical role. Two key properties of specifications are completeness (i.e., their ability to capture all the user requirements) and minimality (i.e., their ability to capture nothing but the user requirements). The paper describes a system that helps specifiers check these properties on specifications that are written in some predefined relational form.
All Science Journal Classification (ASJC) codes
- Information Systems
- Computer Science Applications
- requirements specification
- specification language
- verification and validation