1 / 17

The Maintenance Process

The Maintenance Process. Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture. Today. Friday’s lab – How’d it go? Project assignments & what to do next – questions? Tomorrow’s class – Tori HW2 – Thurs Maintenance process - this. Outline. Short Review

elsa
Télécharger la présentation

The Maintenance Process

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. The Maintenance Process Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture

  2. Today • Friday’s lab – How’d it go? • Project assignments & what to do next – questions? • Tomorrow’s class – Tori • HW2 – Thurs • Maintenance process - this

  3. Outline • Short Review • Maintenance Process Models • Quick-fix • Boehm’s • Osborne’s • Iterative • Reuse

  4. Short Review

  5. Software Maintenance Framework Components • User Requirements • Organizational Environment • Operational Environment • Maintenance Process • Software Product • Maintenance Personnel

  6. Maintenance Process(extended to real life) Ingredients of such a process (in general, Steve’s experience): • Processing requests before starting to work on them, like: • Capturing maintenance requests • Investigating those requests – like testing to verify a bug and decide how hard to fix it • Deciding the time / cost to do, getting customer ok • Prioritizing requests – versus other requests! • Assigning to a sub-team to do • Coding and documenting (as per standards) • Testing with various configurations, other legacy code issues • Deciding to send it out (special, or in which sub-release)

  7. An example… • Note the amount of “pre-fixing” & other communication activity! From http://www.indiawebdevelopers.com/CustomerSupport/maintenance_process.asp.

  8. Another example… • Ditto… From http://www.stsc.hill.af.mil/crosstalk/1997/07/stark1.gif.

  9. Basic Strategies for Software Enhancement(one more review topic) • New versions coming out at regular intervals • Ongoing (technical) support – between or instead of releases

  10. The Theoretical Maintenance Process Models Varying sophistication…

  11. Quick-Fix • Advantages • Fast • Can be useful for small projects • Disadvantages • Little or no documentation • Any design becomes less useful over time

  12. Boehm’s • Advantages • Controlled process • Emphasis on feedback • Disadvantage • Slower than quick-fix

  13. Osborne’s • Advantages • Involves all life-cycle phases • Documentation is updated • Disadvantages • Complicated • Lots of Overhead

  14. Iterative • Advantages • Relatively simple • Allows for analysis • Disadvantage • Management decisions are not explicitly included • Appears informally to be on a tilt!

  15. Reuse • Advantages • Can use components from other projects • Code is modular • Disadvantages • Overhead in designing for reuse

  16. Quiz Exercise! Do in small groups…

  17. Steve’s alternative Maintenance process model… • Self-improvement, a 12-step approach (only 6 shown):

More Related