ITPEC FE Morning October 2021 Question 65

Creating technical requirements for the development standards that suit the programming language — non-functional requirements cover everything except the business functions themselves.

Requirements definition has two parts. Functional requirements say what the system must do for the business: its functions, the data flowing between them, and the interfaces to other systems. Non-functional requirements are everything else: quality (performance, reliability, security), operation and migration, and technical requirements for the development itself, such as the development method and the coding standards that fit the programming language to be used.

Answer (b)

Why not others:

• •(a) — the flow of data between the functions that make up the business is part of defining those functions, a functional requirement
• •(c) — deciding which scope is implemented as system functions is defining the functional requirements
• •(d) — the interface for exchanging information with other systems specifies what the system sends and receives, a functional requirement (external interface)

Key rule: If a requirement describes what the business needs the system to do, including its data and external interfaces, it is functional; quality, operation, standards and technical constraints are non-functional.

System Planning · AI-written, may contain errors