ICE Task 1

1. The degree to which software meets specified requirements and user expectations.
2. CMMI level where organisational standards and processes are documented and followed.
3. Ability to transfer the software to different environments or platforms.
5. A serious failure where the application stops running unexpectedly.
6. Degree to which users achieve their goals when using the software (quality in use).
8. Measure of how urgently a defect should be fixed (e.g., urgent, high, normal, low).
11. Efficiency in terms of time and resource usage under given conditions.
13. Capability Maturity Model Integration, a framework with five maturity levels for organisations.
14. CMMI level focused on continuous process improvement and innovation.
16. Usability defect where UI elements or behaviours do not follow a uniform pattern.
20. Defect where memory is not released, causing performance degradation over time.
21. A structured set of activities, methods, and practices used to develop and maintain software.
23. Type of security defect where attackers insert malicious code via inputs (e.g., SQL injection).
25. Ease of modifying the software to fix defects, add features, or adapt to changes.
26. How easy and pleasant it is for users to learn and operate the software.
28. Overall capability of the system to perform required functions correctly.
29. Defect type where user manuals or guides are incorrect, incomplete, or outdated.

1. CMMI level where processes are measured and controlled using quantitative data and metrics.
4. Activity of evaluating software to detect defects and verify that quality parameters are met.
7. Suitability for providing the right functions for intended tasks.
9. Consistency of performance over time under stated conditions.
10. Any deviation from expected behaviour, requirements, or accepted standards.
12. Protection of information and prevention of unauthorized access or attacks.
15. CMMI level where basic project management processes are established and repeatable.
17. User’s comfort and acceptability when using the software (quality in use).
18. Measure of how much impact a defect has on the system (e.g., critical, high, medium, low).
19. Ability to co-exist and interact with other systems, environments, or devices.
22. Performance issue where the system responds too slowly to user actions.
24. CMMI maturity level where processes are ad hoc and chaotic.
27. Common informal term for a software defect or fault.