CCBA Leak Questions

 A roles and permissions matrix is a technique that defines the roles and responsibilities of the stakeholders involved in a business process, and the level of authority and access they have to the information and resources required to perform their tasks. A roles and permissions matrix can help the BA to model the people involved in the contracting process, and identify any gaps, overlaps, or conflicts in their roles and permissions. A roles and permissions matrix can also help to improve the efficiency, effectiveness, and security of the process, and ensure compliance with the policies and regulations. A roles and permissions matrix is part of the Requirements Analysis and Design Definition Knowledge Area in the BABOK® Guide. References: 1, 2 (pages 31-32), 3 (pages 13-14)

The communication method was inappropriate because the BA sent a 600-page document without any summary or explanation to all stakeholders, which is likely to overwhelm and confuse them. The BA should have chosen a more suitable format and level of detail to communicate the status of the requirements management process, such as a dashboard or a report. The business rules, the distribution, and the models were not the main issues in this situation. References: BABOK Guide v3, page 50; CCBA Mock Test, question 17

The requirement classification schema that this requirement belongs to is nonfunctional requirements. Nonfunctional requirements are statements of conditions or restrictions on a solution or its components that affect its quality, performance, usability, reliability, security, etc. Nonfunctional requirements specify how well a solution should perform or behave.

The other options are incorrect because:

• Option B is incorrect because stakeholder requirements are not a requirement classification schema, but a requirement type. Stakeholder requirements are statements of needs, expectations, preferences, or problems of stakeholders or an organization.
• Option C is incorrect because transitional requirements are not a requirement classification schema, but a requirement type. Transitional requirements are statements of capabilities or conditions that enable a solution to transition from its current state to its desired future state.
• Option D is incorrect because functional requirements are not a requirement classification schema, but a requirement type. Functional requirements are statements of features, functions, or behaviors of a solution or its components that enable it to provide value to stakeholders.

References:

• BABOK Guide v3, section 6.1: Specify and Model Requirements
• CCBA Exam Questions, question 35

Requirement attributes are additional pieces of information that provide more details about each requirement1. They can include information such as priority, source, status, owner, risk, complexity, etc1. When the product roadmap is modified due to changing market conditions, the BA should modify the requirement attribute values to reflect the new situation and communicate the impact to the stakeholders2. For example, the priority of some requirements may change, the status of some requirements may be deferred or cancelled, the risk of some requirements may increase or decrease, etc2. Modifying the requirement attribute values helps the BA to manage the requirements effectively and ensure alignment with the business objectives and stakeholder needs3.

Requirement description is the statement that captures what the requirement is about and what it intends to achieve1. It should be clear, concise, consistent, and testable1. Requirement description does not need to be modified unless the requirement itself changes or is clarified4.

Requirement performance measures are the criteria that are used to evaluate the degree to which the requirement meets the stakeholder expectations and the business value1. They can include metrics such as quality, timeliness, cost, customer satisfaction, etc1. Requirement performance measures do not need to be modified unless the stakeholder expectations or the business value change5.

Scope model is a graphical representation of the boundaries and relationships of the solution and its components1. It can include diagrams such as context diagram, scope diagram, feature model, use case diagram, etc1. Scope model does not need to be modified unless the scope of the solution changes or is refined6. References: 1(https://www.iiba.org/business-analysis-certifications/ccba/),  2(https://www.iiba.org/business-analysis-certifications/ccba/ccba/),  3(https://www.techno-pm.com/blogs/project-management-concepts/ccba),  4(https://www.simplilearn.com/project-management/ccba-certification-training),  5(https://www.oreilly.com/library/view/ccba-and-cbap/9781838825263/),  6(https://www.apm.org.uk/blog/how-to-engage-stakeholders-who-keep-changing-project-requirements/)