1 / 16

ITEC 370

This lecture focuses on the essential strategies for software maintenance after product delivery. It discusses proactive versus reactive maintenance styles, emphasizing the importance of anticipating user needs and adapting to market changes. Key topics include the benefits and downsides of corrective maintenance, user objectives, and testing interfaces. The lecture includes real-world examples, demonstrating how continuous improvement and adaptability can enhance product longevity and user satisfaction. Discover how to decide on a maintenance style that best suits your software development objectives.

brent
Télécharger la présentation

ITEC 370

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITEC 370 Lecture 22 Maintenance

  2. Review • Questions? • Project update on F, next F give prototype demonstration • Interface testing • Checklist of design features • Users

  3. Objectives • Maintenance • What do you do once it is delivered???

  4. Fin • Congrats, you just delivered your product

  5. Now what • Decide on the style of maintenance you want to follow • Reactive • Proactive

  6. Reactive • Status quo and keeping it • Only react when a client requests a fix • Corrective maintenance • Benefits • Less attention required to details • Retraining less of an issue • Downsides • Not good for publicity of product • Miss opportunities

  7. Example • DGL – software created for my dissertation • Used by NIST / VT on a daily basis for 5+ years • No new major development for 5+ years • Bug fixes when a particular problem occurs with an application • No new adopters

  8. When • Good for when clients are not apt to change • Expensive retraining • Manufacturing lines • Call centers • You don’t have the resources to do anymore than is necessary • Buggy updates are bad…

  9. Active • Anticipate what is coming down the road • New software versions and compatibility • Preventative maintenance • Competitors products • Improve on what you currently have • Graphics card drivers

  10. iOS software • App store provides millions of users a chance to find software that smaller developers probably wouldn’t ever have been able to put in front of users • AngryBirds anyone? • Requires a lengthy “validation” by Apple beforehand • Apple changes their platform constantly

  11. Betting on maintenance • World of Warcraft • November 23rd 2004 • Team Fortress 2 • Since 2007, would you like a hat with that? • Halloween themed levels

  12. Numbers • Typically • 25% Adaptive • 20% Corrective • 55% Preventative • In other words, time moves on and so must your software

  13. Lehman’s laws • Continuing change • Increasing complexity • Conservation of familiarity • Continuing growth • Declining quality • Feedback system

  14. Environments • Remember the user’s environment may be different than what you use • Remember your environment’s quirks • Remember staging is your best friend

  15. Update testing • Remember, change causes issues • Deleting/corrupting user data • Clean install • Over-write information • Do you force an overwrite? • Only update the pieces needed?

  16. Review • Reactive • Active

More Related