Software Quality Assurance and Testing – Chapter 1 Flashcards

0.0(0)
studied byStudied by 1 person
GameKnowt Play
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/44

flashcard set

Earn XP

Description and Tags

A comprehensive set of question-and-answer flashcards covering definitions, concepts, models, and distinctions introduced in Chapter 1 of the Software Quality Assurance and Testing course.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

45 Terms

1
New cards

What is the IEEE definition of software?

Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system.

2
New cards

Name the four components of software.

1) Computer programs (code) 2) Procedures 3) Documentation 4) Data necessary for operating

3
New cards

Why are procedures necessary in software quality assurance?

They define the order, schedule, methods, and responsibilities for running programs, ensuring correct application of the software.

4
New cards

Identify the three primary types of documentation and their audiences.

• Development documentation – for developers • User documentation – for end-users • Maintenance documentation – for maintenance personnel

5
New cards

Why is data considered a necessary component for SQA?

It adapts software to specific users (parameters, codes, lists) and includes standard test data to detect unintended changes or malfunctions.

6
New cards

Besides code quality, what other component qualities must SQA always include?

Quality of procedures, documentation, and necessary data.

7
New cards

Define a software error/mistake.

A programmer-made error such as a syntax or logical mistake in the code.

8
New cards

Give two common categories of software errors.

Grammatical/syntax errors and logical errors that violate client requirements.

9
New cards

Define software fault/defect/bug.

Any non-conformance with the requirements specification found during testing.

10
New cards

What is a software failure?

An observed malfunction when the application runs in the customer’s environment, causing it not to work as expected.

11
New cards

Arrange the causal chain linking error, fault, and failure.

Error → Defect/Fault/Bug → Failure

12
New cards

Give two reasons a fault might never become a failure.

1) Faulty code is never executed by users. 2) Required conditions to activate the fault never occur.

13
New cards

List the nine common causes of software errors.

1) Faulty requirement definitions 2) Client–developer communication failures 3) Deliberate deviations 4) Logical design errors 5) Coding errors 6) Non-compliance with instructions 7) Testing shortcomings 8) Procedure errors 9) Documentation errors

14
New cards

State the IEEE definition of software quality (two parts).

1) Degree to which a system, component, or process meets specified requirements. 2) Degree to which it meets customer or user needs or expectations.

15
New cards

According to Crosby, what does quality mean?

Conformance to requirements.

16
New cards

According to Juran, what are the two aspects of quality?

(1) Features that meet customer needs and give satisfaction. (2) Freedom from deficiencies.

17
New cards

Give Pressman’s three requirements for software quality assurance.

Conformance to: 1) Explicit functional & performance requirements, 2) Documented development standards, 3) Implicit professional (state-of-the-art) characteristics.

18
New cards

Provide the IEEE definition of software quality assurance.

A planned and systematic pattern of all actions necessary to provide adequate confidence that a product conforms to established technical requirements and to evaluate the process by which it is developed.

19
New cards

How does the expanded SQA definition extend the IEEE’s?

Adds coverage of maintenance, schedule adherence, and budget constraints.

20
New cards

Differentiate QA from QC in terms of orientation.

QA is process-oriented; QC is product-oriented.

21
New cards

Which activity is preventive and which is corrective: QA or QC?

QA is preventive; QC is corrective.

22
New cards

Regarding verification vs. validation, which corresponds to QA and which to QC?

QA = verification (doing the right things in the right way); QC = validation (checking the product meets requirements).

23
New cards

According to IEEE 1991, what is software engineering?

The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software.

24
New cards

How many quality factors are in McCall’s model?

11 software quality factors.

25
New cards

List McCall’s product operation factors.

Correctness, Reliability, Efficiency, Integrity, Usability.

26
New cards

List McCall’s product revision factors.

Maintainability, Flexibility, Testability.

27
New cards

List McCall’s product transition factors.

Portability, Reusability, Interoperability.

28
New cards

What does the correctness factor focus on?

Accuracy, completeness, timeliness, availability, and standards of the software outputs.

29
New cards

What metric do reliability requirements typically specify?

Maximum allowed failure rate for the system or its functions.

30
New cards

Which resources are considered under efficiency requirements?

Processing power, memory/disk capacity, communication bandwidth, and sometimes power consumption between recharges.

31
New cards

What is meant by integrity in software quality?

Security measures that prevent unauthorized access and distinguish read and write permissions.

32
New cards

Define usability in the context of software quality.

The staff resources and training time needed to learn and operate the system effectively.

33
New cards

What is maintainability?

The effort required to locate, fix, and verify corrections of software failures.

34
New cards

What is flexibility?

The effort and resources needed to adapt or enhance software for new customers, environments, or requirements.

35
New cards

Define testability.

The ease of testing a system, including built-in diagnostics, logs, and standard test data.

36
New cards

Define portability.

The ability to transfer software to different hardware, operating systems, or environments at low cost.

37
New cards

Define reusability.

The capability to use existing software modules in new projects, saving time and improving quality.

38
New cards

Define interoperability.

The capacity of software to interface and exchange data with other systems or equipment firmware.

39
New cards

Which quality factors are usually of greater interest to developers than to clients?

Portability, Reusability, and Verifiability/Testability.

40
New cards

Name three key features of the SQA environment highlighted in the lecture.

1) Projects must work in teams and coordinate with other teams. 2) Software must interface with other systems. 3) Maintenance must continue for many years even as teams change.

41
New cards

Summarize the difference between QA focus and QC focus.

QA improves development processes to prevent errors; QC improves the product by detecting and correcting defects.

42
New cards

In the chapter summary, what four software components are always included in SQA?

Code, procedures, documentation, and necessary data.

43
New cards

What is the main objective of SQA?

To provide confidence that the software process and product conform to technical, functional, schedule, and budget requirements.

44
New cards

What two categories of decisions shape an organization’s SQA system?

(a) The SQA organizational base; (b) The components to be implemented and their extent of use.

45
New cards

Give three contexts outside professional development where SQA is still needed.

Software created by students, hobbyists, or non-software professionals to support their work.