sdsdsdsdsdsdsdssdssd

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/47

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

48 Terms

1
New cards

Software Quality Assurance

A set of activities ensuring the software development process and its products meet established quality standards.

2
New cards

Software Quality

The degree to which a software product meets the gathered requirements.

3
New cards

Defect Prevention, Detection, and Removal

Core activities of software quality assurance aimed at improving software quality.

4
New cards

Software Review and Inspection

A structured peer-review process used to detect and correct defects in software artifacts.

5
New cards

Software Artifacts

Documented items from the software development process like requirements, code, documentation, test plans.

6
New cards

Fagan Inspection Methodology

A formal software inspection process developed by Michael Fagan, focusing on error detection and process improvement.

7
New cards

Moderator (Fagan)

Leads the inspection team and handles logistics.

8
New cards

Author (Fagan)

Creator of the artifact being inspected, responsible for defect fixes.

9
New cards

Reader (Fagan)

Experienced peer who understands the artifact.

10
New cards

Tester (Fagan)

Writes and executes test cases, focuses on product testing.

11
New cards

Planning (Fagan Activity)

Identify roles, verify materials, distribute materials, arrange meetings.

12
New cards

Overview (Fagan Activity)

Author briefs participants on the artifact.

13
New cards

Preparation (Fagan Activity)

Inspectors prepare, read deliverables, use checklists, mark issues.

14
New cards

Inspection Meeting (Fagan Activity)

Inspectors identify defects, record/classify them, agree on outcomes.

15
New cards

Rework (Fagan Activity)

Author corrects defects and investigates issues.

16
New cards

Follow-up (Fagan Activity)

Moderator checks if defects have been resolved.

17
New cards

Process Improvement (Fagan Activity)

Root cause analysis, recommendations for process improvement.

18
New cards

Requirements Inspection

Finds requirement defects, confirms correctness of requirements.

19
New cards

Design Inspection

Finds design defects, ensures design matches requirements.

20
New cards

Code Inspection

Finds code defects, ensures code matches design/requirements.

21
New cards

Test Plan Inspection

Finds defects in test plans, ensures test cases verify design/requirements.

22
New cards

Structured Walkthrough

Peer review where the author presents a document or code to reviewers for feedback.

23
New cards

Review Leader (Walkthrough)

Chairs the walkthrough meeting.

24
New cards

Scribe (Walkthrough)

Records errors, decisions, and actions during the meeting.

25
New cards

Walkthrough Step 1

Author circulates the deliverable.

26
New cards

Walkthrough Step 2

Author schedules a meeting.

27
New cards

Walkthrough Step 3

Reviewers read the deliverable.

28
New cards

Walkthrough Step 4

Review leader leads the meeting.

29
New cards

Walkthrough Step 5

Author explains the deliverable and requests feedback.

30
New cards

Walkthrough Step 6

Scribe records observations.

31
New cards

Walkthrough Step 7

Outcome is agreed and revisions made.

32
New cards

Walkthrough Step 8

Deliverable is re-circulated for sign-off.

33
New cards

Walkthrough Step 9

Author stores comments and sign-offs.

34
New cards

Code Review

Systematic check of code to ensure it meets standards and is free of defects.

35
New cards

Tool-Driven Code Review

Uses automated tools/IDEs to find code issues.

36
New cards

Developer-Driven Code Review

Developers manually review code to find hard-to-detect quality issues.

37
New cards

Modern Code Review

Lightweight, tool-based review process that doesn’t require face-to-face meetings.

38
New cards

Repository-Based Review Tools

Tools like Gerrit or CodeFlow integrated with version control for code review.

39
New cards

Pull-Based Development

Uses pull requests for code review and integration by authorized developers.

40
New cards

Technical Debt

The cost of additional rework caused by choosing an easy or limited solution now instead of using a better approach.

41
New cards

Prototyping

Building a software model to test and clarify requirements early in the development process.

42
New cards

Throwaway Prototyping

Fast prototypes discarded after feedback, used in early stages.

43
New cards

Evolutionary Prototyping

Prototypes evolve into the final product, used in later stages.

44
New cards

Low-Fidelity Prototyping

Simple, rough design (e.g., paper-based) to test layout and flows.

45
New cards

Paper-Based Prototyping

Hand-drawn UI mockups to explore and refine ideas.

46
New cards

Wireframing

Visual representation of UI structure

47
New cards

Wireframing Tools

Balsamiq, Axure, MockFlow, Adobe XD.

48
New cards

High-Fidelity Prototyping

Detailed, functional prototypes using actual code and tools.