ITPEC FE Morning October 2019 Question 67
ITPEC FE Morning October 2019 — Question 67 of 80
Non-Functional Requirements Definition — identify quality, technical, and operational constraints for a system.
Non-functional requirements (NFRs) describe how a system should perform, not what it should do. They cover areas such as performance, reliability, security, scalability, and usability.
The NFR definition process clearly identifies the quality requirements, technical requirements, and operational requirements necessary to implement business requirements.
Why not others:
- (a) Describes identifying business functions that remain manual — this is about scoping functional requirements, not non-functional ones.
- (b) Describes checking conformity of a new software package to business needs — this is package evaluation, not NFR definition.
- (c) Describes identifying missing functions in the current system — this is gap analysis for functional requirements.
Key rule: Functional = what the system does; non-functional = how well it does it (speed, uptime, security).
AI-generated — may contain errors
The original exam layout is preserved in the image so diagrams, formulas, tables, and code remain accurate.
This question comes from an official ITPEC past paper. ITPEC Practice is an independent study tool and is not affiliated with ITPEC. See the official FE past-paper collection or Report an issue.