Buisness Quiz: Requirements Management And Communication

Surveys/questionnaires, document analysis, and interviews are techniques used by a business analyst.

Approved requirements are solution components that that have stakeholder agreement and are ready for use. Traced requirements are the solution components that are considered essential by the stakeholder and have clear relationships to other requirements. The requirements package is the document that contains the requirements for stakeholder review. The other answer is a distractor.

Requirements can be communicated to stakeholders via conversations, discussions, conferences and documentation. Observation is used to elicit requirements, not convey them.

The requirements created during Requirements Management & Communication task are approved requirements, traced requirements, maintained and reusable requirements, packaged requirements, and communicated requirements.

The sequence of the Requirements Management & Communication tasks is Manage Solution Scope and Requirements, Manage Requirements Traceability, Maintain Requirements for Re-use, Prepare Requirements Package, Communicate Requirements.

Selecting a homogeneous group will exclude the differing perspectives shared when the participants are not alike. Selecting a heterogeneous group may provide lower quality results since those with different perspectives might be uncomfortable. Power user and closed-ended are distracters.

Traced requirements are the solution components that are considered essential by the stakeholder and have clear relationships to other requirements. Approved requirements are solution components that that have stakeholder agreement and are ready for use. The requirements package is the document that contains the requirements for stakeholder review. The other answer is a distracter.

To complete a requirements workshop, the business analyst should document what was discovered in the workshop and validate that it aligns with the stakeholder needs.

The approaches for conflict resolution are communication between the stakeholders, formal meetings, third party resolution, and research. Coverage is not a conflict resolution approach.

A configuration management system is used to trace large numbers of requirements. A change control system is used to track changes. The other answers are distracters.

Maintaining requirements for re-use allows an organization to use those requirements for future solutions or projects and those requirements become organizational process assets.

A regulator is involved with the business analyst in establishing government, legal, and contractual requirements, but not process requirements.

There are three elements associated with managing requirements traceability. They are relationships, impact analysis, and a configuration management system.

The Conduct Elicitation Activity task is comprised of meeting with stakeholders to determine their needs and requirements in relation to the opportunity or project. The Prepare for Elicitation task is comprised of identifying and scheduling all resources needed to affect the necessary elicitation activities for the project or opportunity. The Document Elicitation Results task is comprised of logging the results of the stakeholder elicitation meetings. The Confirm Elicitation Results task is comprised of meeting with the stakeholders to ensure that the requirements align with the stakeholder needs and expectations in relation to the solution.

An evolutionary prototype is a prototyped that is modified or updated continuously based on user feedback. A throw-away prototype is a prototype created with simple tools which is used to determine and refine interface requirements and is typically discarded upon completion of the final system. Prototyping is too general in this case. Agile development is the general approach used in this instance, but the evolutionary approach is the better answer because it is more specific.

The requirements package is the document that contains the requirements for stakeholder review. Approved requirements are solution components that that have stakeholder agreement and are ready for use. Traced requirements are the solution components that are considered essential by the stakeholder and have clear relationships to other requirements. The other answer is a distractor.

Stated, unconfirmed requirements are the solution components that the business analyst determines to be considered essential by the stakeholder. You will need to document the information, then obtain confirmation from the stakeholder that the documented requirements accurately describe the requirements that he considers essential to the solution. Assumptions and constraints are a distracter.

The main output of Manage Solution Scope and Requirements is approved requirements. One of the key techniques is baselining.

Alternate terms for a storyboard are dialog map and navigation flow. A process flowchart depicts the steps of a process. A Gantt chart depicts the order in which project activities occur. State diagram is a distracter.

A drawing pad is used to create a throw-away prototype. The drawing pad shows stakeholders the lay out of the screen. Storyboarding depicts sequence. Document analysis, used to extract information from existing documentation, is typically used to establish requirements. Preliminary prototyping is a distracter.