Data structures

• Software Reliability vs. Availability:
• Software Availability: The probability that a software system is operational and performing according to specified requirements at a given point in time:

• Software Reliability: The probability of failure-free operation over a specified interval of time under specified conditions.
• Conclusion: The probability at a given point in time is Software Availability (Option 3).

Correct option: (3) Software Availabilty

• Software Reengineering Activities:
• Software Reengineering involves modifying a legacy system to reconstitute it in a new form without altering external functionality.
• Key activities include source code restructuring, code translation (e.g., converting legacy code to modern language), program modularization, and database restructuring.
• Reverse Engineering: Extracting design specifications and abstractions from existing source code.
• Forward Engineering: Implementing new system features from high-level designs.
• Conclusion: Reengineering (Option 4).

Correct option: (4) Reengineering

• Software Configuration Management (SCM) Use Cases:
• Standard Version Control Systems (VCS like Git, SVN) natively support:
• Managing several versions/releases: Branching, tagging, release branches.
• Allowing team members to work in parallel: Isolated feature branches and concurrent editing.
• Identifying when and where regression occurred: Commit history, diffs, blame, and bisect.
• (B) Filing and tracking bug reports: Managed by Issue/Defect Tracking Systems (e.g., Jira, Bugzilla, GitHub Issues), not the version control engine itself.
• Conclusion: Only (A), (C), and (D) (Option 1).

Correct option: (1) Only (A), (C), and (D)