Software quality testing

Short answers

Unit-1

**1. Total Quality Management (TQM):**

- **Definition:** Total Quality Management is a management philosophy that focuses on

continuous improvement in all aspects of an organization. It involves the active participation of all
members to enhance processes, products, services, and the overall organizational culture.

**2. Information Engineering:**

- **Definition:** Information Engineering is a methodology for designing, planning, and

implementing information systems. It emphasizes a top-down approach, focusing on business
needs, data architecture, process modeling, and technology infrastructure to develop effective
information systems.

**3. ISO (International Organization for Standardization):**

- **Definition:** ISO is an international standard-setting body that develops and publishes

standards to ensure the quality, safety, and efficiency of products, services, and systems. ISO
standards cover various industries and disciplines.

**4. Software Process:**

- **Definition:** Software process refers to a set of activities, methods, practices, and

transformations applied to develop and maintain software systems. It includes processes for
requirements gathering, design, coding, testing, deployment, and maintenance.

**5. Kaizen:**

- **Definition:** Kaizen is a Japanese term that translates to “continuous improvement.” In the

context of business and management, Kaizen refers to the philosophy of continuous, incremental
improvement in all aspects of an organization, involving all employees.

**6. Quality:**
 - **Definition:** Quality is the degree to which a product or service fulfills or exceeds customer
expectations. It encompasses attributes such as performance, reliability, durability, and other
characteristics that contribute to customer satisfaction.

**7. Quality Control:**

- **Definition:** Quality Control is a set of activities and techniques used to ensure that a product
or service meets specified requirements. It involves the inspection, testing, and monitoring of
processes to identify and rectify defects or deviations from quality standards.
-

Unit-2

**1. Software Requirements Specifications (SRS):**

- **Definition:** Software Requirements Specifications (SRS) is a comprehensive document that

outlines the functional and non-functional requirements of a software system. It serves as a
communication bridge between stakeholders and the development team, providing a detailed
description of what the software should do.

**2. Walkthrough:**

- **Definition:** A walkthrough is a form of peer review where software developers, testers, or

stakeholders come together to review and discuss a document, code, or design. The purpose is to
identify issues, obtain feedback, and ensure a common understanding among team members.

**3. Cyclomatic Complexity:**

- **Definition:** Cyclomatic Complexity is a software metric used to measure the complexity of a

program. It is calculated based on the number of linearly independent paths through a program’s
source code, providing insights into the potential number of test cases required for thorough
testing.

**4. Types of Metrics:**

- **a. Size Metrics:** Measure the size of software artifacts, e.g., lines of code, function points.

- **b. Complexity Metrics:** Evaluate the complexity of software, e.g., cyclomatic complexity.

- **c. Quality Metrics:** Assess the quality of software, e.g., defect density, failure rate.

- **d. Process Metrics:** Measure the efficiency and effectiveness of the software development
process, e.g., lead time, cycle time.
**5. Inspection:**

- **Definition:** Inspection is a formal review process where a team examines a software product
or document to identify defects, issues, and improvements. It is a systematic method of verification
and validation used to improve the quality of software artifacts.

**6. Lines of Code (LOC):**

- **Definition:** Lines of Code is a metric used to measure the size of a software program by
counting the number of lines in the source code. While it provides a basic measure of size, it is
essential to consider other metrics and factors for a comprehensive evaluation of software
complexity and maintainability.

Unit-3

**1. Defect:**

- **Definition:** A defect, also known as a bug or issue, is a flaw or imperfection in a software

product that may cause it to behave incorrectly, produce unexpected results, or fail to meet
specified requirements.

**2. Unit Testing:**

- **Description:** Unit testing is a level of software testing where individual units or components of
a program are tested in isolation. It ensures that each unit functions as intended by validating its
behavior, inputs, and outputs. Unit testing is typically performed by developers during the
development phase.

**3. Testing:**

- **Definition:** Testing is the process of evaluating a software application or system to identify

defects, ensure its compliance with specified requirements, and verify that it meets the intended
purpose.

**4. Debugging:**
 - **Definition:** Debugging is the process of identifying, isolating, and fixing defects or errors in a
software program. It involves the examination of code, system logs, and other diagnostic tools to
understand and eliminate the root cause of issues.

**5. Failures:**

- **Definition:** Failures occur when a system, software, or component does not perform as
expected and deviates from its specified behavior, leading to incorrect or unexpected results.

**6. White Box Testing:**

- **Definition:** White box testing, also known as structural or glass-box testing, is a testing
approach that involves examining the internal logic, code structure, and implementation details of
a software system. Test cases are derived from the internal design and code paths.

**7. Test Oracle:**

- **Definition:** A test oracle is a mechanism or criterion used to determine whether the output of
a specific test case is correct. It serves as a reference or expected outcome against which the actual
output is compared during testing.

**8. Validation:**

- **Definition:** Validation is the process of evaluating a software system or component during or

at the end of the development process to ensure that it meets specified requirements and satisfies
the intended use.

**9. Error:**

- **Definition:** An error is a mistake or unintentional deviation from the intended behavior in a

software program. Errors can lead to defects and negatively impact the performance and
functionality of the software.

**10. Verification:**

- **Definition:** Verification is the process of evaluating whether a system or component meets

specified requirements and adheres to its specified design. It focuses on assessing the correctness
of the software at various stages of development.