Please enable JavaScript.
Coggle requires JavaScript to display documents.
QA Week 4 - Chapter 5 - Coggle Diagram
QA Week 4 - Chapter 5
Requirements Engineering
-
-
Standards that define, for example, what we mean by 'good' requirements
Framework
Requirement Elicitation
-
Tacit Knowledge - Things users think are so widely known, that they do not bother to mentioned to their Business Analysis
Qualitative Elicitation Techniques: Interviews, Workshops, Focus Groups, Observations, Shadowing, Scenarios, Prototyping.
Quantitative Elicitation Techniques: Questionaries and surveys, Documentation Analysis, Record searching, Special Purpose Records, Activity Sampling
-
-
-
User Stories
Small Pieces of functionality that are to be developed in collaborative sessions between the users and software developers
-
Requirements Management
Set of processes and procedures through which the set of requirements is managed throughout the project.
-
Requirement Engineering and agile development: Adjustments are needed so that the requirements are scoped out in early stages but only fully developed just before the final development stage.
Requirements Engineering: If a product is bought off the shelf customisation is limited and what the users want and and what the system can do don't always align.
Types of Requirements
-
-
General Requirements - High level, overarching requirements of a technical policy nature
-
-
-
-
-