ASQ CSQE - Certified Software Quality Engineer Exam

Testing a software upgrade is classified under the appraisal category of the Cost of Quality. Appraisal costs are associated with evaluating and measuring the quality of products through testing and inspection to ensure they meet quality standards and specifications.

A milestone like " Coding 50% completed " is poorly defined because it is ambiguous and difficult to measure precisely. Here’s a detailed explanation:

Ambiguity : It is unclear what 50% completion means – is it 50% of total lines of code, 50% of modules, or 50% of functionality?

Measurement Challenges : Determining exact percentages of completion can be subjective and inconsistent.

Milestone Criteria : Good milestones should be clear, measurable, and verifiable. " Coding completed for module X " is more specific and measurable.

Project Tracking : Poorly defined milestones can lead to confusion and inaccurate tracking of project progress.

When new requirements are recommended after planning, the correct response is to perform an impact analysis before deciding how to proceed. Impact analysis evaluates effects on scope, schedule, cost, staffing, design, risks, quality objectives, test plans, documentation, and contractual commitments. Automatically moving the requirements to a future release may ignore business priority or urgency. Outsourcing the work does not remove the need to understand impacts and may introduce supplier risks. Simply adding resources and budget to preserve the original date may be unrealistic and can create quality problems. Software quality engineering requires controlled requirement changes based on evidence. Therefore, the team should analyze the impact and then adjust the plan appropriately.

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

When a project experiences significant deviations from baselined budgets, schedules, or quality levels, the first corrective action should be to realign project actuals and continue with the plan. This involves:

Assessing the Deviation : Understanding the root cause and impact of the deviation on the project.

Adjusting the Plan : Making necessary adjustments to realign the project with its original goals.

Updating Stakeholders : Keeping stakeholders informed about the changes and the new plan.

Monitoring Progress : Continuously monitoring the project ' s progress to ensure it remains on track after the adjustments.

This approach allows the project to stay aligned with its original objectives while addressing the issues causing the deviations.

The ASQ Code of Ethics includes responsibilities related to the public, clients, employers, and professional peers. The statement about building a professional reputation on the merit of services and competing fairly with others is directly tied to ethical relations with peers. It emphasizes fairness, professional respect, honest competition, and avoiding actions that damage another professional’s reputation unfairly. Option B relates primarily to public safety, health, and welfare. Option C relates to duties toward clients and employers, especially loyalty and conflict-of-interest avoidance. Option D supports professional development, but the option most clearly focused on peer relationships is fair competition and merit-based professional reputation. Therefore, the correct answer is A.

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

The critical factor for the software manager ' s decision on whether to continue or disregard the inspection program is the cost of not using inspection. Code inspections are a preventive measure to identify defects early in the development process. The cost of not using inspections can include increased defects in the final product, higher costs for post-release fixes, decreased customer satisfaction, and potentially significant impacts on the company’s reputation. While resources, schedule impact, and additional testing costs are important considerations, the long-term cost implications of not identifying defects early can be far more detrimental.

The Chair of the Change Control Board (CCB) is responsible for escalating change requests and other issues to a higher level CCB or management. The Chair ensures that all changes are properly reviewed and approved, and any significant issues that cannot be resolved at the current level are escalated for further consideration.

In the context of software safety, " Level of Control " (LOC) is used to classify software based on the severity of the consequences of its failure. LOC I - Autonomous Time Critical is assigned to software where failure could result directly in a mishap with significant consequences. This level demands the highest safety controls and rigorous testing to mitigate risks.

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 " .