1. A business analysis team has collected the main business requirements from the major stakeholders of a project. The team wants to be sure that each stakeholder has a clear understanding of the areas of analysis that will be in scope. Which model should the team employ to ensure the most effective representation of analysis boundary?

A) C. State diagram
B) A. Context diagram
C) D. Entity relationship diagram
D) B. Data flow diagram



2. How should a business analyst determine whether a solution satisfies business requirements?

A) B. By evaluating the solution against the project charter
B) A. By conducting a brainstorming session with end users
C) C. By reviewing the results of user acceptance testing
D) D. By reviewing the traceability matrix



3. A company is in the final phases of implementing a project for a client. Which tool or technique could the business analyst use to iteratively validate the solution?

A) A. Expected vs. actual results
B) D. Quality variance
C) B. Expected vs. actual costs
D) C. Schedule variance



4. Which technique or tool is used to obtain acceptance of the delivered product?

A) A. Inspection
B) C. Contextual inquiry
C) B. Facilitated workshops
D) D. Expert judgment



5. A company has just finished the development work for a new software sales tracking application and is in the process of validating that the new application meets all of the acceptance criteria defined for the business requirements. During the validation process, a stakeholder discovers that the application does not provide the selection criteria needed to produce the sales volume reporting required by the companyâ??s financial department. The business analyst for the project determines that the selection criteria needed was not specified in the system requirements or design specifications. Which of the following tools and/or techniques might be used by the business analyst to determine how the selection criteria requirement was missed?

A) B. Scope modeling, Ishikawa diagram, and/or the Five Whys
B) A. Root cause analysis, fishbone diagram, and/or the Five Whys
C) C. Root cause analysis, problem tracking, and/or benchmarking
D) D. Cause and effect diagram, brainstorming, and/or the Five Whys