September 2006 Aberdeen Global IT Team ISTQB CTFL Study Session Section 3
Overview <ul><li>Introductions </li></ul><ul><li>Review of Section 3 Practice Quiz </li></ul><ul><li>Open Forum </li></ul>
Introductions <ul><li>Name </li></ul><ul><li>Tenure With Firm </li></ul><ul><li>Primary Job Function(s) </li></ul><ul><li>...
1. The objective for any review meeting is to solve problems with the design? <ul><ul><li>a. True </li></ul></ul><ul><ul><...
2. Which is  not  a role of the facilitator during a review meeting? <ul><ul><li>a. Running the review meeting </li></ul><...
3. Which of the following is an example of static testing: <ul><ul><li>Black box testing </li></ul></ul><ul><ul><li>Struct...
4. Defects detected while testing are more costly to remove than those detected during reviews early in the life cycle. <u...
5. Which of the following is not a task during the planning phase of a formal review:  <ul><ul><ul><li>Select the personne...
6. Which of the following is a form of static testing: <ul><ul><li>a. Appraisal </li></ul></ul><ul><ul><li>b. Walkthrough ...
7.  Desk Checking defines a process where someone reads the program carefully and analyzes its behavior without running te...
8. The transformation of information – either through parameters or a stored database – from one component of a system to ...
9. Which of the items listed below is  not  a benefit of software reviews: <ul><ul><ul><ul><li>Development productivity im...
10. During _______, the designer simulates the program, showing step by step what the program will do with test data suppl...
11. The main purpose of  _______ is to learn, gain understanding, and find defects. <ul><ul><ul><li>Inspections </li></ul>...
12. The main purpose of  _________ is to make decisions, evaluate alternatives, find defects, solve technical problems and...
13. What is the Cyclomatic Complexity of the code below: <ul><ul><ul><li>3 </li></ul></ul></ul><ul><ul><ul><li>4 </li></ul...
14. _________ identifies how the program transitions from one state to another.  <ul><ul><ul><ul><li>Data Flow </li></ul><...
15. In an ideal review meeting, the following individual(s) do not make comments on design documentation. <ul><ul><ul><ul>...
16. Review, Static Analysis, and Dynamic testing have the same objective – Identifying defects.  <ul><ul><li>a. True </li>...
17. During ______, reviewers check every line of the design against each item in a checklist. <ul><ul><ul><li>Inspections ...
18. Which of the following types of defects are easier to find in reviews than in dynamic testing (select all that apply):...
19. Which is  not  a success factor for reviews: <ul><ul><ul><ul><li>Each review has a clear predefined objective. </li></...
20. Static analysis tools are typically used by developers (checking against predefined rules or programming standards) be...
Open Forum
Upcoming SlideShare
Loading in …5
×

Section 3 Answers & Presentation

