• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/12

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

12 Cards in this Set

  • Front
  • Back

Which of the following artifacts can be examined by using review techniques?

A. Software code
B. Requirements specification
C. Test design
D. All of the above

D. Software code, requirements specification and test design.

A static analysis tool gives quality information about the code without executing it.

A. True
B. False

A. True

Which is not a type of review?

A. Walkthrough
B. Inspection


C. Informal review
D. Management approval

D. Management approval

What statement about reviews is true?

A. Inspections are led by a trained moderator, whereas technical reviews are not necessarily.
B. technical reviews are led by a trained leader, inspections are not.
C. In a walkthrough, the author does not attend.
D. Participants for a walkthrough always need to be thoroughly trained.

A. Inspections are eld by a trained moderator, whereas technical reviews are not necessarily.

What is the main difference between a walkthrough and an inspection?

A. An inspection is led by the authors, whilst a walkthrough is led by a trained moderator.
B. An inspection has a trained leader, whilst a walkthrough has no leader.
C. Authors are no present during inspections, whilst they ate during walkthroughs.
D. A walkthrough is led by the author, whilst an inspection is led by a trained moderator.

D. A walkthrough is led by the author, whilst an inspection is led by a trained moderator.

What statement about static analysis is true?

A. With static analysis, defects can be found that are difficult to find with dynamic testing.
B. Compiling is not form of static analysis.
C. When properly performed, static analysis makes functional testing redundant.
D. Static analysis find all faults.

A. With static analysis, defects can be found that are difficult to find with dynamic testing.

Which of the following statements about early test design are true and which are false?

1. Defects found during early test design are more expensive to fix.
2. Early test design can find defects.
3. early test design can cause changes to the requirements.
4. Early takes design takes more effort.

2 is true, rest is false.

Static code analysis typically identifies all but one of the following problems. Which is it?

A. Unreachable code
B. Undeclared variables
C. Faults in the requirements
D. Too few comments

C. Fault in the requirements

The _______ of a review process is related to the following factors.

- the maturity of the development process.
- any legal requirements for the software product/project.
- the need for an audit trail.

Formality / Degree of formality

The formality of a review process is related to the following factors.

Pair the following review activities with their description:

1. Planning
2. Kick-off
3. Individual preparation
4. review meeting
5. Rework
6. Follow-up

A. The moderator distributes to all the participant the documents to be reviewed.


B. Each participant reads their part of document and notes the detects found.
C. The author of the reviewed doc fixes the defects found and reported in the review meeting.
D. A moderator selects who is going to attend the review activity and assigns roles in the review process.
E. The moderator checks if the defects have been indeed fixed.
F. Meeting in which each participants lists the defects they found. The author takes noted. The moderator moderated the discussion.

1 -> D


2 -> A


3 -> B


4 -> F


5 -> C


6 -> E

Why do you think it is important to have clean code? Why is it important to keep it clean?

???

Do you think its good to impose coding conventions to a team? (naming conventions, tabs, complexity of methods, interfaces, API, etc.)

???