Define Requirements Flashcards
what is the requirement engineering framework?
a structured approach to develop well-defined requirements:
Elicitation Analysis Validation Documentation Management
what is the Elicitation stage?
drawing out information and requirements from stakeholders
using a choice of elicitation techniques
documenting them in a Requirement List
What is the analysis stage?
the BA reviews the collected requirements to ensure they are well-formed and categorised.
What is the validation stage?
involved the stakeholders reviewing the requirements and sign off the document so that it is handed over the Development team.
What is the documentation stage?
it s an iterative stage throughout the RE framework where the BA documents the requirements in a list and supporting visual models.
What is the management stage?
it is an iterative stage throughout the RE framework to manage potential changes to requirements, their versions and enable their traceability.
How do we ensure requirements meet quality criteria?
Requirements must be:
clear concise consistent correct atomic unambiguous complete measurable testable traceable relevant
Explain the 4 types of requirements
General - business policies and constraints, ie: the system shall comply with GDPR laws.
Technical - IT policies and constraints on what the system should do, ie: the system shall operate with Chrome, Safari and EI.
Functional - what the system must do, ie: users must be able to choose their seats.
Non-Functional - how well the system must behave, e: the system must record up to 50 customers a day.
Who are the actors that should attend the validation meeting?
Business representatives - sponsor, SMEs, users
Project Team - project manager, BA, developers, testers, author, PMO.
Explain the requirement prioritisation technique
MOSCOW in an iterative environment:
Must-Have in this sprint as the solution cannot exist without those requirements,
Should-Have do add value to the customer & can be included in this sprint if there is time otherwise,
following sprint with a workaround in the meantime,
Could-Have are a nice-to-have and can be left out altogether or for a later sprint
Want to Have but won’t have this time around - not important and helps to avoid scope creep, can be re-prioritised at a later stage
Explain the 2 types of validation
Informal - quick conversation at someone’s desk leading to a verbal sign off
Formal - a group review to ensure all requirements are meeting business objectives leading to a written sign off
Describe the content of a Requirement Document
Introduction and background - context, objectives, scope, constraints, assumptions, stakeholder list
process models - process maps, swimlane diagram, activity diagram
functional models - context diagram, use case models and descriptions, traceability matrix
data models - ERD, class, data dictionary
requirement catalogue - general, technical, functional & NFR
glossary
Describe the 16 items of a Requirement Catalogue
ID and/or version Name Description Source Owner Business area Priority Type Associated NFR Acceptance criteria Justification Related documents Related requirements Resolution Comments catalogue version
What is the verification process?
BA and stakeholders will check that the requirements and supporting documentation are ready for validation. We ensure that things are done right.
What is Configuration Management?
it is a way of differentiating between different version of the requirements and their documents.
