class_19 - Software Engineering 3156 6-Nov-01 #19:...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
Software Engineering 3156 6-Nov-01 #19: Maintenance and Swing Phil Gross
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Administrativia Prototype status Modify schedule again, give a few more days? Perl Tomorrow 6-8pm No Wednesday class Guest speaker on Thurs
Background image of page 2
3 FYI
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Being a maintenance programmer Lots of maintenance: 67% on average of total time in lifecycle Most difficult: incorporate everything else
Background image of page 4
5 Corrective maintenance Need to debug if fault report is good Deal with regression faults Poor documentation Testing, including regression testing Need to document changes But what about adaptive and perfective maintenance?
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 Even more work… Often, you need new functionality implemented Must go through requirements, specification, …, integration again Or change existing ones Again, lack of documentation Conclusion: you need a good programmer
Background image of page 6
7 And in return… No thanks: if users were happy, they wouldn’t need maintenance User’s problems frequently caused by original developer, but maintainer blamed Original code might be badly written Not a “glamorous job”: drudge work “After-sales service” Needs management help
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
8 Mini-case study Temperate Fruit Committee “We need only 7 fruits” Maintainance “Oh, we actually need 8” Fortunately, hooks were in there Time passes… “We now need 26… you went from 7 to 8, so it must be trivial”
Background image of page 8
9 Case study lessons Problem with product: no provision for expansion Original developer’s fault: “obey” chairman
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 25

class_19 - Software Engineering 3156 6-Nov-01 #19:...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online