2,358
-1

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,358
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
140
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Section 3 Answers & Presentation

  1. 1. September 2006 Aberdeen Global IT Team ISTQB CTFL Study Session Section 3
  2. 2. Overview <ul><li>Introductions </li></ul><ul><li>Review of Section 3 Practice Quiz </li></ul><ul><li>Open Forum </li></ul>
  3. 3. Introductions <ul><li>Name </li></ul><ul><li>Tenure With Firm </li></ul><ul><li>Primary Job Function(s) </li></ul><ul><li>Testing Tools Used </li></ul>
  4. 4. 1. The objective for any review meeting is to solve problems with the design? <ul><ul><li>a. True </li></ul></ul><ul><ul><li>b. False </li></ul></ul><ul><ul><li>b. False </li></ul></ul><ul><ul><li>Testing Computer Software p.39 Syllabus Section 3.1 </li></ul></ul><ul><ul><li>“The objective for any review meeting is to identify problems with the design”. </li></ul></ul>
  5. 5. 2. Which is not a role of the facilitator during a review meeting? <ul><ul><li>a. Running the review meeting </li></ul></ul><ul><ul><li>b. Stopping Interruptions </li></ul></ul><ul><ul><li>c. Commenting on the design documentation </li></ul></ul><ul><ul><li>d. Keeping the discussion focused </li></ul></ul><ul><ul><li>e. Preparing a summary report. </li></ul></ul><ul><ul><li>c. Commenting on the design documentation </li></ul></ul><ul><ul><li>Testing Computer Software p.40 Syllabus Section 3.2.2 </li></ul></ul>
  6. 6. 3. Which of the following is an example of static testing: <ul><ul><li>Black box testing </li></ul></ul><ul><ul><li>Structural testing </li></ul></ul><ul><ul><li>Path testing </li></ul></ul><ul><ul><li>Glass box testing </li></ul></ul><ul><ul><li>None of the above </li></ul></ul><ul><ul><li>e. None of the above </li></ul></ul><ul><ul><li>Testing Computer Software p.46 Syllabus Section 3.1 </li></ul></ul><ul><ul><li>“In static testing, the code is examined. It is tested without being executed.” </li></ul></ul>
  7. 7. 4. Defects detected while testing are more costly to remove than those detected during reviews early in the life cycle. <ul><ul><ul><li>True </li></ul></ul></ul><ul><ul><ul><li>False </li></ul></ul></ul><ul><ul><li>a. True </li></ul></ul><ul><ul><li>CTFL Syllabus p.28, Syllabus Section 3.1 </li></ul></ul><ul><ul><li>“Defects detected during reviews early in the life cycle are often much cheaper to remove than those detected while running tests” </li></ul></ul>
  8. 8. 5. Which of the following is not a task during the planning phase of a formal review: <ul><ul><ul><li>Select the personnel </li></ul></ul></ul><ul><ul><ul><li>Allocate roles </li></ul></ul></ul><ul><ul><ul><li>Select which parts of documents to look at </li></ul></ul></ul><ul><ul><ul><li>Distribute Documentation </li></ul></ul></ul><ul><ul><ul><li>Define the entry and exit criteria </li></ul></ul></ul><ul><ul><li>d. Distribute Documentation </li></ul></ul><ul><ul><li>CTFL Syllabus p.28, Syllabus Section 3.1 </li></ul></ul><ul><ul><li>“Planning: selecting the personnel, allocating roles; defining the entry and exit criteria for more formal review types (e.g. inspection); and selecting which parts of documents to look at.” </li></ul></ul>
  9. 9. 6. Which of the following is a form of static testing: <ul><ul><li>a. Appraisal </li></ul></ul><ul><ul><li>b. Walkthrough </li></ul></ul><ul><ul><li>c. Assessment </li></ul></ul><ul><ul><li>d. Gap Analysis </li></ul></ul><ul><ul><li>b. Walkthrough </li></ul></ul><ul><ul><li>Tata Consulting – Learning and Development tutorial, Section 3 </li></ul></ul><ul><ul><li>“ IEEE classifies Static Testing under three broad categories: </li></ul></ul><ul><ul><li>Reviews </li></ul></ul><ul><ul><li>Walkthroughs </li></ul></ul><ul><ul><li>Inspections “ </li></ul></ul>
  10. 10. 7. Desk Checking defines a process where someone reads the program carefully and analyzes its behavior without running test cases at the computer. <ul><ul><li>a. True </li></ul></ul><ul><ul><li>b. False </li></ul></ul><ul><ul><li>a. True </li></ul></ul><ul><ul><li>Testing Computer Software p.47 Syllabus Section 3.1 </li></ul></ul>
  11. 11. 8. The transformation of information – either through parameters or a stored database – from one component of a system to another is: <ul><ul><ul><ul><li>Data Flow </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Internal Flow </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Control Flow </li></ul></ul></ul></ul><ul><ul><ul><ul><li>None of the above </li></ul></ul></ul></ul><ul><ul><li>a. Data Flow </li></ul></ul><ul><ul><li>Managing the Testing Process p.14 Syllabus Section 3.3 </li></ul></ul>
  12. 12. 9. Which of the items listed below is not a benefit of software reviews: <ul><ul><ul><ul><li>Development productivity improvements </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Reduced development timescales </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Reduced testing cost and time </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Lifetime cost reductions </li></ul></ul></ul></ul><ul><ul><ul><ul><li>None of the above </li></ul></ul></ul></ul><ul><ul><ul><ul><li>e. None of the above </li></ul></ul></ul></ul><ul><ul><ul><ul><li>CTFL Syllabus p.28 Syllabus Section 3.1 </li></ul></ul></ul></ul><ul><ul><li>“Benefits of reviews include early defect detection and correction, development productivity improvements, reduced development timescales, reduced testing cost and time, lifetime cost reductions, fewer defects and improved communication.” </li></ul></ul>
  13. 13. 10. During _______, the designer simulates the program, showing step by step what the program will do with test data supplied by the reviewers. <ul><ul><ul><li>Inspections </li></ul></ul></ul><ul><ul><ul><li>Walkthroughs </li></ul></ul></ul><ul><ul><ul><li>Reviews </li></ul></ul></ul><ul><ul><ul><li>None of the above </li></ul></ul></ul><ul><ul><li>b. Walkthroughs </li></ul></ul><ul><ul><li>Testing Computer Software p.39 Syllabus Section 3.2.3 </li></ul></ul>
  14. 14. 11. The main purpose of _______ is to learn, gain understanding, and find defects. <ul><ul><ul><li>Inspections </li></ul></ul></ul><ul><ul><ul><li>Walkthroughs </li></ul></ul></ul><ul><ul><ul><li>Reviews </li></ul></ul></ul><ul><ul><ul><li>None of the above </li></ul></ul></ul><ul><ul><li>b. Walkthroughs </li></ul></ul><ul><ul><li>CTFL Syllabus p.30, Syllabus Section 3.2.3 </li></ul></ul>
  15. 15. 12. The main purpose of _________ is to make decisions, evaluate alternatives, find defects, solve technical problems and check conformance to specifications and standards. <ul><ul><ul><li>Inspections </li></ul></ul></ul><ul><ul><ul><li>Walkthroughs </li></ul></ul></ul><ul><ul><ul><li>Reviews </li></ul></ul></ul><ul><ul><ul><li>None of the above </li></ul></ul></ul><ul><ul><li>c. Reviews </li></ul></ul><ul><ul><li>CTFL Syllabus p.30, Syllabus Section 3.2.3 </li></ul></ul>
  16. 16. 13. What is the Cyclomatic Complexity of the code below: <ul><ul><ul><li>3 </li></ul></ul></ul><ul><ul><ul><li>4 </li></ul></ul></ul><ul><ul><ul><li>5 </li></ul></ul></ul><ul><ul><ul><li>6 </li></ul></ul></ul><ul><ul><ul><li>c.5 </li></ul></ul></ul><ul><ul><ul><li>Cyclomatic Code Complexity Analysis for Microsoft .NET Applications , Syllabus Section 3.3 </li></ul></ul></ul><ul><ul><ul><ul><li>public void ProcessPages() </li></ul></ul></ul></ul><ul><ul><ul><ul><li>{ </li></ul></ul></ul></ul><ul><ul><ul><ul><li>while(nextPage !=true) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>{ </li></ul></ul></ul></ul><ul><ul><ul><ul><li>if((lineCount<=linesPerPage) && (status != Status.Cancelled) && (morePages == true)) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>{ </li></ul></ul></ul></ul><ul><ul><ul><ul><li>//.... </li></ul></ul></ul></ul><ul><ul><ul><ul><li>} </li></ul></ul></ul></ul><ul><ul><ul><ul><li>} </li></ul></ul></ul></ul><ul><ul><ul><ul><li>} </li></ul></ul></ul></ul>
  17. 17. 14. _________ identifies how the program transitions from one state to another. <ul><ul><ul><ul><li>Data Flow </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Internal Flow </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Control Flow </li></ul></ul></ul></ul><ul><ul><ul><ul><li>None of the above </li></ul></ul></ul></ul><ul><ul><li>c. Control Flow </li></ul></ul><ul><ul><li>Testing Computer Software p.212 Syllabus Section 3.3 </li></ul></ul><ul><ul><li>“When you ask about control flow, your asking how to get the program from one state to another.” </li></ul></ul>
  18. 18. 15. In an ideal review meeting, the following individual(s) do not make comments on design documentation. <ul><ul><ul><ul><li>Author </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Scribe </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Facilitator </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Reviewer </li></ul></ul></ul></ul><ul><ul><li>b & c. Scribe & Moderator </li></ul></ul><ul><ul><li>Testing Computer Software p.40 Syllabus Section 3.2.2 </li></ul></ul><ul><ul><li>“The ideal review meeting is administered by a meeting manager (facilitator) and a recorder. Neither comments on the design. </li></ul></ul>
  19. 19. 16. Review, Static Analysis, and Dynamic testing have the same objective – Identifying defects. <ul><ul><li>a. True </li></ul></ul><ul><ul><li>b. False </li></ul></ul><ul><ul><li>a. True </li></ul></ul><ul><ul><li>CTFL Syllabus p.28, Syllabus Section 3.1 </li></ul></ul>
  20. 20. 17. During ______, reviewers check every line of the design against each item in a checklist. <ul><ul><ul><li>Inspections </li></ul></ul></ul><ul><ul><ul><li>Walkthroughs </li></ul></ul></ul><ul><ul><ul><li>Reviews </li></ul></ul></ul><ul><ul><ul><li>None of the above </li></ul></ul></ul><ul><ul><li>a. Inspections </li></ul></ul><ul><ul><li>Testing Computer Software p.40 Syllabus Section 3.2.3 </li></ul></ul>
  21. 21. 18. Which of the following types of defects are easier to find in reviews than in dynamic testing (select all that apply): <ul><ul><ul><ul><li>deviations from standards </li></ul></ul></ul></ul><ul><ul><ul><ul><li>requirement defects </li></ul></ul></ul></ul><ul><ul><ul><ul><li>design defects </li></ul></ul></ul></ul><ul><ul><ul><ul><li>None of the above </li></ul></ul></ul></ul><ul><ul><li>a. deviations from standards, b. requirement defects, & c. design defects </li></ul></ul><ul><ul><li>Testing Computer Software p.350 Syllabus Section 1.5 </li></ul></ul><ul><ul><li>“Typical defects that are easier to find in reviews than in dynamic testing are: deviations from standards, requirement defects, design defects, insufficient maintainability and incorrect interface specifications.” </li></ul></ul>
  22. 22. 19. Which is not a success factor for reviews: <ul><ul><ul><ul><li>Each review has a clear predefined objective. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>The right people for the review objectives are involved. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Authors are held accountable for design mistakes. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Defects found are welcomed, and expressed objectively. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>None of the above </li></ul></ul></ul></ul><ul><ul><ul><ul><li>c. Authors are held accountable for design mistakes. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>CTFL Syllabus p.30 Syllabus Section 3.2.4 </li></ul></ul></ul></ul>
  23. 23. 20. Static analysis tools are typically used by developers (checking against predefined rules or programming standards) before and during component and integration testing, and by designers during software modeling. <ul><ul><ul><ul><li>True </li></ul></ul></ul></ul><ul><ul><ul><ul><li>False </li></ul></ul></ul></ul><ul><ul><ul><ul><li>True </li></ul></ul></ul></ul><ul><ul><li>CTFL Syllabus p.32 Syllabus Section 3.3 </li></ul></ul>
  24. 24. Open Forum
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×