Scribd
Upload
8 views3 pages

Slide - 11 Summery

Software maintenance involves modifications to software post-delivery for bug fixes, performance improvements, and adapting to new environments. It constitutes a significant part of the software lifecycle, yet it is often under-researched and lacks adequate training in academia. Key challenges include high costs, lack of documentation, and evolving user expectations, necessitating effective strategies for prioritizing and managing maintenance tasks.

Uploaded by

gihel53025
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views3 pages

Slide - 11 Summery

Software maintenance involves modifications to software post-delivery for bug fixes, performance improvements, and adapting to new environments. It constitutes a significant part of the software lifecycle, yet it is often under-researched and lacks adequate training in academia. Key challenges include high costs, lack of documentation, and evolving user expectations, necessitating effective strategies for prioritizing and managing maintenance tasks.

Uploaded by

gihel53025
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Software Maintenance: Key Concepts and Insights

**Definition of Software Maintenance**


- Modifications to a software product after delivery for:

- Correcting faults.

- Improving performance.

- Adapting to a modified environment. (IEEE Std 1219)

**Importance of Maintenance**
- Accounts for a significant part of the software lifecycle.

- More than 50% of graduate students are involved in maintenance, yet it's
under-researched and rarely taught.

**Why Maintenance is Needed**


1. **Bug Fixes**: Address issues encountered by users.

2. **Environment Adaptation**: Update systems for new


hardware/software changes.

3. **Upgrades**: Add or modify features to meet changing organizational


needs.

4. **Performance Improvements**: Enhance system efficiency for


increased user demands.

5. **Future Facilitation**: Reorganize complex systems for easier updates.


Page
**Lifecycle of Maintenance**
1. **Initial Development**: Creating the software.

2. **Evolution**: Implementing new requirements and enhancements.

3. **Servicing**: Maintaining operational efficiency without adding new


features.

4. **Phase-out**: Limited use with no further changes.

5. **Closedown**: System retirement.

**Types of Maintenance (IEEE Classification)**


1. **Corrective**: Fixing faults post-delivery.

2. **Adaptive**: Adjusting software for environmental changes.

3. **Perfective**: Enhancing system functionality to meet user needs.

4. **Preventive**: Anticipating and preventing potential issues.

**Challenges in Maintenance**
- Lack of clear documentation.

- High costs (up to 90% of lifecycle costs in some cases).

- Difficulty in adapting to evolving requirements and user expectations.

Page
**Maintenance vs. Development**
- Development builds a new system; maintenance modifies an existing one.

- Maintenance involves understanding the existing system architecture.

**Prioritizing Maintenance Requests**


- **Priority 1**: Immediate fixes to maintain operations.

- **Priority 2**: High-impact issues requiring quick resolution.

- **Priority 3**: Delayed, tolerable repairs.

- **Priority 4**: Non-critical updates when resources allow.

**Key Issues in Maintenance**


- Misalignment between academia and industry on training.

- The high cost due to user-driven enhancements and outdated structures.

- Naming and categorization debates in defining maintenance practices.

**Recommendations for Effective Maintenance**


- Foster team stability and enhance staff skills.

- Document changes comprehensively.

- Design systems with future adaptability in mind.

Page

You might also like