A need or want of the business to solve a problem or achieve an objective.
A condition or capability of a product or solution that documents a problem or objective of the business.
A need or necessary feature of a system that could be sensed from a position anywhere within the system.
A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
A known deliverable.
A documented representation of a condition or capability.
Whatever the business analyst deems it to be.
A list of items presented to the business analyst on a napkin.
A set of changes to the current state.
Automation of a new end product.
Changes to the current software and the associated business processes.
Anything that solves a business problem or seizes an opportunity.
Training of technical team on new software.
Helping to build usability into the application software.
Construction of the software and driving the implementation process.
Making decisions regarding tradeoffs that impact the requirements.
Allocate requirements (task) and release planning (element). Allocate requirements (task) and release planning (element).
Define solution scope (task) and implementation approach (element).
Determine solution approach (task) and implementation approach (element).
Determine solution approach (task) and release planning (element).
Solution performance assessment.
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.
Session objectives so people know the purpose of the session.
Desired outcome so people know what should be produced as part of the session.
Gauging the group's ability to reach consensus.
A plan for the Requirements Elicitation techniques to be used during the session.
Interfaces to and from external applications.
UIs (user interfaces).
Interfaces to and from external hardware devices.
Plan Business Analysis Approach.
Conduct Stakeholder Analysis.
Plan Business Analysis Communication.
Business analysis performance metrics.
Business analysis plans.
Organizational process assets.
A diagram with stick-figure actors connected to use cases drawn in ovals.
Text flows of events that describe the steps an actor takes to accomplish the goal of a use case.
A diagram with stick-figure actors connected to use cases drawn in ovals, and text flows of events that describe the steps an actor takes to accomplish the goal of a use case.
A diagram with stick-figure actors connected to use cases drawn in ovals, text flow of events that describe the steps an actor takes to accomplish the goal of a use case, and associated documented business rules affecting the use case.
Improve access to stakeholders.
Improve access to information.
Increase consistency of behavior.
Document the data characteristics which will become the columns or fields in a database.
Document the business concepts that will be the basis for Use Cases that involve data.
Document the business objects that will contain data characteristics.
Be used mainly for database design, because entities or classes do not belong in requirements documentation.
It ensures all stakeholders have been involved in the requirements management plan which provides the process for prioritization of requirements.
It indicates levels of power to determine which stakeholders are needed for prioritization.
It helps the project manager create the meeting invitation for the requirements prioritization meeting.
It provides the organizational structure that will be impacted by the solution.
Specificity, performance, interface, privacy, environmental.
Unique, privacy, operational, quality, environmental, transferability.
Security, reliability, operability, compatibility, maintainability
Security, performance, quality, unique, complete
Reliability, operability, security, functionability.
Dependability, operability, performance efficiency, security.
Reliability, operability, compatibility, transferability.
Reliability, operability, adjustability, scalability.
Assumptions may affect all aspects of the project and pose a certain degree of risk.
Assumptions and constraints are generally documented with associated attributes.
Assumptions and constraints are generally documented to be generic, like business rules.
Constraints are defined as restrictions or limitations on possible solutions.
Rounded rectangles converging independent flows into a single flow.
Branches represented by a horizontal bar with multiple paths continuing forward.
Diamonds from one path to one or more mutually exclusive alternate paths.
Joins represented by a diamond bringing a number of parallel flows into a single flow.
Context level data flow diagram.
Functional decomposition diagram.
Functional requirements analysis.
Non-functional requirements analysis.
Confidence of the participants in the decision-analysis process. Confidence of the participants in the decision-analysis process
Decisions are made by considering the interest of every stakeholde
Stakeholders include the BA in the decision making process.
Confidence of the participants in the selected solution.
Context scope diagram.
Executive sponsors and management want high-level requirements, so include executive summaries.
Many business SMEs will not be available to review requirements, so there is little need to write in the language they can understand.
There is virtually little difference in the time needed to prepare formal or informal requirements reviews. The difference lies in the organizational level of the audience being presented to.
A requirement may be presented informally in an e-mail message, a note, or verbally.
According to the situation and stakeholder.
During requirements workshops and structured walkthroughs.
According to the BA communication plan.
Likelihood of a risk.
Impact of a risk.
Scope of a risk.
Mitigation of a risk.
Acceptance, transfer, mitigation.
Acceptance, enhance, mitigation.
Share, transfer, exploit.
Share, enhance, exploit.
Make best use of earned value for determining the health of the business analysis activities.
Analyze risk probability and impact.
Store and access project historical records.
David's business analysis communication plan was incomplete.
David's business analysis plan was incomplete.
David did not get the necessary stakeholder analysis information from the project manager.
David forgot to review previous project documentation to identify all stakeholder involvement.
Force field analysis.
Determine Solution Approach.
Conduct Feasibility Analysis.
Assess Organization Readiness.
During requirements signoff.
During lessons learned.During the requirements workshop.
During a structured walkthrough.
Evaluate whether stakeholders are prepared to make use of the solution.
Assess impact of business analysis to organization.
Evaluate whether stakeholders are physically capable of operating the equipment.
Evaluate alternative solutions and recommend effect on operational aspects of the organization.
User requirements model.
The business analyst plays a key role in the eliciting of requirements and stakeholder concerns.
The business analyst ensures that requirements are elicited and prioritized for approval.
The business analyst ensures that solutions meet the business need and to facilitate their successful implementation.
The business analyst ensures that requirements are fully realized.