A. Communicate business analysis package
B. Monitor stakeholder engagement
C. Guide elicitation activity
D. Collaborate assigned tasks
A. is understood independently of other requirements or designs.
B. aligns with the identified needs of the stakeholders.
C. uses common terminology understood by the audience.
D. contains no extraneous or unnecessary content.
A. Decision
B. Modeling
C. Impact
D. Competitive
A. Scope modelling
B. User stories
C. Business case
D. Lessons learned
A. Solution
B. Evaluation
C. Approval
D. Acceptance
A. Theoretical
B. Quantitative
C. Statistical
D. Qualitative
A. Number of customers and end-users affected
B. Amount of time needed to create new documents
C. Agreement by executive board members
D. Capacity of the requirements management tool
A. SWOT analysis, workshop, cost analysis
B. Inspection, formal walkthrough, desk check
C. Brainstorming, functional decomposition, lessons learned
D. Mind mapping, decision analysis, interviews
A. Project manager
B. Business analyst
C. Programmer
D. Project sponsor
A. Experiment
B. Interview
C. Research
D. Collaboration
