In requirements, what does 'objective' describe?

In requirements, what does 'objective' describe?

• A. How the system should be
• B. The environment constraints
• C. What the system should do
• D. The user requirements

Answer: (C)

An objective describes what the system should do—the functions, capabilities, and outcomes it is intended to deliver. It states the end goals for the system in terms of actions it performs and services it provides, not how those things are implemented. This is different from environment constraints, which specify the conditions or limits under which the system must operate (like platforms or regulatory rules), and from user requirements, which capture what stakeholders want or need from the system. For example, an objective might be that the system can process payments securely and generate a receipt, focusing on the actions the system must take.

An objective describes what the system should do—the functions, capabilities, and outcomes it is intended to deliver. It states the end goals for the system in terms of actions it performs and services it provides, not how those things are implemented.

This is different from environment constraints, which specify the conditions or limits under which the system must operate (like platforms or regulatory rules), and from user requirements, which capture what stakeholders want or need from the system. For example, an objective might be that the system can process payments securely and generate a receipt, focusing on the actions the system must take.