Software Quality Assurance Quiz
48 Questions
1 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

What is the purpose of conducting SQE audits?

  • To evaluate customer satisfaction post-delivery
  • To train new employees on quality management
  • To implement new testing strategies
  • To verify compliance with standard processes (correct)
  • What happens if issues found during audits are not addressed?

  • They are elevated to upper management (correct)
  • They are forwarded to lower management
  • They are ignored and not reported
  • They are documented in STR forms
  • Which form is used to document issues found during testing?

  • STR form (correct)
  • IPDS form
  • QER form
  • TFR form
  • Who is responsible for writing the test report when a separate test group is available?

    <p>The SQE is relieved from this responsibility</p> Signup and view all the answers

    What type of tests are conducted to sell the end-product to the customer?

    <p>Final Acceptance Tests (FAT) and Site Acceptance Tests (SAT)</p> Signup and view all the answers

    Which element of Software Quality Assurance involves selecting appropriate procedures and standards for a project?

    <p>Software Quality Planning</p> Signup and view all the answers

    What is the primary purpose of Software Quality Control?

    <p>To ensure adherence to quality procedures and standards</p> Signup and view all the answers

    Which of the following best describes the role of standards in the SQA process?

    <p>They encapsulate best practices and assist in continuity of work.</p> Signup and view all the answers

    What is the focus of Software Quality Metrics?

    <p>Predicting and controlling quality through data analysis</p> Signup and view all the answers

    Which statement is true about adapting standards for specific software projects?

    <p>Standards should not exceed the requirements of the project.</p> Signup and view all the answers

    What is not a responsibility of Software Quality Assurance (SQA)?

    <p>Creating product standards</p> Signup and view all the answers

    Which of the following is a primary focus of Quality Assurance activities?

    <p>Process used to create the product</p> Signup and view all the answers

    How does the quality of the development process affect the quality of the delivered product?

    <p>It directly impacts product quality.</p> Signup and view all the answers

    Which of the following ISO 9001 elements relates to managing the correctness of a product's design?

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

    What type of activity is integration testing an example of?

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

    Which ISO element is primarily concerned with traceability of products?

    <p>Product identification and traceability</p> Signup and view all the answers

    What does corrective action in quality systems aim to address?

    <p>Any detected non-conformity</p> Signup and view all the answers

    Which approach is suggested to be ineffective for software product quality control?

    <p>Factory manufacturing model</p> Signup and view all the answers

    What is the primary purpose of standardizing metrics in software quality assurance?

    <p>To enhance the effectiveness of the assessment</p> Signup and view all the answers

    Why is it important for the Software Quality Assurance (SQA) team to maintain independence?

    <p>To provide an unbiased perspective on the process</p> Signup and view all the answers

    What does it mean when a build is in a freeze state during testing?

    <p>No changes to the system code are permitted</p> Signup and view all the answers

    What is the role of the Software Quality Assurance (SQA) team concerning deviations in process and product?

    <p>They ensure deviations are reported using the proper procedures</p> Signup and view all the answers

    How does reliability relate to software quality?

    <p>It signifies how rarely users experience failure with the system</p> Signup and view all the answers

    What should a Software Quality Assurance (SQA) plan include?

    <p>Guidelines for evaluations, audits, and error tracking procedures</p> Signup and view all the answers

    What misconception might people have regarding prototyping in relation to standards?

    <p>Prototyping involves tailored standards rather than no standards</p> Signup and view all the answers

    What is a key challenge when constructing a reliable system?

    <p>Ensuring the system is free of faults</p> Signup and view all the answers

    What is considered a fault in a software system?

    <p>The cause of a failure in the software</p> Signup and view all the answers

    How is software reliability defined?

    <p>The probability of failure-free operation for a specific time in a specific environment</p> Signup and view all the answers

    What factors influence a user's perception of software reliability?

    <p>The number of faults present and the methods of user operation</p> Signup and view all the answers

    What does a high failure intensity indicate about a software system?

    <p>The software experiences frequent failures</p> Signup and view all the answers

    In the context of reliability, what is execution time denoted by?

    <p>τ</p> Signup and view all the answers

    Which of the following does NOT directly influence the fault count of a software system?

    <p>User interface design</p> Signup and view all the answers

    What is considered when evaluating the reliability of a software system over time?

    <p>The interval between successive failures</p> Signup and view all the answers

    Which of the following is an example of failure intensity?

    <p>An air traffic control system that fails only once every two years</p> Signup and view all the answers

    What is the primary goal of defect prevention?

    <p>To establish practices that minimize reliance on defect detection</p> Signup and view all the answers

    Which of the following represents a formal bug finding activity?

    <p>Quality Reviews</p> Signup and view all the answers

    What does 'Managing With Metrics' refer to in the context of defect prevention?

    <p>Collecting data and making product changes based on analysis</p> Signup and view all the answers

    What phase of software development has the highest percentage of defects contained?

    <p>System Integration</p> Signup and view all the answers

    What is the purpose of learning from other people's experiences in defect prevention?

    <p>To improve efficiency by avoiding known pitfalls</p> Signup and view all the answers

    In the software development phases, which phase typically has a low defect percentage that escapes containment?

    <p>Unit Test</p> Signup and view all the answers

    Which activity involves reviewing a product's design to identify potential defects?

    <p>Design Review</p> Signup and view all the answers

    What percentage of defects typically originate during the Software Qualification Test phase?

    <p>0%</p> Signup and view all the answers

    What is meant by a defect being 'contained' in a particular phase of software development?

    <p>The defect is discovered before reaching the next phase</p> Signup and view all the answers

    Which of the following best describes the process following 'Post System Test'?

    <p>Closing out unverified defects</p> Signup and view all the answers

    What does 'Lessons Learned' contribute to defect prevention?

    <p>A resource for improving processes by sharing experiences</p> Signup and view all the answers

    In the software development process, which role typically verifies a resolved defect?

    <p>Tester</p> Signup and view all the answers

    What is the primary strategy during the Software Integration phase?

    <p>Merging individual software components into a cohesive system</p> Signup and view all the answers

    What is the impact of having a high percentage of defects originating in a specific phase?

    <p>It suggests potential weaknesses in that phase</p> Signup and view all the answers

    Study Notes

    Lecture 7: Software Quality

    • Software quality is defined as a developed product meeting its specifications.
    • Problems include: Requirements exceeding customer specifications, ambiguous quality characteristics (e.g., maintainability), and users not involved in requirements development, potentially leading to products deemed low quality, even if they meet specifications.
    • Quality can be understood in terms of "fitness for purpose".
    • Customer perception of quality is crucial.
    • Observable factors (e.g., user interface, freedom from faults) are easier to evaluate than less obvious aspects (e.g., security, future upgrades).
    • Customers don't always articulate their needs clearly.
    • Making quality software is about meeting customer needs, not just what they say they want.

    Software Quality Assurance (SQA)

    • SQA is a systematic approach to ensuring software products and processes meet quality standards and customer needs.

    • SQA encompasses more than just testing.

    • It involves a range of practices to reduce the risks of developing low-quality products.

    • SQA includes Software Quality Planning (SOP), Software Quality Control (SQC), and Software Quality Metrics (SOM).

      • Processes and standards for creating software are selected and tailored to the specific quality objectives.
      • Definition & implementation of processes to ensure quality procedures and standards are followed.
      • Collection and analysis of quality data to predict and control quality throughout the software development lifecycle.

    SQA Umbrella (Components)

    • Product Assessment
    • Test Management
    • Test Planning
    • Test Development
    • Test Automation
    • Test Execution
    • QA Project Management
    • Defect Management
    • Triage
    • Metrics
    • Audits
    • Process Assessment
    • Process Improvement
    • Risk Management
    • Estimating and Scheduling
    • Release Criteria
    • Defect Reporting
    • Release Process
    • Project Retrospective
    • Change Management
    • Peer Reviews & Inspections
    • Verification & Validation

    SQA - Iceberg Analogy

    • External Quality: Visible aspects like correctness, efficiency, reliability, and maintenance cost.
    • Internal Quality: Less visible aspects like program structure, complexity, coding practices, testability, coupling, maintainability, readability, and reusability.

    Why are Standards Important?

    • Standards encapsulate best practices.
    • They provide a framework for quality assurance implementation.
    • They ensure consistency across projects, no matter who implements the processes.

    SDS (Systems Development Standards)

    • ISO 9000 isn't the only standard source for SDS.
    • Process and product standards are derived independently.
    • Product standards are not created only by the SQA group.

    Quality Standards (e.g. ISO 9001:2000)

    • Standards like ISO 9001:2000 define quality management systems, specifying requirements for documentation, procedures, and activities.
    • Ensure quality throughout a project's lifecycle

    ISO - 9001 Elements (Key Components)

    • Various quality system requirements, including management responsibility, contract review, design control, document controls, purchasing, product identification and traceability, process control, inspection and testing, corrective action, quality records, internal audits, training, and statistical techniques. These govern all aspects of the software development process.

    Process and Product Quality

    • Quality of the development process directly affects the quality of delivered products.

    Obtaining Quality: Quality Control & Assurance

    • Quality Control: Measures quality of produced products via testing methods (integration testing, code reviews).
    • Quality Assurance: Focuses on the development process itself, ensuring all procedures are correctly followed (e.g., testing at all stages).

    Methods of Software Quality Control (SQC)

    • Quality Reviews: In-process reviews of processes and products.
    • Tests (e.g., Unit Tests, SQE Dry-runs, TFR): End-result verifications to check if procedures are correctly implemented.
    • Quality Audits: In-process verifications to ensure compliance with process standards.

    Quality Reviews (Types - Peer Reviews, Walkthroughs, Desk Inspections)

    • Peer reviews involve groups, while walkthroughs are group-based discussions about products.
    • Desk inspections are individual reviews.

    Tests (Engineering Dry-runs, SQE Dry-runs, TFR)

    • Engineering dry-runs are conducted by engineers without SQA involvement, used to check correctness, etc.
    • SQE dry-runs are done by the SQE before formal customer testing and involve the end-product.
    • TFR (Testing for record) are conducted as the final customer test, and SQE is involved.

    Quality Audits (SQE Audits, Independent Audits)

    • SQE Audits: Verify that procedures are followed by evaluating tasks, and escalating issues not addressed.
    • Independent Audits: Conducted by a third party to confirm process validity through external means.

    Defect Detection Process and Metrics

    • Analyzing the frequency of defects arising from each development stage, and from different test phases.

    Defect Prevention Strategies

    • Lessons learned from previous projects.
    • Risk analysis to identify potential issues early-on.
    • Standardized testing guidelines, and creating a fixed/freeze point for code.
    • Baseline Acceptance Criteria and ensuring testing (No P1 STRs in FAT TRR).

    Continuity and Independence of SQA

    • An independent team is crucial for an objective perspective.
    • Tailored standards based on the specific project requirements, not using a one-size-fits-all approach.
    • Emphasizing that quality is everyone's responsibility.
    • The SQA teams' role is to assist the development team in creating high-quality software, not to entirely manage the project.

    The SQA Plan

    • Preparing an SQA plan at the start of a project provides structure to quality assurance activities

    SQA Activities

    • Assist with process selection for a specific project.
    • Review software engineering activities and products to ensure project/process compliance.
    • Document all process deviations for correction.
    • Detail any non-compliances for management review.

    Reliability Concepts

    • Reliability: A broad concept measuring how frequently a software crashes or has issues.
    • Fault vs. Failure: fault is the issue, failure is the consequence.
    • Time aspects of reliability include execution time and calendar time between failures.
    • Definitions of Reliability: Probability of error-free operation over a given time in a specific environment or in relation to failure intensity (the frequency of failure).
    • Factors Influencing Reliability: The size and complexity of the code, the development process, and even the environment in which the product is operated.

    Studying That Suits You

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

    Quiz Team

    Related Documents

    Description

    Test your knowledge on the principles and practices of Software Quality Assurance (SQA). This quiz covers essential topics like auditing, quality control, and the roles of standards in the SQA process. Perfect for software professionals looking to refresh their understanding of SQA.

    More Like This

    Use Quizgecko on...
    Browser
    Browser