Scribd
Upload
2 views3 pages

City Taxi System Maintenance Strategy

The maintenance strategy for the City Taxi Reservation System includes a structured weekly schedule focusing on preventive, corrective, adaptive, and perfective maintenance to ensure system reliability and user satisfaction. Key activities involve monitoring performance, addressing user-reported issues, ensuring compatibility with third-party services, and implementing enhancements based on feedback. Weekly reviews are conducted to summarize activities and prioritize tasks for the upcoming week.

Uploaded by

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

City Taxi System Maintenance Strategy

The maintenance strategy for the City Taxi Reservation System includes a structured weekly schedule focusing on preventive, corrective, adaptive, and perfective maintenance to ensure system reliability and user satisfaction. Key activities involve monitoring performance, addressing user-reported issues, ensuring compatibility with third-party services, and implementing enhancements based on feedback. Weekly reviews are conducted to summarize activities and prioritize tasks for the upcoming week.

Uploaded by

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

Chapter 05: Project Maintenance

The maintenance strategy for the City Taxi Reservation System is designed to ensure that the
system operates reliably, securely, and efficiently, meeting the evolving needs of both passengers
and drivers. As a critical part of the project’s lifecycle, maintenance is organized into weekly
tasks that address potential system issues proactively while remaining responsive to user
feedback and environmental changes. By implementing a structured maintenance schedule, the
team can continually optimize performance, fix bugs promptly, adapt to technological changes,
and enhance the system based on user feedback.

Day Task Type Activities Responsible


Monday Preventive - Review and monitor server Back-end developer
Maintenance performance logs for any
anomalies.
- Conduct database backup and
data integrity check.
Tuesday Corrective - Review user-reported issues Scrum Master
Maintenance from the previous week.
- Assign priority and begin
addressing any critical bugs
affecting bookings, payments,
or GPS tracking.
Wednesday Preventive - Conduct security check for Full Stack Developer
Maintenance vulnerabilities, including
monitoring firewall and access
logs.
Perform database optimization
for frequently accessed tables.
Thursday Adaptive - Check for updates in third- Backend Developer
Maintenance party services (e.g., GPS,
payment gateway) and review
compatibility.
- Assess if there are any
compliance or regulatory
updates impacting the system.
Friday Perfective - Review and prioritize user Product Owner,
Maintenance feedback collected through Front End developer
support channels.
- Plan minor enhancements or
interface improvements based
on feedback.
Saturday Preventive - Conduct server health check Backend Developer
Maintenance (CPU, memory usage, disk
space).
- Clean up unnecessary logs and
temporary files.
Sunday Review and - Weekly summary report on Scrum Master and
Reporting maintenance activities and development team
issues resolved.
- Review pending tasks for
corrective or adaptive
maintenance to prioritize for the
next week.

Preventive Maintenance

 Scheduled three times a week (Monday, Wednesday, and Saturday) to ensure the system
remains stable, optimized, and secure. This includes checking system performance,
optimizing the database, and monitoring for vulnerabilities.

Corrective Maintenance
 Focused review of any user-reported issues from the previous week on Tuesday. Critical
bugs are addressed promptly, especially those affecting core functions like booking,
payments, and GPS tracking.

Adaptive Maintenance

 Conducted on Thursday to ensure the system is compatible with external services and
complies with regulatory standards. This includes monitoring for updates in third-party
services or APIs.

Perfective Maintenance

 Implemented on Friday, based on user feedback, for minor enhancements and interface
improvements that can be incorporated into the system. This helps improve the user
experience over time.

Weekly Review and Reporting

 Conducted every Sunday to summarize the week’s maintenance activities, discuss any
unresolved issues, and plan priorities for the following week.

You might also like