Software Quality Assurance: Testing Essentials, Exams of Biology

A concise overview of key concepts in software quality assurance, focusing on testing essentials. It defines terms like quality control, quality assurance, and different types of defects, including solution defects, requirements defects, and business requirements. The document also explains the importance of smart requirements and the processes of verification and validation in software development.

Typology: Exams

2024/2025

Available from 11/02/2024

tutor-lee-1
tutor-lee-1 🇺🇸

4.3

(3)

11K documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Software Quality
Assurance
(Chapter 1:
Testing
Essentials)
Quality Control - answer The process of determining
whether the software works as required
Quality Assurance - answer A set of practices that
removes defects prior to testing
Solution Defect - answer A deficiency in a product or
service that reduces its quality or varies from a desired
attribute, state, or functionality
Requirements Defect - answer An error in requirements
caused by incorrect, incomplete, missing, or conflicting
requirements
pf3

Partial preview of the text

Download Software Quality Assurance: Testing Essentials and more Exams Biology in PDF only on Docsity!

Software Quality

Assurance

(Chapter 1:

Testing

Essentials)

Quality Control - answer The process of determining whether the software works as required Quality Assurance - answer A set of practices that removes defects prior to testing Solution Defect - answer A deficiency in a product or service that reduces its quality or varies from a desired attribute, state, or functionality Requirements Defect - answer An error in requirements caused by incorrect, incomplete, missing, or conflicting requirements

Business Requirement - answer A higher-level requirement that defines a business objective or goal for the project or initiative Stakeholder Requirement - answer Defines the need of a particular stakeholder, commonly defined through use cases Solution Requirement - answer Describes specific characteristics of the solution both in terms of functionality and quality of service. Can be functional or non-functional. Functional Requirement - answer Defines details of the expected behavior of the solution Non-functional Requirement - answer Defines a quality of service requirement such as those relating to speed, response time, throughput, usability, security, privacy, availability, etc. Transition Requirement - answer Expresses how the solution will be placed into service and how to transition from the current state of the organization to its future state