Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

SQA > Klausurfragen > Flashcards

Klausurfragen Flashcards

(106 cards)

Start Studying
1
Q

Explain the static examination type “Review”

A

Review is process or meeting (+1) during which a work product or set of work products is presented (0.5) to project personnel, managers, users, customers or other interested parties (+1) for comment or approval

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Control flow based coverage

A

● Statement coverage
● Branch coverage
● Decision coverage
● Path coverage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Connection: Error

A

● Somebody makes a mistake.
● As a consequence the software contains a defect or fault
● When executing the program containing a defect an error may occur.
● An error may cause the failure of the whole system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Kinds of Error

A

● Functional Errors
● Configuration Errors
● Interface Errors
● Documentation Errors

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Kinds of metric

A

● Product metric

● Process metric

● Project metric

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

General Model Theory - Propertys

A
  1. Mapping property
  2. Reduction property
  3. Pragmatic property
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Definiton: Metric

A

A metric is the objective attribution of a number (or symbol) to an entity to characterize a specific attribute.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Sorting the scales

A

● Nominal Scale
Pure classification of values

● Ordinal Scale
Values are totally ordered

● Interval Scale
Captures information about the size of the intervals that separate the classification

● Rational Scale
Values are totally ordered and additive

● Absolut Scale
Values are absolute entities

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Kinds of Static Examnination of Software

A

● Measuring
● Conformance Check
● Review
● Inspection

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Metic: Granularity

A

● Base metric (simple, direct metric)
- Easy to measure, but hard to interpret

● Derived metric (pseudo, indirect metric)
- There is no direct metric or measurement is very

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Classification: Measurement Procedure metric

A

● Objective (precise) metric
- Measurement is done according to an exact procedure

● Subjective (estimated) metric
- The value is estimated, because it cannot be calculated.

● Calculated metric
- Values are determined based on a formula

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Classification: Purpose metric

A

● Prescriptive metric
- Characterizes the expected state

● Descriptive metric
- Characterizes the actual state

● Prognostic metric
- Creates a forecast, which can be
determined only later

● Diagnostic metric
- Characterizes the actual state.
● cyclomatic number

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Classification: Source of a Metric

A

● Model-based metric
- Combines directly measurable or estimated attributes according to a given formula

● Empirical metric
- Based on observations in the real world, without an underlying model.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Classification: Manipulation Metric

A

● Robust metric
- Returns results that can not be manipulated if the metric is known

● Undermineable metric
- Returns authentic results only if the application of
the metric is not known

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Quality Properties of Metrics = Metric for Readability

A

● Plausibility

● Relevance

● Profitability

● Comparability & Precision

● Availability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Goal-Question-Metric (GQM) - Advantages:

A

● Only relevant attributes are measured

● Interpretations are defined in the context of the respective goals

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

When is Mean Time Between Failure useful?

A

● errors are not corrected
● the kind and intensity of the usage remain the same
● the users do not provoke nor avoid the errors

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Quality Model

A

● The quality model is the cornerstone of a product or process quality evaluation system.
● Defines, which qualities are important and which are not important
● often forming a tree or graph

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

State machine

A

● A behavior model, consisting of a finite number of states

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Definition: State

A

Condition or situation in the life of a system during which it:
● satisfies some condition
● performs some activity, or
● waits for some events

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Events

A

Specification of a significant stimulus that has a location in time and space and can trigger a state transition:
● Signal event

● Call event

● Change Event

● Time event

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Transition

A

Relationship between two states

● where the source state will enter the target state

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Interaction Rule

A

Most failures are induced by single parameter faults or by interaction of two parameters, with progressively fewer failures induced by interactions between three or more parameters

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Combinatorial Testing

A

