A customer has provided a business analyst (BA) with many business requirements and some have inter-dependencies with other requirements. To ensure the requirements are delivered according to customer expectations, which requirements attribute should the BA consider including in the project requirements document?
To ensure the requirements are delivered according to customer expectations, the business analyst should consider including the 'Priority' attribute in the project requirements document. Priority indicates the relative importance of requirements and can refer to the sequence in which they need to be implemented. This allows for the effective management of interdependencies and ensures that the most critical requirements are addressed first, aligning with customer expectations and project goals.
I think it's A 3.4.4.6 • Priority: indicates relative importance of requirements. Priority can refer to the relative value of a requirement or to the sequence in which it will be implemented.
Priority: indicates relative importance of requirements. Priority can refer to the relative value of a requirement or to the sequence in which it will be implemented.Page-45
Question says inter-dependant, hence its Priority
True, but Unique Identifier would visually reflect those dependencies better... on the other hand, if we are sticking to the BABOK definitions, it should be Absolute Reference, so I guess Priority it is.
Deatils on Pg 45
I think Priority is the answer. Only Priority and Unique Identifier (absolute reference) are the two attributes listed as options, mentioned in the BAPM - Info Mgmt KA
Requirements Attribute, BABOK V3 page 45 • Priority: indicates relative importance of requirements. Priority can refer to the relative value of a requirement or to the sequence in which it will be implemented.
A- Prioritization is the act of ranking requirements to determine their relative importance to stakeholders. When a requirement is prioritized, it is given greater or lesser priority. Priority can refer to the relative value of a requirement, or to the sequence in which it will be implemented. Prioritization is an ongoing process, with priorities changing as the context changes. Inter-dependencies between requirements are identified and may be used as the basis for prioritization. Prioritization is a critical exercise that seeks to ensure the maximum value is achieved.
acceptance criteria: Criteria associated with requirements, products, or the delivery cycle that must be met in order to achieve stakeholder acceptance. I will go with D.
Acceptance Criteria is not a requirement attribute
I think you're all wrong, question clearly states: inter-dependencies with other requirements =constraints, = BA should consider constrants. given answer is correct
I will take D. Reason being that the question asked "To ensure the requirements are delivered according to customer expectations" so Acceptance Criteria should be included in the Document
Inter-dependencies between requirements are identified and may be used as the basis for prioritization. Prioritization is a critical exercise that seeks to ensure the maximum value is achieved.Page-87
Keywords: 'To ensure the requirements are delivered according to customer expectations'. I am going with 'Acceptance Criteria'. See pg 217 BABOK v3: Acceptance criteria are used to define the requirements, outcomes, or conditions that must be met in order for a solution to be considered acceptable to key stakeholders. Evaluation criteria are the measures used to assess a set of requirements in order to choose between multiple solutions.
I'm thinking it's A because Constraint isn't even a requirements attribute and Acceptance Criteria is only considered a Requirements Attribute from v2. Priority is the only one that relates to order of importance of completion. Frankly, I'm not getting caught up in a v2 question.