Quality Assurance QA Module 4

Minimum Viable Product, MVP

A version of the product that allows the team to collect maximum customer information and feedback from them at minimal cost.

Stakeholder

A person who gives feedback to the Product Owner and the Scrum team as a whole on vision, Product Backlog and Increments.

Sprint Board

A tool that helps to visualize the Backlog of the Sprint throughout the Sprint.

requirement

A provision that contains criteria to be fulfilled.

business requirements

Express the purpose for which the product is developed (why is it needed at all, what is the expected benefit of it, how the customer will make a profit with its help).

user requirements

Describe the tasks that the user can perform using the system being developed

functional requirements

Describe the behavior of the system, i.e. its actions (calculations, conversions, checks, processing, etc.).

non-functional requirements

Describe the properties of the system (ease of use, safety, reliability, expandability, etc.) that it should have when implementing its behavior.

atomicity

A requirement is atomic if it cannot be broken down into separate requirements without losing completeness and it describes one and only one situation.

consistency

The requirement should not contain internal contradictions and contradictions to other requirements and documents.

unambiguousness

The requirement should be described without the use of jargon, non-obvious abbreviations and vague formulations, should allow only an unambiguous objective understanding and be atomic in terms of the impossibility of different interpretation of the combination of individual phrases.

feasibility

The requirement should be technologically feasible and implementable within the budget and terms of project development.

obligatoriness

If the requirement is optional, it should simply be excluded from the set of requirements. If the requirement is necessary, but "not very important", the priority indication is used to indicate this fact.

traceability

Vertical allows you to correlate requirements at different levels of requirements, horizontal allows you to correlate the requirement with the test plan, test cases, architectural solutions, etc.

modifiability

This property characterizes the ease of making changes to individual requirements and a set of requirements.

ranked for importance, stability, priority

Importance characterizes the dependence of project success on the success of the requirement implementation. Stability characterizes the probability that no changes will be made to the claim in the foreseeable future.

Urgentness determines the distribution of the efforts of the project team over time to implement a particular requirement.

use cases

Are scenarios of user (or users) interaction with a software product to achieve a specific goal.

user story

A user or business requirement consisting of one sentence expressed in the everyday or business language which is capturing the functionality a user needs, the reason behind it, any non-functional criteria, and also including acceptance criteria.

acceptance criteria

The criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.