Business requirements are also called Non-Functional Requirements.

The statement is false. Business requirements and non-functional requirements are distinct and separate categories in the requirements classification schema. Business requirements are high-level statements of goals, objectives, and outcomes that describe why a change has been initiated. They articulate the value the organization wants to achieve.

In contrast, non-functional requirements (also known as quality of service requirements) describe the conditions under which a solution must remain effective or the qualities it must possess. They define how well the system should perform its functions, covering aspects like performance, security, usability, and reliability. They are a sub-category of solution requirements, which are derived from business requirements.

A. True: This is incorrect. Conflating business goals with solution quality attributes is a fundamental error in requirements engineering, as they represent different levels of abstraction and purpose.

1. International Institute of Business Analysis (IIBA). (2015). A Guide to the Business Analysis Body of Knowledge (BABOK Guide) (Version 3). IIBA. Section 2.3.2, "Requirements Classification Schema," explicitly defines Business Requirements and Non-Functional Requirements as separate categories.

2. Sommerville, I. (2011). Software Engineering (9th ed.). Pearson. Chapter 4, "Requirements Engineering," Section 4.1.2, "Non-functional requirements," distinguishes user and system requirements, with non-functional requirements being constraints on services or functions offered by the system, separate from high-level business objectives.

3. Wiegers, K., & Beatty, J. (2013). Software Requirements (3rd ed.). Microsoft Press. Chapter 6, "Documenting the Requirements," clearly separates business requirements from nonfunctional requirements, stating that business requirements describe the "business rationale for the project."