Instructor Manual for
Modern Systems Analysis and
Design, 9th Edition By Joseph
Valacich, Joey George, Jeffrey
Hoffer
(All Chapters 1-14, 100% Original
Verified, A+ Grade)
All Chapters Arranged Reverse: 14-1
This is the Original Instructor Manual
for 9th Edition, All Other Files in the
Market are Wrong/Old Questions.
,Chapter 14 Modern Systems Analysis and Design, 9th edition Instructor’s Manual
Chapter 14
Maintaining Information Systems
Chapter Overview
Chapter 14 introduces students to the process of maintaining information systems, the final phase of
the systems development life cycle. This chapter is not found in many traditional system analysis
and design textbooks, even though maintenance is where most of the financial investment in a
system occurs. More information systems professionals are devoting their careers to systems
maintenance. Also, as more systems move from initial development into operational use, it is likely
that even more professionals will work in maintenance-related activities in the future. This chapter
links maintenance to the SDLC and describes the four types of maintenance requests: corrective,
adaptive, perfective, and preventive. After describing the types and costs of maintenance, the
chapter describes several managerial issues related to system maintenance. The chapter concludes
by describing the role of CASE in maintenance, discussing Web site maintenance, and examining
the maintenance process at Pine Valley Furniture’s WebStore. The topics presented in this chapter
are very important for students to understand because they represent the most prominent systems
development activity, an activity that many students are likely to encounter. The impact of CASE
tools and their use in reverse engineering and reengineering should also be discussed as the future of
maintenance of systems and how they minimize costs and allow the more rapid deployment of
modified and extensible systems.
Instructional Objectives
Specific student learning objectives are included at the beginning of the chapter. From an
instructor's point of view, the objectives of this chapter are to:
1. Explain and contrast four types of maintenance.
2. Describe several factors that influence the cost of maintaining an information system and apply
these factors to the design of maintainable systems.
3. Describe maintenance management issues, including alternative organizational structures,
quality measurement, handling change requests, and configuration management.
1
Copyright © 2020 Pearson Education
,Chapter 14 Modern Systems Analysis and Design, 9th edition Instructor’s Manual
Classroom Ideas
1. Chapter 14 introduces concepts and terms central to understanding the maintenance of
information systems. Discuss Review Question 2 in class, because it encourages students to
compare several key terms. Also, ask your students to review the key terms listed at the end of
the chapter.
2. During a lecture, an effective way to focus the discussion on issues surrounding system
maintenance is to use the tables and figures in the chapter. Figures 14-2, 14-4, 14-5, and 14-6,
as well as Table 14-2, work very well as a basis for class discussion.
3. An alternative method to presenting the chapter material is to lecture from the Review
Questions, Problems and Exercises, and Field Exercises. Pose selected questions to your
students, helping focus a discussion on specific concepts. Problems and Exercises 14.26, 14.27,
14.28, 14.30, and 14.33 and Field Exercise 14.35 are good motivators for class discussion.
4. Another very effective in-class exercise is to ask students who have maintained an information
system to compare their experiences to the concepts presented in Chapter 13. This discussion is
a good way to elaborate on key system maintenance issues.
5. If you have access to practicing systems analysts, an insightful activity is to invite these
analysts into your class to discuss how maintenance is managed in their organization.
6. A hot topic in the systems world is software delivery via the Internet. Have your students
locate articles relating to this topic and discuss their articles in class. Ask your students to
discuss maintenance as it relates to software delivery via the Internet.
2
Copyright © 2020 Pearson Education
, Chapter 14 Modern Systems Analysis and Design, 9th edition Instructor’s Manual
Answers to Key Terms
Suggested answers are provided below. These answers are presented top-down, left to right by page.
14.7. Maintenance
14.5. Corrective maintenance 14.13. System librarian
14.1. Adaptive maintenance 14.3. Build routines
14.9. Perfective maintenance 14.12. Reverse engineering
14.10. Preventive maintenance 14.11. Reengineering
14.6. Maintainability
14.8. Mean time between failures
(MTBF)
14.4. Configuration management
14.2. Baseline modules
Answers to Review Questions
14.14.
a. Adaptive maintenance refers to the changes made to a system to evolve its functionality to
changing business needs or technologies. Corrective maintenance refers to changes made to
a system to repair flaws in its design, coding, or implementation. Perfective maintenance
refers to changes made to a system to add new features or to improve performance.
Preventive maintenance refers to changes made to a system to avoid possible future
problems.
b. Baseline modules are software modules that have been tested, documented, and approved to
be included in the most recently created version of a system. Build routines are the
guidelines that list the instructions to construct an executable system from the baseline
source code. The system librarian is the person responsible for controlling the checking-out
and checking-in of baseline modules for a system when a system is being developed or
maintained.
c. Maintenance refers to the changes made to a system to fix or enhance its functionality.
Maintainability refers to the ease with which software can be understood, corrected,
adapted, and enhanced.
14.15. Four major activities occur within maintenance: 1) obtaining maintenance requests, 2)
transforming requests into changes, 3) designing changes, and 4) implementing changes. The
first phase of the SDLC, project identification and selection, is analogous to the maintenance
process of obtaining a maintenance request. The SDLC phases of project initiation and
planning and analysis are analogous to the maintenance process of transforming requests into a
specific system change. The design phase of the SDLC equates to the designing changes
process. Finally, the SDLC phase implementation equates to implementing changes. This
3
Copyright © 2020 Pearson Education
Modern Systems Analysis and
Design, 9th Edition By Joseph
Valacich, Joey George, Jeffrey
Hoffer
(All Chapters 1-14, 100% Original
Verified, A+ Grade)
All Chapters Arranged Reverse: 14-1
This is the Original Instructor Manual
for 9th Edition, All Other Files in the
Market are Wrong/Old Questions.
,Chapter 14 Modern Systems Analysis and Design, 9th edition Instructor’s Manual
Chapter 14
Maintaining Information Systems
Chapter Overview
Chapter 14 introduces students to the process of maintaining information systems, the final phase of
the systems development life cycle. This chapter is not found in many traditional system analysis
and design textbooks, even though maintenance is where most of the financial investment in a
system occurs. More information systems professionals are devoting their careers to systems
maintenance. Also, as more systems move from initial development into operational use, it is likely
that even more professionals will work in maintenance-related activities in the future. This chapter
links maintenance to the SDLC and describes the four types of maintenance requests: corrective,
adaptive, perfective, and preventive. After describing the types and costs of maintenance, the
chapter describes several managerial issues related to system maintenance. The chapter concludes
by describing the role of CASE in maintenance, discussing Web site maintenance, and examining
the maintenance process at Pine Valley Furniture’s WebStore. The topics presented in this chapter
are very important for students to understand because they represent the most prominent systems
development activity, an activity that many students are likely to encounter. The impact of CASE
tools and their use in reverse engineering and reengineering should also be discussed as the future of
maintenance of systems and how they minimize costs and allow the more rapid deployment of
modified and extensible systems.
Instructional Objectives
Specific student learning objectives are included at the beginning of the chapter. From an
instructor's point of view, the objectives of this chapter are to:
1. Explain and contrast four types of maintenance.
2. Describe several factors that influence the cost of maintaining an information system and apply
these factors to the design of maintainable systems.
3. Describe maintenance management issues, including alternative organizational structures,
quality measurement, handling change requests, and configuration management.
1
Copyright © 2020 Pearson Education
,Chapter 14 Modern Systems Analysis and Design, 9th edition Instructor’s Manual
Classroom Ideas
1. Chapter 14 introduces concepts and terms central to understanding the maintenance of
information systems. Discuss Review Question 2 in class, because it encourages students to
compare several key terms. Also, ask your students to review the key terms listed at the end of
the chapter.
2. During a lecture, an effective way to focus the discussion on issues surrounding system
maintenance is to use the tables and figures in the chapter. Figures 14-2, 14-4, 14-5, and 14-6,
as well as Table 14-2, work very well as a basis for class discussion.
3. An alternative method to presenting the chapter material is to lecture from the Review
Questions, Problems and Exercises, and Field Exercises. Pose selected questions to your
students, helping focus a discussion on specific concepts. Problems and Exercises 14.26, 14.27,
14.28, 14.30, and 14.33 and Field Exercise 14.35 are good motivators for class discussion.
4. Another very effective in-class exercise is to ask students who have maintained an information
system to compare their experiences to the concepts presented in Chapter 13. This discussion is
a good way to elaborate on key system maintenance issues.
5. If you have access to practicing systems analysts, an insightful activity is to invite these
analysts into your class to discuss how maintenance is managed in their organization.
6. A hot topic in the systems world is software delivery via the Internet. Have your students
locate articles relating to this topic and discuss their articles in class. Ask your students to
discuss maintenance as it relates to software delivery via the Internet.
2
Copyright © 2020 Pearson Education
, Chapter 14 Modern Systems Analysis and Design, 9th edition Instructor’s Manual
Answers to Key Terms
Suggested answers are provided below. These answers are presented top-down, left to right by page.
14.7. Maintenance
14.5. Corrective maintenance 14.13. System librarian
14.1. Adaptive maintenance 14.3. Build routines
14.9. Perfective maintenance 14.12. Reverse engineering
14.10. Preventive maintenance 14.11. Reengineering
14.6. Maintainability
14.8. Mean time between failures
(MTBF)
14.4. Configuration management
14.2. Baseline modules
Answers to Review Questions
14.14.
a. Adaptive maintenance refers to the changes made to a system to evolve its functionality to
changing business needs or technologies. Corrective maintenance refers to changes made to
a system to repair flaws in its design, coding, or implementation. Perfective maintenance
refers to changes made to a system to add new features or to improve performance.
Preventive maintenance refers to changes made to a system to avoid possible future
problems.
b. Baseline modules are software modules that have been tested, documented, and approved to
be included in the most recently created version of a system. Build routines are the
guidelines that list the instructions to construct an executable system from the baseline
source code. The system librarian is the person responsible for controlling the checking-out
and checking-in of baseline modules for a system when a system is being developed or
maintained.
c. Maintenance refers to the changes made to a system to fix or enhance its functionality.
Maintainability refers to the ease with which software can be understood, corrected,
adapted, and enhanced.
14.15. Four major activities occur within maintenance: 1) obtaining maintenance requests, 2)
transforming requests into changes, 3) designing changes, and 4) implementing changes. The
first phase of the SDLC, project identification and selection, is analogous to the maintenance
process of obtaining a maintenance request. The SDLC phases of project initiation and
planning and analysis are analogous to the maintenance process of transforming requests into a
specific system change. The design phase of the SDLC equates to the designing changes
process. Finally, the SDLC phase implementation equates to implementing changes. This
3
Copyright © 2020 Pearson Education
