Software Inspection Checklist
18 Questions
6 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

Which of the following is NOT one of the Seven Basic Tools of Quality?

  • Scatter Diagram
  • Flowchart
  • Gantt Chart (correct)
  • Run Chart
  • What is the main purpose of a control chart?

  • To detect defects in a process
  • To prioritize problem areas
  • To prevent defects in a process (correct)
  • To analyze the flow of a process
  • Which tool is used to collect and analyze data?

  • Scatter diagram
  • Flowchart
  • Histogram
  • Checksheet (correct)
  • What is the purpose of a Pareto chart?

    <p>To identify and prioritize problem areas</p> Signup and view all the answers

    Which of the following is used to find the root cause of a problem?

    <p>Cause-and-Effect Diagram</p> Signup and view all the answers

    What is the purpose of the Seven Run Rule in quality control charts?

    <p>To identify patterns in data</p> Signup and view all the answers

    Which of the following is NOT a check for data faults according to the inspection checklist?

    <p>Checking if formal and actual parameter types match</p> Signup and view all the answers

    Which of the following is a check for control faults according to the inspection checklist?

    <p>Verifying that each loop is certain to terminate</p> Signup and view all the answers

    If character strings are used in a program, what should be explicitly assigned according to the data faults checklist?

    <p>A delimiter</p> Signup and view all the answers

    Which of the following is a check for interface faults according to the inspection checklist?

    <p>Verifying that all function and method calls have the correct number of parameters</p> Signup and view all the answers

    According to the inspection checklist, what should be checked for input/output faults?

    <p>If all input variables are used and all output variables are assigned a value before output</p> Signup and view all the answers

    Which of the following is NOT a check listed in the inspection checklist?

    <p>Ensuring that all function and method calls have the correct parameter order</p> Signup and view all the answers

    Which of the following is NOT a type of software fault?

    <p>Inspection checklist fault</p> Signup and view all the answers

    What is the primary purpose of program inspections?

    <p>To examine the source code for anomalies and defects before implementation</p> Signup and view all the answers

    Which of the following statements about inspection checklists is TRUE?

    <p>A checklist of common errors should be used to guide the inspection process</p> Signup and view all the answers

    What is the primary reason why testing alone is not sufficient for preventing software defects?

    <p>Testing only identifies faults in the implemented code, not in the design or requirements</p> Signup and view all the answers

    Which of the following is a goal of quality assurance?

    <p>Continuous quality improvement</p> Signup and view all the answers

    What type of software fault is most likely to be identified during program inspections?

    <p>Control faults</p> Signup and view all the answers

    Study Notes

    Quality Control and Assurance

    • The main outputs of quality control are: acceptance decisions, rework, and process adjustments.

    Seven Basic Tools of Quality

    • Flowcharts: graphic displays of process logic and flow, used to analyze problem occurrence and process improvement.
    • Run Charts: display the history and pattern of variation of a process over time.
    • Scatter Diagrams: show the relationship between two variables.
    • Histograms: bar graphs of a distribution of variables.
    • Pareto Charts: histograms that help identify and prioritize problem areas.
    • Control Charts: graphic displays of data that illustrate process results over time, used to prevent defects.
    • Cause-and-Effect Diagrams: aka fishbone or Ishikawa diagrams, used to find the root cause of a problem.

    Inspection Checklists

    • Data faults:
      • Are all program variables initialized before their values are used?
      • Have all constants been named?
      • Should the upper bound of arrays be equal to the size of the array or Size -1?
      • Is a delimiter explicitly assigned for character strings?
      • Is there any possibility of buffer overflow?
    • Control faults:
      • Is the condition correct for each conditional statement?
      • Is each loop certain to terminate?
      • Are compound statements correctly bracketed?
      • Are all possible cases accounted for in case statements?
      • Is a break included after each case in case statements?
    • Input/output faults:
      • Are all input variables used?
      • Are all output variables assigned a value before they are output?
      • Can unexpected inputs cause corruption?
    • Interface faults:
      • Do all function and method calls have the correct number of parameters?
      • Do formal and actual parameter types match?
      • Are the parameters in the right order?
    • Storage faults management:
      • If components access shared memory, do they have the same model of the shared memory structure?
      • If a linked structure is modified, have all links been correctly reassigned?
      • If dynamic storage is used, has space been allocated correctly?

    Quality Assurance

    • Quality assurance includes all activities related to satisfying relevant quality standards for a project.
    • Another goal of quality assurance is continuous quality improvement.
    • Performing Quality Assurance through:
      • Benchmarking
      • Quality audits

    Testing

    • Many IT professionals think of testing as a stage that comes near the end of IT product development.
    • Types of Tests:
      • Unit testing
      • Integration testing
      • System testing
      • User acceptance testing

    Testing Limitations

    • Watts S.Humphrey defines a software defect as anything that must be changed before delivery of the program.
    • Testing does not sufficiently prevent software defects because it does not cover all possible scenarios.

    Program Inspections

    • These are peer reviews where engineers examine the source of a system to discover anomalies and defects.
    • Inspections do not require execution of a system, so they can be used before implementation.

    Studying That Suits You

    Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

    Quiz Team

    Description

    This quiz covers topics related to software inspection checklist, including initialization, constant naming, loop termination, array bounds, data faults, control faults, and more. Test your knowledge on ensuring the quality of software through thorough inspections.

    More Like This

    Software Inspections for Defect Discovery
    18 questions
    Software Inspection: Benefits and Roles
    18 questions
    Software Review and Inspection Pre-test
    15 questions
    Use Quizgecko on...
    Browser
    Browser