A black-box test selection technique in which test cases are generated to execute specific combinations of values of several input parameters

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Conflict Handling Strategies
A conflict is an irrelevant interaction of two or more parameter values. ``` Conflict handling strategies to exclude irrelevant interactions: ● Abstract Parameter ● Sub-Models ● Replacement ● Avoidance ```
26
Test First Development
1. Write a test for a new feature 2. Run all tests and see the new one fails 3. Write code for the new feature 4. Run the tests 5. Refactor code TDD = Test First Development + Refactoring
27
Test First Development - TDD Benefits
● Instant feedback ● Better development practices ● Improve quality assurance
28
Test First Development - TDD Limitation
● Hard to apply ● TDD needs an upfront design ● Difficult to write test cases for hard-to-test code
29
Path coverage in the activity graph
● Define (at least) one test case for each path through the activity graph
30
Benefits Use Case
● Use cases are considered to systematically design test cases ● Formalization (transformation to a state/ activity diagram) discovers missing information and errors early ● Drawbacks of natural language specifications are weakened
31
Test Driven Development
Test driven development (TDD) is an software development approach in which a test is written before writing the code. Once the new code passes the test, it is refactored to an acceptable standard.
32
Refactoring (TDD)
Refactoring consists of improving the internal structure of an existing program’s source code, while preserving its external behavior.
33
Diffetent types of steps provided by Gherkin
● Given: describe the initial context of the system ● When: describe an event or an action ● Then: describe an expected outcome or result
34
Explain why "Exhaustive Testing" is only feasible in rare cases?
● argumentation of too many test cases | ● for example/in-depth argument for too many test cases
35
Explain the concept of "Test Case Selection Criteria" - TCSC
A TCSC defines for a given program P implementing its specifications a set of conditions which the set of test cases has to meet
36
Practical criterion of Path Coverage
● limiting the number of traversals of loops | ● avoids the path explosion caused by loops
37
Test case design of Boundary Interior Coverage
● No loop execution ● One loop execution (boundary) ● At least two loop execution (interior)
38
Control flow base: Coverage
● Statement Coverage - weak criterion but not easy to achieve ● Branch coverage - minimal criterion in unit testing - inadequate for compound decisions ● Decision coverage - expensive but intensive ● Path coverage - more a theoretical option
39
Variants of Condition Coverage
● Basic Condition Coverage ● Branch and Condition Coverage ● Modified Condition Decision Coverage ● Compound Condition Coverage
40
Practical criterion of Path Coverage
● limiting the number of traversals of loops ● avoids the path explosion caused by loops
41
Examples for “linguistic effects”
● incomplete specified verbs, incomplete comparisons or nominalizations ● requirements that are of lesser value
42
NLP Classes
● Deletion ● Generalization ● Distortion
43
Requirements Examination Process
1. Examine individual words of a requirement sentence! 2. Examine each requirement sentence as a whole! 3. Examine the integration of a requirement in the overall specification!
44
Kinds of Quality Costs
1. Defect Prevention Costs 2. Examination and Inspection Costs 3. Error Costs
45
When do we stop testing?
1. We stop testing when the planned time is over | 2.
46
Test Exit Criteria
● Test Case Set ● Relative Defect Cost
47
Effectiveness of an Examination Strategy - Is influenced by
● effectiveness of the examination activities ● assumptions when defects can be detected ● the number of examined artifacts
48
Assessment of the impact of TDD
● Defect Rate ● Productivity ● Test Frequency ● Design
49
Range Error
There are plenty of test cases (out of a range) to discover the error! o A range error occurs in a certain part q of the input space o The application of n random selected test cases discovers the error with the probability
50
Why do we measure?
• Define measurable goals: Is the product maintainable and reliable? • Analyze important cost drivers in detail: Which part of the costs is caused by the system test? • Quantify important qualitative properties of product or processes: How high is the probability of failure? • Assess the efficiency of new technologies.
51
Key steps of Formal Measurements
1. Identify relevant attribute for real-world entities 2. Identify empirical relations for this attribute 3. Identify corresponding numerical relations 4. Define a mapping from real-world entities to numbers 5. Check that the representational condition holds
52
What can be measured?
``` Product qualities • robustness • usability • testability • efficiency ``` Process qualities • duration • effort • planning precision
53
GQM Steps
1. Defines goals that are relevant for the project 2. Deviate questions for Every goal 3. Define metrics to answer the questions
54
Types of quality models
* Quality prediction model: forecasts quality based on actual or historic measurement values * Quality definition model: describes the quality characteristics of a product or process * Quality assessment model: evaluate quality of a given product or process based on metrics
55
Used quality models:
* Mcall’s Quality Model * Boehm Quality Model * ISO 25010 (2011)
56
McCall's Quality Model – 1977
- Quality perspectives • the user’s point of view - Quality factors • represents a behavioral characteristic of software (manager POV) - Quality criteria • attributes of a quality factor related to software development
57
Boehm’s Quality Model
* Attempts to define software quality by giving a set of attributes * Also presents a hierarchical quality model structured in high-intermediate-basic level characteristics • High level attributes: o As-is Utility: how easy, reliable and efficient is the software o Maintainability: How easy it is to understand, modify and retest o Portability: Can I still use it if I change environment?
58
ISO 9126
• Former standard for the evaluation of the quality of software • Defines 6 quality factors with sub-factors, which overlap a minimum o Portability, Maintainability, Usability, Reliability, Functionality, Efficiency • How to measure a quality factor? o A quality factor has sub factors, which have metrics o The individual measured metrics are evaluated. If values are in the acceptable range, win x points; if not, win 0 points o The sum of points for each sub-factor gives the grade for it.
59
ISO 25010
• Defines 8 quality characteristics with sub-characteristics: o Portability, Maintainability, Usability, Reliability, Functional suitability, Performance efficiency, Compatibility, Security • This model is more comprehensive and complete
60
Maturity + Maturity model
Maturity • Measurement of the ability of an organization for continuous improvement in a particular discipline • The higher the maturity, the higher are the chances that errors are avoided Maturity model • Assesses qualitatively culture, processes/structures and technology • represents the maturity in a hierarchical structure
61
Quality Benchmark Levels
- Complete - Advanced - Extended - Basic - Rudimentary
62
Testing
Process of executing a program with the intent of finding errors
63
Testing Principles
1. Tests must be planned! 2. Start testing very early! 3. Testing is a creative and challenging task! 4. Testing requires independence! 5. Exhaustive testing is impossible! 6. Every test case needs a defined expected result! 7. A successful test case detects an unknown error! 8. The quality of a test depends on the quality of its test cases 9. Avoid throw-away test cases, except if you are developing a throw-away program!
64
Properties of Test Cases
● representative ● error sensitive ● low redundancy ● economical
65
Black vs Glass box tes
● Black-box test (functional test) - based on the specified characteristics ● Glass-box test (structural test) - based on the internal structure
66
Black Box
* Specification is the source for defining test cases * Comprehensive test of specified functionality. * Concrete implementation is not adequately considered. * Minimal requirements of glass-box test are not fulfilled by black-box test Coverage • Function coverage - Every specified function is executed at least once. • Input coverage - Every input value is used in at least in one test case • Output coverage - Every output situation is created at least once
67
Glass Box
• Test cases are selected based on the internal structure Coverage • Statement coverage • Branch coverage • Path coverage
68
WMC - Weighted Methods per Class
``` Total sum of the complexity of methods of a class WMC(c) = comp(m1) + comp(m2) + .. + comp(mn) ```
69
QA Measures
- Organizational Measures - Constructive Measures - Analytical Measures
70
Defect seeding vs Defect pooling
Seeding: ● Defects are explicitly seeded. ● The ratio between detected seeded defects and detected not-seeded defects is used to determine the original number of defects ``` Pooling: ● Detected defects are collected in at least two pools ● Scenario: - two independent testing teams - each has its own defect pool ```
71
Problem: Defect Seeding
Problem: ● Defect must be seeded homogeneously. ● Seeded defects must cover all defect types. ● Additional costs are to be expected.
72
Weak Robust Equivalence Class Test
Each representative value of all equivalence classes needs to be included in at least one test case. 1. For valid inputs, we use one value from each valid class 2. For invalid inputs, a test case has one invalid value and the remaining values will all be valid.
73
Strong Robust Equivalence Classes Test
A test case is created for every element of the Cartesian product of the equivalence classes, both valid and invalid
74
Replacement Conflict Handling
● Resolve conflicts after test generation 1. Clone test cases with conflicts 2. Conflicting values are changed arbitrarily ● Clones must preserve coverage criterion! ● Resolve one conflict at a time to ensure termination
75
Constructive Metric Development Steps
1. Identify a relevant quality aspect 2. Model the relevant quality aspect 3. Determine a scale 4. Develop the metric calculation 5. Develop measurement instructions 6. Apply and improve the metric
76
four steps of developing test cases
1. Identify Input Equivalence Classes 2: Identify Output Equivalence Classes 3. Check Function Coverage 4. Define boundary values
77
SCENT steps
1 → transform the use case description into an UML state diagram/activity diagram, 2 → transform the success scenario, 3 → transform the deviations, 4 → apply state transition testing/interpret the action graph
78
According to ISO 9126, maintainability is influenced by:
analyzability, changeability, stability, testability
79
Quality Benchmark Levels are determined by assessing
empirical comparison data
80
Higher maturity means
- Less chance of errors, - Predictability of dates, - cost and increased quality
81
ISO 25010 consists of how many main quality characteristics?
8
82
How many levels do exist in CMMI?
5
83
How many levels exist in QBL?
5
84
How many rules are there in Cognitive Complexity?
3
85
R. Martin‘s Package Metrics:
- Has 7 metrics, | - Is used to spot those Software packages which are hard to maintain
86
The Coupling metric/s used are:
- Efferent Coupling, - Ingoing dependencies, - Afferent Coupling, - Outgoing dependencies
87
Metric Suite by Chidamber & Kemerer:
- States the quality of object-oriented programs, | - Is based on six metrics
88
Weighted Methods per Class (WMC) is used to determine
- Total complexity of a the methods of a class, | - The difficulty to understand and maintain a class
89
A low LCOM value indicates...
- A high cohesion of the methods within a class, - The methods in the class largely work on the same data., - The class can not be meaningfully split up
90
Regression testing
- Is applied after making changes, | - Compares the results of the modified program with old results
91
For Glass-box testing testcases are selected on the basis of internal structure to analyze through:
- Data Flow, | - Control Flow
92
In BV Testing, the amount of boundary values that are selected for testing is
5
93
Worst Case BVT is useful, if :
- the interaction among two or more input variables is of concern, - a failure of the program is extremely costly
94
Give the amount of test cases generated for two input variables, for Worst Case BVT:
25
95
BVT requires the input variables to be
- Independent, | - Representing bounded properties
96
Give the amount of test cases generated for two input variables, for normal BVT:
9
97
Give the amount of test cases generated for two input variables, for Robustness BVT:
13
98
test case classification for Boundary value analysis
- specification-based selection, | - black-box testing, functional testing
99
There are three partitions: A with 6 elements, B with 4 elements and C with 3 elements. How many test cases are needed in weak normal equivalence class testing?
6
100
What happens during the step "Check Function Coverage"
- A Matrix is created mapping test cases to their tested functions, - Test cases are added, so that every function is tested by at least one test case
101
For Boundary Interior Coverage we design test cases with :
- no loop execution, - one loop execution, - at least two loop executions
102
Which roles participate in reviews?
- Moderator, - Minute Taker, - Author, - Reviewer
103
Reviews: Which rules exist?
- The review meeting is limited to two hours., - The moderator can cancel the meeting., - Every reviewer must present his/her findings., - No solutions are discussed.
104
What is the "third hour" during reviews used for?
- to to talk without rules/protocol, | - to talk about possible solutions
105
Static Examinations?
- Reviews, - Inspections, - Measuring, - Conformance Check
106
Static Examination are used to:
- Increase the quality of the examinee, - identify weaknesses in the development process, - check conformance to standards/guidelines

SQA (16 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions