Foundation Level 3

Question 1

Static testing

Answer 1

1. the software under test does not need to be executed
2. Code, process specification, system architecture specification or other work products are evaluated through manual examination
3. with the help of a tool

Question 2

Static testing objectives

Answer 2

1. improving quality
2. detecting defects
3. assessing characteristics like readability, completeness, correctness, testability and consistency

Question 3

Work Products Examinable by Static Testing

Answer 3

1. Any work product that can be read and understood can be the subject of a review.
2. work products need a structure against which they can be checked

Question 4

Work products that are not appropriate for static testing

Answer 4

are difficult to interpret by human beings and that should not be analyzed by tools (e.g., 3rd party executable code due to legal reasons).

Question 5

Value of Static Testing

Answer 5

1. detect defects in the earliest phases of the SDLC
2. identify defects which cannot be detected by dynamic testing (e.g., unreachable code, design patterns not implemented as desired, defects in non-executable work products).
3. Communication will also be improved between the involved stakeholders
4. Code defects can be detected using static analysis more efficiently than in dynamic testing

Question 6

Differences between Static Testing and Dynamic Testing

Answer 6

1. there are some defect types that can only be found by either static or dynamic testing.
2. Static testing finds defects directly, while dynamic testing causes failures from which the associated defects are determined through subsequent analysis
3. Static testing may more easily detect defects that lay on paths through the code that are rarely executed or hard to reach using dynamic testing
4. Static testing can be applied to non-executable work products,
5. Static testing can be used to measure quality characteristics that are not dependent on executing code

Question 7

Typical defects that are easier and/or cheaper to find through static testing

Answer 7

1. Defects in requirements (e.g., inconsistencies, ambiguities, contradictions, omissions, inaccuracies, duplications)
2. Design defects
3. Certain types of coding defects
4. Deviations from standards
5. Incorrect interface specifications
6. Specific types of security vulnerabilities
7. Gaps or inaccuracies in test basis coverage

Question 8

Success Factors for Reviews

Answer 8

1. Defining clear objectives and measurable exit criteria.
2. Choosing the appropriate review type to achieve the given objectives, and to suit the type of work product, the review participants, the project needs and context
3. Conducting reviews on small chunks, so that reviewers do not lose concentration during an individual review and/or the review meeting
4. Providing feedback from reviews to stakeholders and authors so they can improve the product and their activities
5. Providing adequate time to participants to prepare for the review
6. Support from management for the review process
7. Making reviews part of the organization’s culture, to promote learning and process improvement
8. Providing adequate training for all participants so they know how to fulfil their role
9. Facilitating meetings

Question 9

Review types

Answer 9

1. Informal review
2. Walkthrough
3. Technical Review
4. Inspection

Selecting the right review type is key to achieving the required review objectives

Question 10

Informal review

Answer 10

do not follow a defined process and do not require a formal documented output. The main objective is detecting anomalies.

Question 11

Walkthrough

Answer 11

can serve many objectives, such as evaluating quality and building confidence in the work product, educating reviewers, gaining consensus, generating new ideas, motivating and enabling authors to improve and detecting anomalies

Question 12

Technical Review

Answer 12

1. performed by technically qualified reviewers and led by a moderator
2. objectives of a technical review are to gain consensus and make decisions regarding a technical problem, but also to detect anomalies, evaluate quality and build confidence in the work product, generate new ideas, and to motivate and enable authors to improve

Question 13

Inspection

Answer 13

find the maximum number of anomalies. Other objectives are to evaluate quality, build confidence in the work product, and to motivate and enable authors to improve. Metrics are collected and used to improve the SDLC, including the inspection process.

Question 14

Roles and Responsibilities in Reviews

Answer 14

1. Manager
2. Author
3. Moderator
4. Scribe
5. Reviewer
6. Review leader

Question 15

Manager Role

Answer 15

1. decides what is to be reviewed
2. provides resources, such as staff and time for the review

Question 16

Author role

Answer 16

creates and fixes the work product under review

Question 17

Review leader role

Answer 17

takes overall responsibility for the review such as deciding who will be involved, and organizing when and where the review will take place

Question 18

Review Process Activities

Answer 18

1. Planning
2. Review initiation
3. Individual review
4. Communication and analysis
5. Fixing and reporting

NB: f the required review is more formal, then more of the tasks described for the different activities will be needed.

Question 19

Planning stage defines

Answer 19

the scope of the review, which comprises the purpose, the work product to be reviewed, quality characteristics to be evaluated, areas to focus on, exit criteria, supporting information such as standards, effort and the timeframes for the review

Question 20

Review initiation

Answer 20

1. goal is to make sure that everyone and everything involved is prepared to start the review

making sure that every participant has access to the work product under review, understands their role and responsibilities and receives everything needed to perform the review.

Question 21

Individual review

Answer 21

Every reviewer performs an individual review to assess the quality of the work product under review, and to identify anomalies, recommendations, and questions by applying one or more review techniques (e.g., checklist-based reviewing, scenario-based reviewing). The ISO/IEC 20246 standard provides more depth on different review techniques. The reviewers log all their identified anomalies, recommendations, and questions.

Question 22

Communication and analysis

Answer 22

1. anomalies identified during a review are not necessarily defects => discuss
2. the decision should be made on its status, ownership and required actions.

Question 23

Fixing and reporting

Answer 23

for every defect, a defect report should be created so that corrective actions can be followed-up. Once the exit criteria are reached, the work product can be accepted. The review results are reported.