You are the business analyst for your organization and you're creating the requirements package. In this documentation, to what level should you document the requirements for your stakeholders?
A) All requirements should be clearly defined with technical, business, functional, and non-functional attributes.
B) All requirements should be defined only to the extent needed to assure understanding by the team.
C) All requirements should be defined to the extent the organizational process assets demand.
D) All requirements should be defined in detail to the work package level of WBS.

Question

You are the business analyst for your organization and you're creating the requirements package. In this documentation, to what level should you document the requirements for your stakeholders?
A) All requirements should be clearly defined with technical, business, functional, and non-functional attributes.  
B) All requirements should be defined only to the extent needed to assure understanding by the team.
C) All requirements should be defined to the extent the organizational process assets demand.
D) All requirements should be defined in detail to the work package level of WBS.

Quizplus · Accepted Answer

When creating the requirements package, as in this scenario, it's mandatory that the requirements be defined with enough detail that the team can understand the requirements. Answer: D is incorrect. This isn't a valid explanation for the level of detail needed in the requirements package. Answer: A is incorrect. Not all requirements need the technical, business, functional, and non-functional requirements. Answer: C is incorrect. The organizational process assets won't demand that the requirements be defined to any extent. This isn't a valid answer for this question.

You Are the Business Analyst for Your Organization and You're