This PPT covers the unit-V of syllabus

1. SOFTWARE
MAINTENANCE
UNIT-V

2. Maintenance and Other Life Cycle Activities-
Introduction
• Effect of requirements gathering on maintenance

3. Effect of requirements gathering on
maintenance
• Obtaining commitment for requirements from the right people
• Presents the big picture or the marketplace expectations of the planned
product
• Nominates other contacts for more details
• Acts as s tie-breaker in the case of conflicts
• Prioritises the various requirements: agreements, change control
norms, statutory processes
• Current system needs: functionality needs, performance needs,
availability needs, security, environmental definition

4. Effect of requirements gathering on
maintenance
• Targets
• Success measure
• Acceptance criteria
• Ongoing needs
• Documentation
• Training
• Ongoing support

5. Design and Maintenance
• Evolving an architecture
• Designing for reuse
• Standardisation: External Standards and Internal Standards
• Interoperability
• Diagnosable Systems: providing enough “footprints”, Making context self-contained,
Having self-identifying data structures, providing “validatable redundancy” in data
structures
• Testable Systems: Identification of test data to ensure that the design faithfully reflects
requirements and that development reflects design, Modularisation with clear
specification of input and output, specification of limiting conditions and the action on
limiting conditions, Error conditions and how they are handled.
• Maintainable systems: module level accountability, no spaghetti code or spaghetti design,
proper documentation
• Programming, Debugging and Maintenance

7. Testing and Maintenance

9. Putting it all together
• A Traceability Matrix is used to contain or counter this problem. A
template for traceability matrix is provided.

10. Other Forms of Maintenance
• Introduction
• Adaptive Maintenance
Certification-a)Market priorities ,popularity of the given environment,
customers response to the product, b)Relinking or Regeneration of the
dependent product
• Relinking or Regeneration of the dependent product
• Data Migration
• Re-writing the code
• Project management and people issues in adaptive maintenance

11. Other Forms of Maintenance
• Enhancement Request
• Proactive defect prevention or preventive maintenance
Operational activities for preventive maintenance
Analytical and communication –oriented activities of preventive maintenance
Analysing common user errors and updating documentation when necessary
Analysing common user errors and changing the product where necessary
Publishing common user errors and workarounds on a bulletin board or a website
Performing root cause analysis of problem areas and cleaning up the code of such
areas
Beefing up regression tests with tests for critical/oft-appearing bugs
• conclusions