10 Most non-functional requirements (NFRs) relate to the system as a whole. They include constraints on: Performance, Reliability, Security, Maintainability, Usability, Standards, etc.
12 They are often more critical than individual functional requirements.
Must be built into the software product, as
failure to meet a NFRs system requirement may make the whole system unusable.
13 For example, if an aircraft system does not meet reliability requirements, it will not be certified as ‘safe’.
If a real-time control system fails to meet its
performance requirements, the control functions will not operate correctly e.g. ATM in banking system
14 NFRs come up/depends through: User needs, budget & interoperability, Organizational policies(s/w developing), External factors such as safety regulations, privacy legislation, etc.
15 Non-functional requirements should be documented in SRS, so that they can be used to build the architecture of the software product
16 •Architecture: where non-functional decisions are cast, and functional requirements are partitioned •Design: where functional requirements are accomplished
