ITPEC FE Morning April 2018 Question 66
ITPEC FE Morning April 2018 — Question 66 of 80
Non-functional requirements definition — identifying technical constraints, standards, and quality attributes of the system
Non-functional requirements describe how a system should perform, not what it should do. They cover performance, reliability, security, development standards, and technology constraints.
Defining technical requirements for development criteria and standards according to the programming language (option c) is a non-functional requirement — it specifies how the system will be built, not what business functions it provides.
Why not others:
- a) Clarifying data flow between business functions → functional requirement (defines what data moves where)
- b) Clarifying interfaces for exchanging info with other systems → functional / external design (defines what is exchanged)
- d) Defining the scope of system functions → functional requirement (defines what features to build)
Key rule: Functional = what the system does; Non-functional = how it does it (performance, standards, reliability, technology choices).
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.