Full Access IIBA CCBA Tutorials

The domain subject matter expert will provide the verification that the approach to the process design is feasible for the staff who perform the end of month accounting procedures. According to the BABOK Guide, a domain subject matter expert is “a stakeholder who has specialized knowledge of a business domain or area of expertise that is relevant to the change or the solution” 4. The domain subject matter expert can provide the business analyst (BA) with the necessary information, feedback, and validation regarding the current and desired state of the accounting process and the impact of the new solution on the staff. The implementation subject matter expert, the operational support, and the project sponsor are also important stakeholders, but they do not have the same level of expertise or authority as the domain subject matter expert in this case. References: 4: BABOK Guide, Version 3, Section 2.4.2 Domain Subject Matter Expert

According to the BABOK® Guide, one of the tasks of the business analyst (BA) during requirements lifecycle management is to validate requirements. This involves ensuring that the requirements and designs support the delivery of value to stakeholders, fulfill the goal or objectives, and meet the quality standards. One of the techniques that can be used for this task is assumption and constraint analysis, which is the process of identifying, documenting, validating, and managing the assumptions and constraints that affect the requirements and designs. Incorrect assumptions are statements that are believed to be true without sufficient evidence or validation. They can create a situation where the design cannot be validated to support the requirements, as they may introduce errors, risks, or inconsistencies in the solution. References: BABOK® Guide, Version 3, Chapter 7, Section 7.2; Business Analysis Expert Certification, CCBA® | IIBA®, Section “What Should I know to be CCBA Certified?”.

According to the BABOK Guide, elicitation scope is the set of information that needs to be discovered or confirmed through elicitation activities3. Understanding the elicitation scope can assist the BA with the elicitation activity by determining when elicitation is complete4. This means that the BA can stop eliciting information when he or she has obtained enough information to meet the elicitation scope. This can help avoid over-elicitation or under-elicitation of information. References: BABOK Guide, CCBA Practice Test

According to the BABOK® Guide, non-functional requirements analysis is a technique that is used to examine and group requirements that describe the quality attributes of a solution, such as efficiency, capacity, security, and scalability. Non-functional requirements analysis helps to ensure that the solution meets the expected standards of performance, reliability, usability, and maintainability. Non-functional requirements analysis also helps to identify trade-offs and dependencies among different quality attributes. References: BABOK® Guide, Version 3, Chapter 10, Section 10.32; Business Analysis Expert Certification, CCBA® | IIBA®, Section “What Should I know to be CCBA Certified?”