The Maintenance Process Steve Chenoweth CSSE 375 RoseHulman

  • Slides: 17
Download presentation
The Maintenance Process Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture

The Maintenance Process Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture 1

Today Friday’s lab – How’d it go? n Project assignments & what to do

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

Outline n Short Review n Maintenance Process Models n n n Quick-fix Boehm’s Osborne’s

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

Short Review 4

Short Review 4

Software Maintenance Framework Components n n n User Requirements Organizational Environment Operational Environment Maintenance

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

Maintenance Process (extended to real life) Ingredients of such a process (in general, Steve’s

Maintenance Process (extended to real life) Ingredients of such a process (in general, Steve’s experience): n Processing requests before starting to work on them, like: w w w n n n 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) 6

An example… n Note the amount of “pre -fixing” & other communication activity! From

An example… n Note the amount of “pre -fixing” & other communication activity! From http: //www. indiawebdeveloper s. com/Customer. Support/maint enance_process. asp. 7

Another example… n Ditto… From http: //www. stsc. hill. af. mil/crosstalk/1997/07/stark 1. gif. 8

Another example… n Ditto… From http: //www. stsc. hill. af. mil/crosstalk/1997/07/stark 1. gif. 8

Basic Strategies for Software Enhancement (one more review topic) n n New versions coming

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

The Theoretical Maintenance Process Models Varying sophistication… 10

The Theoretical Maintenance Process Models Varying sophistication… 10

Quick-Fix n Advantages n n n Fast Can be useful for small projects Disadvantages

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

Boehm’s n Advantages n n n Controlled process Emphasis on feedback Disadvantage n Slower

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

Osborne’s n Advantages n Involves all life -cycle phases n Documentation is updated n

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

Iterative n Advantages n n n Relatively simple Allows for analysis Disadvantage n n

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

Reuse n Advantages n n n Can use components from other projects Code is

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

Quiz Exercise! Do in small groups… 16

Quiz Exercise! Do in small groups… 16

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

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