Exam CBAP All QuestionsBrowse all questions from this exam
Question 327

A business unit of a transnational manufacturer wants to implement a robust process for addressing integrity-critical equipment deterioration incidents. Timely and complete resolution of such incidents is vital for the business unit's continuous safe and profitable operation. Treating each incident involves many employees from different departments extensively collaborating and exchanging information. That information is spread across multiple systems having their access limited to particular user groups. With the current manual process, some incidents get forgotten and remain unresolved for years.

The project's Sponsor is an Equipment Integrity and Reliability Advisor, who moved into this position from another business unit. That business unit implemented a proprietary application to integrate the information and to assist in tracking and managing the incidents. Having a positive experience with the application, the

Sponsor is suggesting to customize it and reuse in the new business unit.

The business unit's Enterprise Architect (EA), who is responsible for assessing solution options and presenting them to executive decision makers, has a few concerns with adopting the existing application. The application uses point-to-point interfaces with other data sources whereas the business unit's target architecture relies on a data warehouse-based integration. Moreover, the two business units use different legacy systems, as well as different front-end implementation technologies. Additionally, the existing application is monolingual, while the business unit needs user interfaces and some data to be presented in two languages. With all of this, it may be easier to build a new application from scratch than to customize the existing one. To understand which option is better, the EA asks a business analyst (BA) to define business requirements.

With the team ready to consider design options, they are reviewing the following requirement: "Appropriate stakeholders shall be timely and reliably notified on incident-related events."

What quality criteria does this requirement fail to satisfy?

    Correct Answer: B

    The requirement 'Appropriate stakeholders shall be timely and reliably notified on incident-related events' lacks completeness because it does not specify which stakeholders need to be informed, what constitutes timely notification, or what is meant by reliable notification. For a requirement to be complete, it needs to be detailed enough to guide further work and contain sufficient information to be actionable. This requirement is missing critical details that would enable those responsible to accurately implement the notification process.

Discussion
rhsdealOption: B

Answer should be B - COMPLETE Reasoning - Question states: Reliably notified. How/by what means? Appropriate stakeholders. Who? Timely? What interval BABOK V-3 7.2.4.1 Characteristics of Requirements and Designs Quality • Complete: enough to guide further work and at the appropriate level of detail for work to continue. The level of completeness required differs based on perspective or methodology, as well as the point in the life cycle where the requirement is being examined or represented. • Consistent: aligned with the identified needs of the stakeholders and not conflicting with other requirements.

OlivierPaudex

I think you should be right - COMPLETE is the best criteria. When sending notification, it should mention the from, to, subject, frequency, ...which is not the case in this requirement

Jules_Cmrfrd

The question is about quality criterea which are Defined, Necessary, Correct, Unambiguous, Consistent. The only one here is the last one. So the answer is correct

siliconvalleykamOption: A

quality criteria are Defined Necessary Correct Unambigous Consistent. Hence Consistent

rupakarthik

the question is about quality criteria for requirements(Pg-143) not requirement relationships

TochToch

Read the question again. The requirement is meant to address the challenge faced with manual process where incidents get forgotten and remain unresolved for years. It is already consistent with the issue to be addressed. Therefore, the answer should be B (Complete) as the requirement lacks completeness.

Yoli22_Option: B

The key thing I noticed is the BA is reviewing this requirement with stakeholders- That will mean its 7.2 Verify Requirements Task - to ensure that requirementse and designs specifications and models meet quality standardsand are usable for thed purpose they serve. Characteristics of Requirements and Design Quality Element 7.2.4 Acceptable quality requirements exhibit - Atomic, Complete, Consistent, Concise, Feasible, Unambiguous, Testable, Prioritized, Understandable. We have 3 options from this category so the word Quality Criteria is confused with 7.4 in 7.4.4.4Verify Requirement Relationships quality criteria to satisfy requirement relationships - Defined, Necessary, Correct, Unambiguous and Consistent. Hence I think the relationship is consistent. However, this requirement is not Atomic/Complete Atomic - self-contained and capable of being understood independently of other requirements or design Complete - see @rhsdeal comment above. Hence I will go with B - Complete as the best quality characteristics . Although I believe it neither Atomic or Complete.

Dillon91Option: C

Changed my mind... C: • Complete: enough to guide further work and at the appropriate level of detail for work to continue. The level of completeness required differs based on perspective or methodology, as well as the point in the life cycle where the requirement is being examined or represented

Dillon91Option: C

C: In the design phase so: Atomic: self-contained and capable of being understood independently of other requirements or designs.

786NB786Option: C

It is C: Atomic as per 7.2.4 - • Atomic: self-contained and capable of being understood independently of other requirements or designs. Timely and Reliably are not self contained.

Farooq_95Option: B

Complete is correct answer. As per BABOK v3 7.2.4.1 a requirement is complete if it is detailed enough to guide further work and at the appropriate level of detail for work to continue. The requirement says "Appropriate stakeholders shall be timely and reliably notified on incident-related events". The requirement lacks the following details: * Who are the specific stakeholders that need to be informed? What is the criteria to identify the appropriate stakeholders? * What is the definition of timeliness? At what intervals the stakeholders need to be notified? * What is the definition of reliability? What content, level of details and structure of the information concludes that the information is reliable? As the requirement fails to answer above question, hence it is not considered enough to guide further work and implemented until the above information is known. Hence, the requirement fails to satisfy complete.

RabbitsfootOption: C

The most appropriate quality criteria for the given requirement would be C. Atomic. This is because the requirement "Appropriate stakeholders shall be timely and reliably notified on incident-related events" encompasses multiple aspects (stakeholder identification, timeliness, reliability, event notification), which could be broken down into more granular, individual requirements for each aspect to make them atomic or indivisible.

Rabbitsfoot

BABOK V3 pg 143 RADD

OlivierPaudexOption: A

Answer A is correct : Consistent "Some incident get forgotten and remain unresolved for years" is NOT consistent (aligned) with "Appropriate stakeholders shall be timely and reliably notified on incident-related events" Requirement means 100% of incident shall be notified Description means that NOT all incidents are notified This is a clearly a non-consistent requirement.

TochToch

Read the question again. The requirement is meant to address the challenge faced with manual process where incidents get forgotten and remain unresolved for years. It is consistent with the issue to be addressed.