Chapter 4 requirements en2014 requirements

  • No School
  • AA 1
  • 12

This preview shows page 3 - 5 out of 12 pages.

Chapter 4 Requirements Engineering 16 30/10/2014 Requirements completeness and consistency In principle, requirements should be both complete and consistent. Complete They should include descriptions of all facilities required. Consistent There should be no conflicts or contradictions in the descriptions of the system facilities. In practice, because of system and environmental complexity, it is impossible to produce a complete and consistent requirements document. Chapter 4 Requirements Engineering 17 30/10/2014 Non-functional requirements These define system properties and constraints e.g. reliability, response time and storage requirements. Constraints are I/O device capability, system representations, etc. Process requirements may also be specified mandating a particular IDE, programming language or development method. Non-functional requirements may be more critical than functional requirements. If these are not met, the system may be useless. Chapter 4 Requirements Engineering 18 30/10/2014
Image of page 3

Subscribe to view the full document.