CSQE Exam Dumps : Certified Software Quality Engineer Exam

Failure severity is based on the consequence or impact of the failure, especially its effect on customers, users, safety, mission performance, business operations, or regulatory compliance. In software quality engineering, severity is different from priority. Severity describes how serious the failure is; priority describes how quickly it should be fixed. A defect affecting safety, security, financial transactions, or critical operations is severe even if only one customer reports it. The cost to find and fix the fault may influence project planning, but it does not define severity. The number of reports may indicate frequency or visibility. Time without failure relates to reliability. Therefore, customer impact determines severity.

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

Limiting access to a software system through passwords supports the security objective of access control. Access control ensures that only authorized users can enter the system or perform specific actions based on identity, role, privilege, or permission. Passwords are one authentication mechanism used to verify identity before access is granted. An audit trail records user actions and system events, but passwords do not by themselves supply complete audit records. Preserving data integrity means protecting data from unauthorized or improper modification, which access control may support indirectly. Backup and recovery protect availability and restoration after failure or loss. Since the question specifically describes restricting system entry through passwords, the security objective being met is maintaining access control.

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

Requirements change impact analysis is performed before a change is approved, while the change control board is reviewing the request. The purpose is to evaluate how the proposed change will affect requirements, design, code, test cases, schedule, cost, risk, documentation, baselines, and related configuration items. If impact analysis is delayed until after CCB approval, the board may approve a change without understanding its consequences. Placing items under control and marking them as baselined are configuration management activities, but they do not by themselves trigger impact evaluation. Software quality engineering requires objective analysis before change decisions are made so that approvals are based on risk, feasibility, traceability, and total lifecycle impact.

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