A well-formed requirement is said to comply with which of the following acronyms?

A well-formed requirement is one that is clear, concise, and actionable. The SMART acronym provides a widely accepted framework for ensuring this quality. A requirement should be Specific (unambiguous), Measurable (verifiable/testable), Achievable (realistic and feasible), Relevant (aligned with business objectives), and Time-bound (having a defined timeframe, though in requirements this is often interpreted as Testable). Adhering to SMART criteria helps eliminate ambiguity and ensures that all stakeholders have a common understanding, which is critical for successful development and testing.

A. MOSCOW: This is a prioritization technique used to rank a set of requirements (Must have, Should have, Could have, Won't have), not to define the quality of a single requirement.

C. OSCAR: This is a framework for defining the terms of reference for an assignment or project (Objective, Scope, Constraints, Authority, Resources), not for structuring individual requirements.

D. MOST: This is a high-level strategic planning framework (Mission, Objectives, Strategies, Tactics) used to analyze an organization's purpose and goals, not for detailing specific system requirements.

1. Pohl

K. (2010). Requirements Engineering: Fundamentals

Principles

and Techniques. Springer Publishing. In Section 3.3.2

"Qualities of a single requirement

" the text details essential characteristics such as being "Unambiguous" (Specific) and "Verifiable" (Measurable)

which are core tenets of the SMART framework.

2. University of Toronto

Department of Computer Science. (2019). CSC443/2519: Software Requirements and Specification

Lecture 2: Requirements Basics. Course materials discuss the characteristics of good requirements

emphasizing clarity

testability

and feasibility

which are encapsulated by the SMART criteria.

3. Sommerville

I. (2011). Software Engineering (9th ed.). Pearson. Chapter 4

"Requirements Engineering

" Section 4.1.2

"Functional and Non-functional requirements

" discusses the importance of writing requirements that are complete

consistent

and unambiguous

with verifiability being a key attribute. These principles directly align with the SMART framework.