Quality Management System Awareness - 5

The correct answer is "All of the above." This means that all three methods mentioned - LoC based, complexity based, and function point based - are standard methods of doing estimation at NHST. Each method has its own advantages and is used in different situations depending on the requirements and constraints of the project.

WBS stands for Work Breakdown Structure. A Work Breakdown Structure is a hierarchical decomposition of the project scope into smaller, more manageable components. It provides a visual representation of the project deliverables and their relationships, allowing for better planning, organizing, and controlling of the project. The WBS helps in defining the work packages, estimating resources and durations, and assigning responsibilities, making it an essential tool in project management.

The correct answer is fine-tuning a pre-existing estimation model. Calibration of an estimation model refers to the process of adjusting or refining an existing model to make it more accurate and reliable for a specific project or context. This involves making small adjustments, modifications, or updates to the existing model based on past data, feedback, or expert judgment to improve its performance and align it with the specific requirements and characteristics of the project at hand. It does not involve creating a completely new model or adopting an existing one without any modifications.

Defect Density is not a core metric for testing projects. Core metrics for testing projects typically include test case coverage, test case development productivity, and test case execution efficiency. Defect density, on the other hand, is a measure of the number of defects found per unit of code or functionality. While it is an important metric for assessing the quality of the software, it is not considered a core metric for testing projects.

If a project identifies "Cost Effectiveness" as one of its objectives, it should monitor the metric of productivity. Monitoring productivity allows the project team to track the efficiency and output of their work, ensuring that resources are being used effectively and efficiently. By measuring productivity, the project can identify areas where improvements can be made to optimize costs and achieve the objective of cost effectiveness.

The correct answer is "Both A and B." WBRT, which stands for "Walkthrough Based Review Technique," is a method used to record the defects found during both Walkthrough and Offline reviews. Walkthrough review involves a group of people reviewing a document or code together, while Offline review allows individuals to review the material independently. Both methods aim to identify and document any defects or issues that need to be addressed. Therefore, the correct answer is that WBRT can be used to record defects found during both types of reviews.

The correct answer is Planning > Review > Follow-up. During an offline review, the first step is planning, where the objectives and scope of the review are defined. The next step is the review itself, where the review team examines the work product and identifies any issues or areas for improvement. Finally, there is the follow-up, where the findings from the review are communicated, and any necessary actions are taken to address the identified issues. This sequence ensures that the review process is organized and effective.

RACI stands for Responsible, Approver, Consulted, Informed. This acronym is commonly used in project management to define and clarify roles and responsibilities within a team or organization. The responsible person is the one who is accountable for completing a task or delivering a result. The approver is the person who has the authority to approve or reject a decision or action. Those who are consulted are individuals who provide input or expertise on a particular matter. Lastly, those who are informed are kept up to date on progress or decisions but do not have a direct role in the task.

The requirement document, design document, and test cases are eligible for formal review because these artifacts are crucial for the project's success. The requirement document outlines the project's objectives and scope, the design document provides a blueprint for the solution, and the test cases ensure that the solution meets the specified requirements. By conducting formal reviews of these artifacts, the project team can identify any potential issues or gaps early on and make necessary improvements before implementation. This helps to ensure that the final product meets the desired quality standards.

Defect Density is a metric used to measure the number of defects in a software system relative to its code size. It is calculated by dividing the number of defects by the actual code size. This metric helps in assessing the quality of the code and identifying areas that require improvement. By measuring the number of defects per unit of code, it provides a standardized measure that can be used to compare different projects or releases. Therefore, the correct answer is "Number of defects/Actual code size."

Reused LOC is not a component of LOC based estimation. LOC based estimation is a technique used to estimate the size of a software project based on the number of lines of code (LOC) that need to be written. The components of LOC based estimation include optimistic LOC, pessimistic LOC, and most likely LOC. These components help in determining the range of effort required for the project. Reused LOC refers to the lines of code that are reused from existing software components or libraries, and it is not considered a separate component in LOC based estimation.

The Function Point estimation model is used to estimate the size of a project. It is a technique that measures the functionality provided by a system based on the user's perspective. By using this model, the project estimate focuses on determining the size of the software, which is a crucial factor in estimating resources, effort, and cost required for the project.

A walkthrough is a review process where a group of people come together to examine a project or work against specific criteria or standards. They identify any gaps or areas that need improvement. This process involves multiple perspectives and inputs from different individuals, making it more comprehensive. Therefore, the correct answer is "performed by a group of people to check the gaps against defined criteria."

A complexity-based estimation model is used to estimate the effort required for a software development project based on its complexity. The productivity factor is an essential input factor in this model because it helps in determining the productivity level of the development team. It takes into account various factors such as the skill level of the team, their experience, and the tools and technologies they will be using. By considering the productivity factor, the estimation model can provide a more accurate estimate of the effort required for the project.

Effort Variance is a metric that measures the difference between the estimated effort and the actual effort spent on a project. By monitoring this metric, project managers can validate the accuracy of their initial effort estimates. If the effort variance is high, it indicates that the estimated effort was significantly different from the actual effort, highlighting the need for adjustments in future estimations. Therefore, Effort Variance is an important metric to monitor in order to validate the estimated effort of a project.