4. Requirements Definition Flashcards
Why do we document requirements
To ensure there is an understanding between all parties involved in a project of the business needs, projects can be scheduled accordingly, and solutions are aligned with business strategy and objectives
What is a requirement
A requirement in the context of Business Analysis is a statement provided by a stakeholder about what they believe they need in order to solve a particular business problem, carry out an activity related to their role or respond to a specific business need.
Why do we prioritise requirements
By prioiritising our requirements we can identify those that are vital to our processes from those that the stakeholders could do without, or with a workaround. This allows us to deliver requirements in increments or reduce our requirements list if required.
Name a method for Prioritising requirements
MOSCOW
How do we gather requirements
Through requirement elicitation with stakeholders, there are many techniques to do this, such as workshops, interviews, shadowing, document analysis
What are the characteristics of a good requirement
Specific Measurable Achievable Relevant Time-bound
Name some common problems with requirements
Lack of relevance to project objectives Ambiguity Duplication Not specific Difficult to test Assume solutions
What are the 5 steps to the business analysis framework
Investigate situation Consider perspectives Analyse needs Evaluate options Define Requirements (can be being gathered throughout)
Name a technique used to elicit requirements
Interviews Workshops Observation Shadowing Questionnaires Document analysis Focus groups Sampling Special purpose records Scenarios Prototyping
Why is it important to plan and estimate requirement engineering
Requirement gathering and analysis is often undervalued in a project plan.
This requirement documentation stage of a project is vital to its success and therefore sufficient time needs to be allocated to the process.
What is the SDLC
Software development life cycle
Give 5 steps of a SDLC
Design Development Acceptance testing Implementation Maintenance
What are the 5 elements of Requirements engineering
Req Elicitation Req analysis Req validation Req documentation Req management
What different types of knowledge are there
Tacit
Explicit
Explain Tacit knowledge
Tacit knowledge is knowledge that is difficult for a stakeholder to explain or articulate, such as skills, actions, culture norms, things they take for granted
Explain Explicit knowledge
Explicit knowledge is knowledge that can be evidenced such a processes, procedures, reports, targets
Give a technique for eliciting Tacit knowledge
Observation or shadowing
Give a technique for eliciting Explict knowledge
Document analysis, interviews, workshops, MOST elicitation techniques
What is the difference between Req’ elicitation and Req’ analysis
Requirement elicitation is the gathering of information in order to document requirements, requirement analysis is the analysis that is needed to be done against the requirements to ensure that they are organised, non-conflicting, well-formed and of quality to the business and the projet
Name 3 tasks involved in Req’ analysis
Checking congruence with business objectives and the business case
Checking feasibility
Structuring the requirements
Prioritising requirements
Packaging requirements for delivery
Use of scenarios and prototyping in requirements analysis
Dealing with overlapping, duplicate and conflicting requirements
How would you deal with overlapping, duplicate and conflicting requirements
Identify each stakeholders perspective to highlight the reasons for the conflict
gather involved stakeholders and decision makers together to discuss the conflict
What is requirement prioritisation
Prioritisation – the structure and application of a technique to allocate a priority to each requirement. This can then be used to allow for interations of packages of requirements to be delivered and to identify requirements that are not vital to the business objectives and solution
What characteristics should a requirement be, name 3
Testable Unambiguous Relevant Clear Complete Consistent Traceable
How do we validate requirements
…
Which stakeholders may be involved in the requirement engineering process
Project stakeholders
- Project Manager
- Business Analysts
- Solution developers
- Testers
- System Architects
Business stakeholder
- Project Sponsor
- SMEs (Business and Industry)
- End users and managers (For who the solution is designed)
What is Requirement elicitation
Gathering info from stakeholders and creating req list
What is requirement validation
Getting requirements signed off as correct and covering business need by key stakeholders
What is requirement management
Requirements Management is an iterative set of activities that help ensure that elicitation, documentation, refinement, and changes of requirements is adequately dealt with during a project lifecycle
What is requirement documentation
Requirement documentation is the chosen template within which requirements are documented, with information supporting the user story, in order to be published to the project team for use
What is requirement analysis
The work done to confirm a requirement is of quality, non-conflicting, well-structured and well-formed for use of all those in the project.
