Following a recent, successful deployment, a business analyst (BA) has noticed that several of the requirements are candidates for reuse in multiple upcoming change initiatives. Which type of requirement is a potential candidate for re-use?
Following a recent, successful deployment, a business analyst (BA) has noticed that several of the requirements are candidates for reuse in multiple upcoming change initiatives. Which type of requirement is a potential candidate for re-use?
Business requirements are the most general type of requirements, focusing on the goals, objectives, and outcomes of an initiative rather than specific solutions or tools. Because they are not tied to specific departments or applications, they can be more easily reused across multiple initiatives. This generality makes them less subject to revision during changes, enhancing their reusability.
i guess ans is C. non-functional requirements Explanation-Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system across the different backlogs. (From Google)
Refers to page 85, Requirements that are represented in a general manner without ties to any tool or organizational structure tend to be more reusable.
Requirements at the highest level are best suited for re-use therefore the answer is B= Business Requirements
Babok pg 85. Requirements at high levels of abstraction may be written with limited reference to specific solutions. Requirements that are represented in a general manner, without direct ties to a particular tool or organizational structure, tend to be more reusable. These requirements are also less subject to revision during a change. As requirements are expressed in more detail, they become more tightly associated with a specific solution or solution option. Specific references to applications or departments limit the reuse of requirements and designs across an organization. Requirements that are intended for reuse reflect the current state of the organization. Stakeholders validate the proposed requirements for reuse before they can be accepted into a change.
Business requirements are at the highest level and not tied to any solution or department.
Babok pg 85. Requirements at high levels of abstraction may be written with limited reference to specific solutions. Requirements that are represented in a general manner, without direct ties to a particular tool or organizational structure, tend to be more reusable. These requirements are also less subject to revision during a change. As requirements are expressed in more detail, they become more tightly associated with a specific solution or solution option. Specific references to applications or departments limit the reuse of requirements and designs across an organization. Requirements that are intended for reuse reflect the current state of the organization. Stakeholders validate the proposed requirements for reuse before they can be accepted into a change.
I believe it is B - Business requirements: statements of goals, objectives, and outcomes that describe why a change has been initiated. They can apply to the whole of an enterprise, a business area, or a specific initiative. They are most general of all other types, doesn't describe the solution or current stakeholders needs.
C is easy to reuse
Also BABOK Page 303,44,16 ans-non-functional
Ans is Business Requirement
Reference???
B. Business requirements Business requirements, when clearly named, defined, and stored in a manner that makes them easily retrievable, can be reused within the current initiative, within similar initiatives, within similar departments, and throughout the entire organization, as stated in BABOK. Requirements at higher levels of abstraction, such as business requirements, tend to be more reusable compared to those tied to specific solutions or organizational structures. Therefore, business requirements are potential candidates for reuse in multiple upcoming change initiatives. Pg 85
pls check babok v3 page 44 and page 16