After a number of requirements elicitation workshops, the business analyst (BA) notices that two business stakeholders did not speak up during any of the discussions. What should the BA do in the next workshop?
If an organization wants to re-use requirements, where should the defined requirements be kept?
The Business Requirements Document (BRD) prepared by the business analyst (BA) was circulated to stakeholders for approval. Some stakeholders objected to the Use Case diagrams and could not understand them. Why would these be included in the document?
A business analyst (BA) is developing the requirements for an inventory management system. Some current accounting processes are automated but other departments like purchasing, marketing, sales and distribution departments work in isolation and have a manual process. They extensively use spreadsheets to maintain the transactions and at the end of the day the department managers manually verify and reconcile transactions before supplying the information to the accounting department. In order to verify and validate the elicited requirements, the BA will need to prepare a:
You are the business analyst for your organization and you're preparing to elicit requirements from the stakeholders. You've gathered several inputs to help with the elicitation process. Which input(s) will be used to ensure that you understand the type of information that should be elicited from the stakeholders?
