Quality Management System Awareness - Part 3

Reviewed by Editorial Team
The ProProfs editorial team is comprised of experienced subject matter experts. They've collectively created over 10,000 quizzes and lessons, serving over 100 million users. Our team includes in-house content moderators and subject matter experts, as well as a global network of rigorously trained contributors. All adhere to our comprehensive editorial guidelines, ensuring the delivery of high-quality content.
Learn about Our Editorial Process
| By Anuragnechcl
A
Anuragnechcl
Community Contributor
Quizzes Created: 5 | Total Attempts: 4,546
| Attempts: 938
SettingsSettings
Please wait...
  • 1/10 Questions

    Who all must be informed about the closure of the project

    • QA
    • Finance & HR
    • Senior Management
    • All relevant stakeholder
Please wait...
About This Quiz

This quiz, part of the Quality Management System Awareness series, tests knowledge on review processes, project closure, ETVX framework, project metrics, software requirements specification, and root cause analysis. It's designed to reinforce understanding and ensure alignment with quality management standards.

Quality Management Systems Quizzes & Trivia

Quiz Preview

  • 2. 

    JIRATool can be used as

    • Project Management Tool

    • Defect loging Tool

    • Leave Request

    • None of the above

    Correct Answer
    A. Project Management Tool
    Explanation
    The correct answer is Project Management Tool because JIRATool is specifically designed to help manage projects, track progress, assign tasks, and collaborate with team members. It provides features like task tracking, issue management, project planning, and reporting, making it an ideal tool for project management purposes.

    Rate this question:

  • 3. 

    ETVX stands for

    • Entry,Time,Validation,Exit

    • Entry,Tasks,Verification,Exit

    • Entry,Tasks,Value, Exit

    • None of the above

    Correct Answer
    A. Entry,Tasks,Verification,Exit
    Explanation
    ETVX stands for Entry, Tasks, Verification, Exit. This acronym is commonly used in software testing to describe the different stages in a test case. The "Entry" stage refers to the initial setup or preparation for the test. "Tasks" represent the specific actions or steps to be performed during the test. "Verification" involves checking the expected results against the actual results obtained from the test. Finally, "Exit" signifies the completion or closure of the test case. Therefore, ETVX accurately represents the sequential flow of a test case.

    Rate this question:

  • 4. 

    Project Kick-off Meeting should be done

    • Within 1 week of project start

    • Within 1 month of project start

    • Project Kick-off is not mandatory

    • None of the above

    Correct Answer
    A. Within 1 week of project start
    Explanation
    The correct answer is "Within 1 week of project start" because a project kick-off meeting is an important step in initiating a project. It allows the project team to come together, establish goals and objectives, define roles and responsibilities, and discuss the project plan and timeline. Holding the kick-off meeting within the first week of the project start ensures that all team members are on the same page from the beginning and can start working towards the project's success.

    Rate this question:

  • 5. 

    What are the different types of reviews defined in the review process

    • Walkthrough Process & Offline Review process

    • MRM & SMR

    • SQA Review & SMR

    • None of the above

    Correct Answer
    A. Walkthrough Process & Offline Review process
    Explanation
    The correct answer is "Walkthrough Process & Offline Review process". In the review process, there are different types of reviews that can be conducted. One of these types is the "Walkthrough Process", which involves a step-by-step examination of the product or document being reviewed, with the aim of identifying defects and improving its quality. Another type is the "Offline Review process", which is a review conducted individually by the reviewers, without any direct interaction or discussion. These two types of reviews are commonly used in the review process to ensure thorough evaluation and improvement of the product or document.

    Rate this question:

  • 6. 

    Root Cause Analysis is a mechanism to

    • Analyse the root cause of an already occurred defect

    • Prevent Occurrence of a defect

    • Analyse the root cause of a defect that may potentially occur

    • Analyse the cause and prevent recurrence of a defect

    Correct Answer
    A. Analyse the cause and prevent recurrence of a defect
    Explanation
    Root Cause Analysis is a mechanism used to analyze the cause of a defect and prevent its recurrence. It involves identifying the underlying factors that led to the defect and addressing them to prevent similar issues from happening in the future. By understanding the root cause, organizations can implement effective corrective actions and improve their processes to avoid the repetition of defects. This approach helps in enhancing product quality, reducing costs, and increasing customer satisfaction.

    Rate this question:

  • 7. 

    Project's Quantitative plan must include

    • Metrics with goals & threshold values

    • Work Breakdown Structure

    • Project Review & Audit Plan

    • Quality Assurance Plan

    Correct Answer
    A. Metrics with goals & threshold values
    Explanation
    The project's quantitative plan must include metrics with goals and threshold values in order to measure the project's progress and performance. These metrics provide quantifiable targets and benchmarks that help assess whether the project is meeting its objectives and staying within acceptable limits. By setting goals and threshold values for various metrics, such as cost, schedule, quality, and productivity, the project team can track and evaluate the project's performance, identify any deviations or issues, and take appropriate corrective actions if necessary. This ensures that the project stays on track and meets its intended outcomes.

    Rate this question:

  • 8. 

    SRS is prepared to

    • Assign responsibility to analyze the system requirements

    • Establish common understanding between client and project team over requirements

    • Both of the above

    • None of the above

    Correct Answer
    A. Establish common understanding between client and project team over requirements
    Explanation
    The correct answer is "Establish common understanding between client and project team over requirements." This is because an SRS (Software Requirements Specification) is a document that outlines the requirements for a software system. One of the main purposes of an SRS is to ensure that there is a common understanding between the client (the one who needs the software) and the project team (the one who will develop the software) regarding what the software should do. By establishing this common understanding, the SRS helps to prevent misunderstandings and ensure that the software meets the client's needs. Assigning responsibility to analyze the system requirements is not the main purpose of an SRS, although it may be a part of the process.

    Rate this question:

  • 9. 

    To analyze possible decisions through a formal evaluation process and

    • CAR Process

    • Metrics Process

    • DAR Process

    • DP process

    Correct Answer
    A. DAR Process
    Explanation
    The DAR Process is the most suitable option for analyzing possible decisions through a formal evaluation process because it stands for Decision Analysis and Resolution. This process involves identifying and evaluating alternative solutions, assessing their potential impacts, and selecting the most appropriate decision based on defined criteria. It helps in reducing risks and uncertainties associated with decision-making by providing a structured approach to analyze and resolve complex problems. The CAR Process, Metrics Process, and DP Process do not specifically focus on decision analysis and resolution, making them less suitable options.

    Rate this question:

  • 10. 

    The frequency of obtaining Customer feedback is

    • Every 6 months for Short term projects and on completion for Long term projects.

    • Every 6 months for Long term projects and on completion for short term projects

    • Every 3 months for Long term projects and on completion for short term projects.

    • Both (a) and (b).

    Correct Answer
    A. Every 6 months for Long term projects and on completion for short term projects
    Explanation
    The correct answer is "Every 6 months for Long term projects and on completion for short term projects." This means that for long term projects, customer feedback is obtained every 6 months, while for short term projects, feedback is obtained upon completion. This approach allows for regular feedback and improvement for long term projects, while also ensuring that feedback is obtained in a timely manner for short term projects.

    Rate this question:

Quiz Review Timeline (Updated): Mar 21, 2023 +

Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.

  • Current Version
  • Mar 21, 2023
    Quiz Edited by
    ProProfs Editorial Team
  • Dec 12, 2011
    Quiz Created by
    Anuragnechcl
Back to Top Back to top
Advertisement
×

Wait!
Here's an interesting quiz for you.

We have other quizzes matching your interest.