You are the business analyst for your organization. Management has asked you to define and document the requirements of an endeavor so that the requirements may be reused again in the organization. Why would an organization want to re-use requirements?

Organizations maintain and reuse requirements to improve efficiency and consistency across multiple initiatives. This is particularly valuable for requirements that apply repeatedly, such as regulatory constraints, compliance rules, security policies, or core operational business processes. By treating these requirements as reusable assets, an organization saves time, reduces analysis effort, minimizes errors, and ensures that solutions consistently adhere to established standards and obligations. This practice is a key component of mature requirements management and governance.

A. Selling requirements is not a standard business practice or the primary motivation for creating a reusable requirements repository.
B. While having documented requirements helps if a solution fails, the primary purpose of reusability is proactive efficiency, not reactive disaster recovery.
D. This statement incorrectly defines re-using requirements; tracing requirements to deliverables is a separate, albeit related, activity called traceability.

- International Institute of Business Analysis. (2015). A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3. Toronto

Ontario

Canada: IIBA. Section 5.1.4.5

"Maintain Requirements for Re-use

" explicitly states this is useful for solutions implemented on an ongoing basis or for processes used repeatedly.

- Wiegers

K.

& Beatty

J. (2013). Software Requirements

3rd Edition. Microsoft Press. Chapter 6 discusses the benefits of reusing requirements to leverage existing intellectual property and reduce development effort. (Note: While a commercial book

its principles are foundational and align with IIBA standards).