Plan requirements management, plan requirements communication.
Prepare for elicitation, execute requirements work plan.
Plan requirements management, conduct stakeholder analysis.
Confirm elicitation resources, build requirements work plan.
A non-actionable directive that supports a business goal.
An actionable directive that supports a business goal.
A passive directive that supports a business goal.
A manual that has been created to show the roles and responsibilities of the team.
UIs (user interfaces).
Interfaces to and from external applications.
Interfaces to and from external hardware devices.
Documenting elicitation results.
Executing requirements work plan
Conducting elicitation activities.
Organizational assets, requirements work plan.
Requirements work plan, stakeholder communication, risk analysis.
Observation, prototype, assigned resources.
Supporting materials, scheduled resources.
Meeting minutes, whiteboards, town hall meeting.
Audio recording, virtual whiteboard..
Meeting minutes, videotaping, requirements workshop.
Communication plan, project plan, requirements plan.
The project team
Any stakeholder who has participated in elicitation tasks.
Stakeholders with enough authority to approve requirements.
Interviews and Reverse Engineering.
Requirements workshop and prototyping
Interface analysis and focus group.
Interviews and prototyping.
They will uncover additional data attributes and relationships.
They will help to refine processing requirements for navigation of interfaces.
Use cases help provide the foundation for UIs, including how they should respond to actors.
Documenting user interfaces is not a requirements activity, but should be left to interface designers.
Used for historical purposes and project planning by the project manager.
To ensure that when elicitation produces issues they are tracked to resolution.
Used to ensure the help desk and service management teams are kept in the loop when the resulting production issues come up due to the problems that have been raised.
To ensure the results of your requirements workshops and interviews are documented.
Select requirements activities based on the product being built and then identify stakeholders to provide you with their requirements.
Identify stakeholders and then select requirements activities appropriate to them.
Identify only stakeholders with the necessary time and knowledge and then select requirements activities appropriate to them.
There is no typical relationship between stakeholders and selecting requirements activities.
Availability and physical distance separating the stakeholders.
Project budget and size, and the time allowed to gather requirements.
Requirements documentation tools.
Political issues and power among the stakeholders.
The horizontal prototype models a shallow, and possibly wide view of the system's functionality.
The throw-away prototype seeks to quickly uncover and clarify interface requirements using simple tools, sometimes just paper and pencil.
The vertical prototype models deep, and usually narrow slice of the entire system's functionality.
The evolutionary prototype is not as rigorous as the vertical model and is not intended to extend to a fully functional system.
A purchased software system.
Developing a risk register
An enhancement to an existing automation system.An enhancement to an existing automation system.
An enhancement to a business system.
Requirements management tools.
Configuration management tools.
Specialized application tools.
An 'extends' use case is functionally equivalent to an alternate flow of events
An 'includes' use case must be complete if it is not directly triggered by an actor.
UML standards mandate that an Activity Diagram must be developed to accompany a Use Case diagram.
A 'depends' use case retains the flow of events where the alternate paths are not restricted.
Identify improvement opportunities.
Analyze current documentation and systems.
Capture requirements attributes.
Interviews and root cause analysis.
Organization modeling and decision analysis.
SWOT analysis and business rules analysis.
Data flow diagrams and focus groups.
Business analysis solution assessment plan.
Interaction of the organization and its customers.
Solution assessment recommendation.
Cost-Benefit Analysis, Payback Period, and SWOT analysis.
Document Analysis, Estimating techniques, and Net Present Value.
Goal Baselining, Estimating techniques, and SWOT analysis.
Competitive analysis and benchmark studies, Estimating techniques, and Reverse Engineering.
As a supplement to technical design.
To describe service level requirements.
When a SME cannot decide the priority of a requirement.
As a supplement to the testing process.
The business analyst.
The project team.
The business analyst and the stakeholder(s) the requirements were elicited from.
People who operate and maintain the solution.
Allowing an online focus group to include members located remotely while participating by a network connection.
Reaching agreements with stakeholders on what interfaces are needed.
Coordinating the activities used to elicit interface requirements.
Capturing requirements attributes for interfaces.
Products, services, processes, and solution scope.
Products, services, events, and software features.
Software features, tasks, events, and requirements.
Products, services, goals, and assumptions.