Software Evolution and Maintenance (SEAM) Lecture 2 Outline

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

What is the main objective of classifying the types of software maintenance based on objective evidence?

To eliminate the need for accessing the knowledge of the personnel who originally developed the system (correct)

To make the classification groups independent of hardware platform and operating system choice

To verify maintenance tasks with observations

To reflect the actual mix of activities observed in the practice of software maintenance and evolution

What does the proposed classification of software maintenance aim to accurately reflect?

The mix of activities observed in the practice of software maintenance and evolution (correct)

The design methodology and implementation language

The hardware platform and operating system choice

The knowledge of the personnel who originally developed the system

Why is it more informative to classify maintenance tasks based on objective evidence?

It can be verified with observations (correct)

It requires accessing the knowledge of the personnel who originally developed the system

It reflects the mix of activities observed in software maintenance

It is independent of organizational practices

What does the proposed classification of software maintenance not require?

Accessing the knowledge of the personnel who originally developed the system Signup and view all the answers

What does the granularity of the proposed classification aim to accurately reflect?

Actual mix of activities observed in software maintenance and evolution Signup and view all the answers

What are the classification groups independent of?

Hardware platform, operating system choice, and availability of personnel doing original development Signup and view all the answers

Which category of software maintenance involves making the system adapt to changes in its data or processing environment?

Adaptive maintenance Signup and view all the answers

What is an example of a situation that can be described as corrective maintenance?

Correcting a program that produces incorrect results Signup and view all the answers

Which activity falls under perfective maintenance?

Restructuring the code Signup and view all the answers

What is a preventive maintenance measure to prevent the occurrences of failures due to continuously running software?

Software rejuvenation Signup and view all the answers

What is the main focus of corrective maintenance?

Isolation and correction of defective elements in the software Signup and view all the answers

What does perfective maintenance aim to improve?

Readability of the code Signup and view all the answers

Which category of software maintenance is often performed on safety critical and high available software systems?

Preventive maintenance Signup and view all the answers

What type of failure does adaptive maintenance aim to prevent?

Crashes due to continuously running software Signup and view all the answers

What is an example of a situation that can be described as perfective maintenance?

The program outputs can be made more readable for better user experience Signup and view all the answers

What does adaptive maintenance involve changing in a system?

Supporting new hardware configuration Signup and view all the answers

Study Notes

Classification of Software Maintenance

The main objective of classifying software maintenance types based on objective evidence is to accurately reflect the underlying reasons for maintenance.
The proposed classification aims to accurately reflect the underlying reasons for maintenance, rather than relying on subjective or arbitrary labels.

Advantages of Objective Evidence Classification

Classifying maintenance tasks based on objective evidence is more informative as it provides a clear understanding of the reasons behind maintenance activities.
This approach does not require arbitrary or subjective labels, making it more reliable and consistent.

Granularity of Classification

The granularity of the proposed classification aims to accurately reflect the underlying reasons for maintenance, providing a more detailed and nuanced understanding of maintenance activities.

Independence of Classification

The classification groups are independent of the specific maintenance tasks or activities, focusing on the underlying reasons for maintenance.

Types of Software Maintenance

Adaptive Maintenance: involves making the system adapt to changes in its data or processing environment.
Corrective Maintenance: involves fixing errors or faults, for example, debugging a software issue that causes a program to crash.
Perfective Maintenance: aims to improve the software's performance, maintainability, or other quality attributes, for example, refactoring code to make it more efficient.

Focus and Goals of Maintenance

The main focus of corrective maintenance is to fix errors or faults.
Perfective maintenance aims to improve the software's quality attributes, such as performance, maintainability, or usability.
Adaptive maintenance aims to prevent failures due to changes in the system's environment.

Preventive Maintenance

An example of a preventive maintenance measure is to implement a system restart or failover to prevent failures due to continuously running software.

Safety Critical and High Availability Systems

Adaptive Maintenance is often performed on safety-critical and high-availability software systems to prevent failures due to environmental changes.

Failure Prevention

Adaptive maintenance aims to prevent failures due to environmental changes, such as changes in hardware or software configurations.

Studying That Suits You

Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

Description

Explore the outline for Lecture 2 of the Software Evolution and Maintenance (SEAM) course offered by Cairo University Faculty of Graduate Studies. This lecture covers topics such as Categories of Activities and Evidence-based Classification of Software Maintenance.