Requirements Elicitation and Documentation
Expert-defined terms from the Professional Certificate in Digital Business Analysis course at London School of Planning and Management. Free to read, free to share, paired with a globally recognised certification pathway.
Requirements Elicitation and Documentation #
Requirements Elicitation and Documentation
Requirements elicitation and documentation are crucial processes in the field of… #
These processes involve identifying, analyzing, documenting, and managing the needs and expectations of stakeholders to ensure that a digital solution meets their requirements and delivers value to the organization. Effective requirements elicitation and documentation are essential for project success as they help bridge the gap between business stakeholders and technical teams, ensuring that the final product meets the needs of the users and the business.
Requirements Elicitation #
Requirements Elicitation
Requirements elicitation is the process of gathering, analyzing, and documenting… #
This process involves various techniques such as interviews, workshops, surveys, and observations to gather information about the desired functionality, constraints, and quality attributes of the digital solution. The goal of requirements elicitation is to ensure that all stakeholders have a shared understanding of the project scope and objectives, which is essential for successful project delivery.
Example #
During the requirements elicitation phase of a digital project, a business analyst conducts interviews with key stakeholders to gather information about their needs and expectations for the new system.
Requirements Documentation #
Requirements Documentation
Requirements documentation involves capturing and documenting the gathered requi… #
This documentation serves as a reference for the project team throughout the development process, helping to ensure that the final product meets the agreed-upon requirements. Requirements documentation typically includes functional and non-functional requirements, use cases, user stories, and acceptance criteria, among other artifacts.
Example #
A business analyst creates a requirements document that outlines the key features, functionalities, and constraints of a new digital platform based on the information gathered from stakeholders during the requirements elicitation phase.
Stakeholder Analysis #
Stakeholder Analysis
Stakeholder analysis is a technique used to identify and analyze the stakeholder… #
By conducting stakeholder analysis, business analysts can prioritize stakeholders, manage their expectations, and ensure that their needs are adequately addressed in the requirements elicitation and documentation processes.
Example #
A business analyst conducts a stakeholder analysis to identify the key stakeholders for a digital transformation project, assess their level of influence and interest in the project, and develop a communication plan to engage with them effectively.
Interviews #
Interviews
Interviews are a common technique used in requirements elicitation to gather inf… #
By conducting interviews with key stakeholders, business analysts can gain valuable insights into the project requirements, clarify any ambiguities, and ensure that all stakeholders have a shared understanding of the project goals and objectives.
Example #
A business analyst conducts one-on-one interviews with department heads to gather information about their departmental requirements for a new digital reporting system.
Workshops #
Workshops
Workshops are collaborative sessions that bring together stakeholders, subject m… #
Workshops are an effective way to elicit requirements, resolve conflicts, and build consensus among stakeholders. By facilitating workshops, business analysts can ensure that all stakeholders have a voice in the requirements elicitation process and that the project goals are aligned with the business objectives.
Example #
A business analyst organizes a requirements workshop with key stakeholders to brainstorm ideas, prioritize features, and define the scope of a new digital marketing campaign.
Surveys are a method of requirements elicitation that involves collecting data f… #
Surveys are useful for gathering a large amount of information from a diverse group of stakeholders quickly and efficiently. Business analysts can use surveys to gather feedback on existing processes, identify pain points, and prioritize requirements based on stakeholder preferences.
Example #
A business analyst sends out a survey to employees to gather feedback on the usability of the current CRM system and identify areas for improvement in the upcoming system upgrade.
Observations #
Observations
Observations involve directly observing stakeholders in their work environment t… #
By observing stakeholders in action, business analysts can gain valuable insights into their needs, preferences, and pain points, which can help inform the requirements elicitation process. Observations can provide a more holistic view of stakeholders' requirements than other elicitation techniques.
Example #
A business analyst spends a day shadowing customer service representatives to observe how they interact with customers, identify pain points in the current system, and gather requirements for a new customer relationship management (CRM) system.
Functional Requirements #
Functional Requirements
Functional requirements define the specific features, functions, and capabilitie… #
Functional requirements describe what the system should do in terms of inputs, outputs, processes, and interactions with users. Business analysts work with stakeholders to elicit and document functional requirements to ensure that the final product meets the business objectives and user needs.
Example #
A functional requirement for an e-commerce website may be that customers can add products to their shopping cart, view product details, and proceed to checkout to complete their purchase.
<bNon #
Functional Requirements
Non #
functional requirements specify the quality attributes and constraints that a digital solution must meet, such as performance, scalability, security, and usability. Non-functional requirements describe how the system should behave in terms of reliability, availability, and maintainability. Business analysts work with stakeholders to elicit and document non-functional requirements to ensure that the final product meets the desired level of quality and performance.
Example #
A non-functional requirement for a mobile banking app may be that the app must load within three seconds to provide a seamless user experience for customers.
Use Cases #
Use Cases
Use cases describe how users interact with a digital solution to achieve specifi… #
Use cases typically include a description of the user's actions, the system's responses, and any alternative paths or exceptions that may occur. Business analysts use use cases to illustrate the functional requirements of a system in a structured and user-friendly format that is easy for stakeholders to understand.
Example #
A use case for a social media platform may describe how a user creates a new post, adds tags and images, and publishes the post for their followers to see.
User Stories #
User Stories
User stories are short, simple descriptions of a feature or functionality from t… #
User stories typically follow a specific format: "As a [user role], I want [feature] so that [benefit]." User stories help business analysts and development teams prioritize requirements, focus on user needs, and deliver value incrementally. User stories are commonly used in agile methodologies to manage requirements and track progress.
Example #
A user story for a messaging app may be: "As a user, I want to send text messages, images, and videos to my friends so that I can stay connected with them in real-time."
Acceptance Criteria #
Acceptance Criteria
Acceptance criteria are specific conditions or criteria that must be met for a r… #
Acceptance criteria help define the boundaries of a requirement, clarify expectations, and provide a benchmark for testing and validation. By documenting acceptance criteria, business analysts can ensure that the development team understands the requirements and can deliver a product that meets stakeholder expectations.
Example #
Acceptance criteria for an online booking system may include requirements such as: "The system must allow users to select dates, times, and locations for their bookings" and "Users must receive a confirmation email after making a booking."
Challenges in Requirements Elicitation and Documentation #
Challenges in Requirements Elicitation and Documentation
Requirements elicitation and documentation can present several challenges for bu… #
Some common challenges include:
1. Ambiguous Requirements #
Stakeholders may provide vague or conflicting requirements, making it difficult to understand their needs and expectations.
2. Changing Requirements #
Stakeholders' needs and priorities may change over time, necessitating constant communication and adaptation of requirements.
3. Scope Creep #
Additional requirements may be added to the project without proper analysis or evaluation, leading to scope creep and project delays.
4. Stakeholder Engagement #
Engaging with diverse stakeholders with varying interests and priorities can be challenging, requiring effective communication and relationship management.
5. Requirements Prioritization #
Determining which requirements are most critical to the project's success can be challenging, especially when stakeholders have conflicting priorities.
By addressing these challenges proactively and using effective requirements elic… #
By addressing these challenges proactively and using effective requirements elicitation and documentation techniques, business analysts can ensure that the project delivers value to stakeholders and meets their expectations.