1. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 1 Chapter 16 Maintaining Information Systems

2. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 2 Learning Objectives 7.Explain the role of an analyst in feasibility and requirement analysis.  Explain and contrast four types of maintenance.  Describe several factors that influence the cost of maintaining an information system and apply these factors to the design of maintainable systems.

3. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 3 Learning Objectives  Describe maintenance management issues, including alternative organizational structures, quality measurement, processes for handling change requests, and configuration management.  Explain the role of CASE tools in maintaining information systems.

4. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 4

5. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 5 The Process of Maintaining Information Systems It refers to the process of returning to the beginning of the SDLC and repeating development steps focusing on system change until the change is implemented Maintenance is the longest phase in the SDLC Four major activities:  Obtaining maintenance requests  Transforming requests into changes  Designing changes  Implementing changes

6. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 6 Maintenance is like a mini-SDLC

7. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 7 Types of System Maintenance Corrective maintenance  Changes made to a system to repair flaws in its design, coding, or implementation Adaptive maintenance  Changes made to a system to evolve its functionality to changing business needs or technologies Perfective maintenance  Changes made to a system to add new features or to improve performance Preventive maintenance  Changes made to a system to avoid possible future problems

8. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 8 By far, most maintenance is corrective, and therefore urgent and non-value adding.

9. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 9 The Cost of Maintenance Many organizations allocate eighty percent of information systems budget to maintenance Factors that influence system maintainability:  Latent defects  Number of customers for a given system  Quality of system documentation  Maintenance personnel  Tools  Well-structured programs

10. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 10 A well-documented system is easier to understand, and therefore easier to maintain.

11. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 11 Conducting System Maintenance Managing Maintenance Number of people working in maintenance has surpassed number working in development. Three possible organizational structures:  Separate Maintenance group consists of different personnel than development group.  Combined Developers also maintain systems.  Functional Maintenance personnel work within the functional business unit.

12. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 12 Advantages and Disadvantages Maintenance Organization Type AdvantagesDisadvantages Separate Improved system and documentation quality Ignorance of critical undocumented information Combined Maintenance group knows all about system Less emphasis on good documentation Functional Personnel have vested interest Limited job mobility and human or technical resources

13. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 13 Assignment of Maintenance Personnel Maintenance work is often viewed negatively by IS personnel. Organizations have historically rewarded people involved in new development better than maintenance personnel. Organizations often rotate personnel in and out of maintenance roles in order to lessen negative feelings about maintenance.

14. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 14 Conducting System Maintenance Measures of Effectiveness Important factors to consider  Number of failures  Time between each failure  Type of failure Mean time between failures (MTBF)  It is a measurement of error occurrences that can be tracked over time to indicate the quality of a system

15. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 15 Expect lots of failures early, but as corrective maintenance takes place, error rate should decrease rapidly

16. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 16 Maintenance requests can be frequent Prioritize based on type and urgency of request Controlling Maintenance Requests

17. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 17 Evaluations are based on feasibility analysis The Flow of a Maintenance Request

18. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 18 Configuration Management The process of assuring that only authorized changes are made to the system Baseline modules  Software modules that have been tested, documented, and approved to be included in the most recently created version of a system System librarian  A person responsible for controlling the checking out and checking in of baseline modules when a system is being developed or maintained Build routines  Guidelines that list the instructions to construct an executable system from the baseline source code

19. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 19 Configuration Management Tools Special software systems for managing system configuration Controls access to modules in the system library Two types  Revision control: modules labeled as frozen (unchangeable) or floating (checked out by programmer for modification)  Source code control: extend revision control to all interrelated modules Historical changes can be traced and previous versions can be reconstructed

20. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 20 Role of CASE and Automated Development Tools in Maintenance Traditional systems development  Emphasis on coding and testing.  Changes are implemented by coding and testing first.  Documentation is done after maintenance is performed.  Keeping documentation current is often neglected due to time-consuming nature of task. Development with CASE  Emphasis is on design documents.  Changes are implemented in design documents.  Code is regenerated using code generators.  Documentation is updated during maintenance.

21. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 21 Website Maintenance Special considerations  24 X 7 X 365 Nature of continuous availability makes maintenance challenging. Pages under maintenance can be locked. Date and time stamps  Check for broken links  HTML Validation Pages should be processed by a code validation routine before publication.

22. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 22 Website Maintenance Special considerations (continued)  Reregistration When content significantly changes, site may need to be reregistered with search engines  Future Editions Consistency is important to users Post indications of future changes to the site Batch changes

23. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 23 Summary In this chapter you learned how to: 7.Explain the role of an analyst in feasibility and requirement analysis.  Explain and contrast four types of maintenance.  Describe several factors that influence the cost of maintaining an information system and apply these factors to the design of maintainable systems.

24. © 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 3 Slide 24  Describe maintenance management issues, including alternative organizational structures, quality measurement, processes for handling change requests, and configuration management.  Explain the role of CASE tools in maintaining information systems. Summary