Ben is the business analyst for his organization. Ben is currently working on a solution to improve a laser printer. He has taken the laser printer apart, identified each component, and documented each component's purpose. What type of requirements organization is Ben doing in this scenario?
Ben is practicing functional decomposition by taking the laser printer apart, identifying each component, and documenting each component's purpose. Functional decomposition involves breaking down a system into its smaller components to understand its structure and functionality in detail. Each identified component may have its own set of requirements, contributing to the overall goal of improving the printer.
You are the business analyst for your organization and you're working with Fran on business analysis processes. Fran is a stakeholder who wants to ensure that your business analysis approach and activities are compatible with the project activities. Of the following, what type of business analysis stakeholder is Fran?
You are a business analyst for your organization and you're working with Mary. Mary wants to know what you need to complete the process of planning the business analysis approach if you're already the business analyst for your organization. Which of the following statements is true regarding the plan business analysis approach?
The plan business analysis approach is required to select an approach that will perform business analysis. It outlines the processes and tasks necessary to conduct business analysis in alignment with the organization's goals and constraints. This includes defining the scope, determining the methodologies and stakeholders, and planning how to gather and manage requirements effectively. The purpose of this approach is not limited to budgeting or time allocation, but to ensure a structured and efficient analysis process.
You are the business analyst for a large software development project. There are several issues that must be resolved by certain dates or the problem will prevent the project from advancing. What technique can you use to track problems with the requirements?
The appropriate technique to track problems with the requirements in a software development project is issue tracking. Issue tracking allows the business analyst to systematically monitor, manage, and resolve any issues or problems that arise during the project. This method ensures that issues are documented, prioritized, and addressed in a timely manner to prevent them from hindering project progress. Other methods such as baselining and RTM (Requirements Traceability Matrix) serve different purposes and are not specifically focused on tracking and managing problems.
Which one of the following statements is most true about changing requirements in a change-driven approach to business analysis and requirements management?
Change-driven approaches focus on continuous improvement and iterative processes in which requirements are continuously re-evaluated and updated as needed. These approaches are flexible and dynamic, allowing for adjustments without the strict oversight of a formal change control process. Therefore, the most accurate statement is that change-driven approaches do not use a formal change control process.