Pass the ASQ certification CSQE Questions and answers with Dumpstech

Software cost estimation models, such as COCOMO (Constructive Cost Model), commonly use " Lines of Code (LOC) " as a primary input. LOC is a measure of the size of a software program by counting the number of lines in the source code. This metric is essential for estimating the amount of effort and time required to develop the software. Other inputs may include function points and other metrics, but LOC remains a fundamental component in many models. References: Barry W. Boehm ' s " Software Engineering Economics " .

A software baseline is a set of documents or files that serve as a reference point for further development.

Definition: A baseline is a formally reviewed and agreed-upon set of items that serve as a basis for further development and can only be changed through formal change control procedures.

Components: The test plan and test cases are part of the software baseline because they are essential for verifying and validating the software against its requirements.

Importance: Including test plans and test cases in the baseline ensures that there is a clear, documented set of criteria and procedures for evaluating the software ' s performance and compliance with requirements.

According to the CMMI-DEV (Capability Maturity Model Integration for Development) version 1.3, there are 7 process areas defined for an organization at Maturity Level 2. These process areas are Requirements Management, Project Planning, Project Monitoring and Control, Supplier Agreement Management, Measurement and Analysis, Process and Product Quality Assurance, and Configuration Management. These areas focus on establishing basic project management and process discipline.

Functional configuration audits are used to verify that the completed requirements and designs conform to their requirements specifications. These audits involve checking that the developed product meets all the specified requirements and that the design has been implemented correctly. This process ensures that the final product aligns with the original requirements and design specifications, maintaining consistency and quality.

Knowing when to stop testing is one of the biggest challenges in software testing. This challenge stems from the fact that exhaustive testing is practically impossible due to constraints of time and resources. Testers must decide when enough testing has been done to ensure an acceptable level of quality and risk. This decision is often based on various factors such as coverage of requirements, defect discovery rates, risk assessments, and project timelines.

A code coverage monitor measures the extent to which the source code of a program is executed during testing. The primary output from a code coverage monitor is an indication of which lines of code, branches, or paths have been executed. This helps in identifying untested parts of a codebase, ensuring more comprehensive testing, and improving overall software quality.

Software security is designed to protect systems and data from various types of communication threats. These threats can be categorized as:

Intentional Attacks : These are deliberate actions taken by malicious individuals or groups aiming to exploit software vulnerabilities for gain, disruption, or espionage. Examples include hacking, phishing, and malware attacks.

Unintentional Attacks : These are accidental events that can cause security breaches, such as user errors or software bugs.

Physical Attacks : These involve physical actions against hardware that can affect software, like theft or damage.

Natural Disasters : Events such as earthquakes or floods that can physically damage systems and cause software failures.

Among these, software security primarily addresses intentional attacks. The focus is on preventing unauthorized access, data breaches, and other forms of cyber attacks.

A software product should be re-inspected when the inspection team agrees that re-inspection is necessary. In formal inspections, the decision depends on the seriousness, number, and type of defects found, the extent of required rework, and the risk that corrections may introduce new defects. The team has the technical context to judge whether follow-up verification is enough or a full re-inspection is required. A rework estimate greater than the original inspection effort may suggest concern, but it is not the only decision rule. Being ahead of schedule is not a quality-based reason. A very small number of modules needing rework may reduce the need for re-inspection. The best criterion is the inspection team’s judgment.

================

A program review is used to examine overall project or program performance, including cost, schedule, scope, risks, dependencies, issues, resources, and progress against commitments. In software quality engineering and project management, this type of review gives management visibility into whether the project remains controlled and aligned with business objectives. A phase gate review determines whether a project should proceed from one lifecycle phase to another, but the question’s wording focuses on ongoing examination of management performance areas. A retrospective focuses on lessons learned after an iteration, phase, or project. An architectural design review evaluates technical structure and design quality. Therefore, the review most directly associated with cost, schedule, scope, and risk is the program review.

================

The phrase " 80% coverage " in testing typically refers to the percentage of statements in the program that have been executed at least once during testing. This is known as statement coverage or code coverage. It is a measure of how much of the code has been exercised by the test suite and is used to assess the thoroughness of the testing efforts. It does not necessarily mean that 80% of the software is error-free, that 80% of planned test cases have been completed, or that 80% of predicted errors have been uncovered, although higher coverage often correlates with better defect detection.