Controlled libraries, also known as configuration-controlled libraries, are used to store and manage intermediate baselines. These baselines are versions of the software at various points in the development lifecycle. By archiving these baselines in a controlled library, teams can ensure that all changes are tracked, and specific versions can be retrieved when needed for further development, testing, or rollback purposes. This practice is essential in maintaining configuration management and ensuring the integrity and traceability of software versions.

A test plan should be changed after changes to the design specifications. This ensures that the tests remain relevant and accurately reflect the new design and functionality of the software. Keeping the test plan updated with design changes helps ensure comprehensive test coverage and alignment with the project ' s requirements.

The nominal group technique is a structured decision-making and problem-solving method that is useful when a group faces a controversial or sensitive issue. In software quality engineering, JAD sessions involve multiple stakeholders, and disagreements can occur when requirements, priorities, risks, or design expectations conflict. The nominal group technique helps by allowing participants to generate ideas independently, share them in an organized way, discuss them fairly, and rank or vote on alternatives. This reduces domination by louder participants and encourages balanced input. Brainstorming is useful for generating ideas but may not resolve sensitive conflict. Smoothing reduces visible tension but may avoid the real issue. An effort/impact grid helps prioritize options but does not provide the same structured conflict-resolution process.

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

An effective listener is defined as someone who is attuned to nonverbal cues. Effective listening involves not only hearing the words but also understanding the speaker ' s body language, tone, and other nonverbal signals, which can provide significant context and understanding beyond the spoken words.

A traceability matrix can be used to assess the impact of a proposed software change. This tool maps requirements to their corresponding test cases, ensuring that all requirements are covered and helping to identify the effects of changes on existing functionality. By providing a clear link between requirements, development, and testing, a traceability matrix facilitates impact analysis and helps in maintaining the integrity of the system during changes.

Protection against data intrusion focuses on preventing unauthorized access to systems, applications, networks, and data. One of the most direct controls is limiting who can access the system through authentication, authorization, role-based access control, least privilege, and account management. Trending security breaches can support monitoring and improvement, but it is detective rather than preventive. Improving recovery time is related to resilience, continuity, or disaster recovery after disruption, not intrusion prevention. Switching to degraded mode may help maintain operation during certain failures, but it does not directly protect data from unauthorized access. Software quality engineering treats security as a quality attribute requiring requirements, design controls, testing, and operational procedures. Access limitation is the best protection-oriented answer.

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

For safety-critical software, it is crucial to specify how the system should react to accidents or hazardous conditions to mitigate risks and ensure safety. This type of requirement directly addresses safety concerns by defining specific actions that the system must take in response to potential safety issues.

Performance is a non-functional requirement that describes how well software operates under defined workload and environmental conditions. It may include response time, throughput, latency, resource utilization, scalability, capacity, and behavior under peak or sustained load. In software quality engineering, performance requirements must be measurable so they can be verified through performance testing, load testing, stress testing, or monitoring. User-friendliness and intuitive interaction describe usability, not performance. Easy updating describes maintainability or modifiability. Legal and compliance standards describe regulatory or contractual constraints. The correct answer is determining how well the software operates under varying workload conditions because performance requirements focus on speed, efficiency, capacity, and responsiveness during real operating conditions.

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

Maslow’s hierarchy of needs is often used in management and team leadership topics within software quality engineering because motivation affects team performance, communication, and productivity. The hierarchy begins with physiological needs, such as food, water, rest, and basic survival requirements. These are the most fundamental needs because a person must satisfy them before focusing effectively on higher-level needs. Safety needs come next and include security, stability, and protection. Belonging relates to relationships and team membership. Self-actualization is the highest level and involves personal growth and achieving full potential. Since physiological needs form the base of the hierarchy, they are the most basic among the listed choices.

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

Reengineering a software module typically involves assessing various factors such as code complexity, maintainability, performance requirements, and the age of the platform.  The goal is to identify modules that are costly to maintain, difficult to understand, or are becoming obsolete due to platform changes 1 2 .

Cyclomatic Complexity: This is a quantitative measure of the number of linearly independent paths through a program’s source code.  A higher cyclomatic complexity indicates a more complex and potentially less maintainable module 2 .

Looking at the table provided:

Module A has a version number of 12 and a cyclomatic complexity of 9.

Module B has a version number of 3 and a cyclomatic complexity of 21.

Module C has a version number of 9 and a cyclomatic complexity of 4.

Module D has a version number of 11 and a cyclomatic complexity of 20.

Given these details, Module B stands out as the most likely candidate for reengineering for the following reasons:

It has the  highest cyclomatic complexity (21) , which suggests that the code is highly complex and may be difficult to maintain or extend 2 .

The version number being 3 indicates that it has undergone fewer iterations of updates or fixes compared to the other modules, which might imply that it has legacy code that could benefit from reengineering.