ITPEC FE Morning October 2019 Question 67

Identifying the quality, technical and operational requirements needed to implement the business requirements — that is non-functional requirements definition.

Requirements definition has two parts. Functional requirements say what the system must do for the business: its functions, data and interfaces. Non-functional requirements are everything else needed to realize them: quality (performance, reliability, security, usability), technical requirements (platform, development method and standards) and operational requirements (operation hours, monitoring, backup, migration).

Answer (d)

Why not others:

• •(a) — deciding which business functions stay manual because they are hard to systemize sets the scope of the system's functions, part of functional requirements
• •(b) — checking how well a new package fits the business requirements is fit-gap analysis when choosing a package
• •(c) — finding the functions the current system lacks is analysis of the current system to derive business requirements, which concerns functions, not quality

Key rule: If a requirement says what the system does for the business, it is functional; how well, on what technology and how it is operated are non-functional.

System Planning · AI-written, may contain errors