From chapter 14, I know that there is no single reason why software is maintained; however, most reasons relate to a desire to evolve system functionality in order to overcome internal processing errors or to better support changing business needs. Thus, maintenance is a fact of life for most systems. This means that maintenance can begin soon after the system is installed. As with the initial design of a system, maintenance activities are not limited only to software changes, but include changes to hardware and business procedures. A question many people have about maintenance relates to how long organizations should maintain a system. Five years? Ten years? Longer? There is no simple answer to this question, but it is most often an issue of economics. In other words, at what point does it make financial sense to discontinue evolving an older system and build or purchase a new one? The focus of a great deal of upper IS management attention is devoted to assessing the trade-offs between maintenance and new development. In this chapter, we will provide you with a better understanding of the maintenance process and describe the types of issues that must be considered when maintaining systems.
The 14 chapter reveals that the maintenance process of SDLC is the last stage, and reveals that SDLC is therefore a cyclic process, so we must enter the first process of the SDLC process to make it a complete cycle. The maintenance process is divided into four stages. This article will further introduce and explain these four stages for understanding. It must also be pointed out that these stages are very important, and any stage cannot be ignored for the success of the maintenance process. Obtaining a repair request is the first procedure, and it is conditional to satisfy it. It uses a formal process where users can submit system change requests. The SSR mentioned earlier in this lesson is a user request for each user of the system. Many companies have a form similar to SSR, they use it for many reasons, and they use this feature extensively to request new features in existing systems. The procedure does require the company to formally declare or designate a person responsible for collecting requests and managing their distribution to maintenance personnel. When a request is received, it must be analyzed to determine how the new request will affect the existing system and how long it will exist. The other process at this stage is to convert the request into a change, then design the change, and finally implement the change. They are implemented in a cycle to achieve the desired changes in the system.
In the process of maintaining the information system, there are actually four activities in the maintenance process. 1. Get maintenance request 2. Convert a request to a change 3. Design change 4. Implement a change When a user submits a system change request using SSR (System Service Request), requests new development, reports a problem, oe requests a new feature in an existing system, you can obtain a maintenance request. Once a request is received, an analysis is performed to understand the scope of the request and how the request/change will affect the system. When a change request is converted to a formal design change, it can be submitted to the maintenance implementation phase. This maintenance process reflects the SDLC and returns to the implementation of the change and is consistently developed on a per-change request basis.
Once an information system is installed, the system is essentially in the maintenance phase of the systems development life cycle (SDLC). When a system is in the maintenance phase, some person within the systems development group is responsible for collecting maintenance requests from system users and other interested parties, such as system auditors, data center and network management staff, and data analysts.
For the maintenance cost of the information system, I am more interested in the part in Chapter 14. Because for many companies, they do not have the ability to independently develop information systems and can only use authorized software. This means that there is no dedicated information system maintenance department within the company, and it needs to be handed over to the supplier for update and maintenance. Most of the fees are more expensive, and this is a cost that many companies cannot avoid. The potential defects of the system, the number of customers that can accommodate him, the quality of system files, maintenance personnel, tools, and well-structured projects will all have a large or small impact on the maintenance cost.
The use of automated maintenance tools in the process of maintaining information systems can improve work efficiency. In the development process of information system, the most time-consuming work is system coding and testing. Moreover, in system maintenance, if the system changes are approved, the code changes and tests are still carried out.In order to solve these problems, many companies have developed automation tools to support system maintenance, which can realize the synchronization of code modification and document update, and provide support for system maintenance. Especially when using some comprehensive CASE development environment, the system can automatically generate all the documentation for system analysis, design, and maintenance. Furthermore, if changes are made to the system design document, the system automatically modifies the code and generates a new version.
This chapter discuss the final phase in the SDLC.During maintenance, systems are changed to rectify internal processing errors or to extend the functionally of the system.How a system is designed and implemented can greatly impact the cost of performing maintenance.The number of unknown errors in a system when it is installed is a primary factor in determining the cost of maintenance,Other factors ,such as the number of separate customers and the quality of documentation, significantly influence maintenance costs.
Another maintenance issue relates to understanding how to measure the quality of the maintenance effort.Most organizations track the frequency ,time, and type of failure and compare performance over time. Because limited resources preclude organizations form performing all maintenance requests, some formal process for reviewing requests must be established to make sure that only those requests deemed consistent with organizational and information systems plans are preformed.
Maintenance personal must be prevented from making unapproved changes to a system,Automated tools are actively employed during maintenance to enable maintenance to be performed on design documents rather than on low-level source code.Reverse engineering and re-engineering tools are used to cover design specifications of older systems.Once recovered,those older systems can then be changed at the design level rather than the source code level,yielding a significant improvement in maintenance personal productivity.
It is during maintenance that the SDLC becomes a life cycle because requests to change a system must first be approved, planned, analyzed, designed, and then implemented.
The Maintenance Process:
1. Obtaining Maintenance Requests
2. Transforming Requests into Changes
3. Designing Changes
4. Implementing Changes
There are several types of maintenance on an information system. Corrective maintenance ,Adaptive maintenance, Adaptive maintenance, and Preventive maintenance. Also. managing maintenance is critical process, As maintenance activities consume more and more of the systems development budget, maintenance management has become increasingly important. Team managers should pay attention to several concerns when they manage maintenance, Managing Maintenance Personnel, Measuring Maintenance Effectiveness, Controlling Maintenance Requests. and Configuration Management. Anyway, Maintenance is the final phase in the SDLC. During maintenance, systems are changed to rectify internal processing errors or to extend the functionality of the system.
There is no single reason for maintaining software; most have to do with changing business requirements. The maintenance process for the SDLC is the last stage, and the SDLC is therefore a circular process. The maintenance process is divided into four phases including obtaining a maintenance request, transforming the request into a change, designing a change, and implementing a change. Especially with some full-blown CASE development environments, the system can automatically generate all the documentation for system analysis, design, and maintenance.
Maintenance is the final phase in the SDLC. During maintenance, systems are changed to rectify internal processing errors or to extend the functionality of the system. Maintenance is where a majority of the financial investment in a system occurs and can span more than 20 years. More and more information systems professionals have devoted their careers to systems maintenance and, as more systems move from initial development into operational use, it is likely that even more professionals will in the future. It is during maintenance that the SDLC becomes a life cycle because requests to change a system must first be approved, planned, analyzed, designed, and then implemented.
The maintenance phase is the last phase of the SDLC. It is here that the SDLC becomes a cycle, with the last activity leading back to the first. This means that the process of maintaining an information system is the process of returning to the beginning of the SDLC and repeating development steps until the change is implemented.
There are four major activities occurring within maintenance:
1. Obtaining maintenance requests
2. Transforming requests into changes
3. Designing changes
4. Implementing changes
There are four major activities occur within maintenance: obtaining maintenance requests, transforming requests into changes, designing changes, implementing changes. Obtaining maintenance requests requires that a formal process be established
whereby users can submit system change requests. Most companies have some sort of document like an SSR to request new development, to report problems, or to request new features within an existing system. When developing the procedures for obtaining maintenance requests, organizations must also specify an individual within the organization to collect these requests and manage their dispersal to maintenance personnel.
The chapter 14 described several factors that influence the cost of maintaining an information system and apply these factors to the design of maintainable systems.
The process of maintaining an information system is the process of returning to the beginning of the SDLC and repeating development steps until the change is implemented. Four major activities occur within maintenance:
1. Obtaining maintenance requests
2. Transforming requests into changes
3. Designing changes
4. Implementing changes
Chapter14 discusses systems maintenance which is the largest systems development expenditure for many organizations. Maintenance is the final stage of the SDLC. During maintenance, the system is changed to correct internal processing errors or to extend the functionality of the system .It is during maintenance that the SDLC becomes a life cycle, as requests to change the system must first be approved, planned, analyzed, designed, and then implemented. Maintenance requests can be one of four types: Corrective, Adaptive, Perfection, and Preventive. How a system is designed and implemented can greatly affect the cost of performing maintenance. When installing a system, the number of unknown errors is a major factor in determining maintenance costs. Other factors, such as the number of unique customers and the quality of documentation, significantly affect maintenance costs. Another maintenance management issue involves measuring the quality of the maintenance effort. Most organizations track the frequency, time, and type of each failure and compare performance over time. Because limited resources prevent the organization from executing all maintenance requests, some formal process for reviewing requests must be established to ensure that only those requests are executed that are deemed to be consistent with the organization’s and information systems plans. A central source (typically the project manager) is used to collect maintenance requests. When requests are submitted, this person forwards each request to a committee that evaluates its value. Once the assessment is done, the project manager assigns higher priority activities to the maintenance staff.
There are four activities in maintaining an information system. You can obtain a maintenance request when a user submits a system change request using SSR (System Service Request), requesting new development, reporting problems, or requesting new “features” in an existing system. Once the request is received, it is analyzed to understand the scope of the request and how the request/change will affect the system. Once the change request has been transformed into a formal design change, it can be submitted to the maintenance implementation phase. This maintenance process reflects the SDLC and goes back to the implementation of the changes and is developed on a per-change request basis.
Maintenance is the final phase in the SDLC. During maintenance,systems are changed to rectify internal processing errors or to extend the functionality of the system.There are four major activities occur within maintenance:1)Obtaining maintenance requests; 2)Transforming requests into changes; 3)Designing changes; 4)Implementing changes.
There are four types of maintenance:Corrective;Adaptive;Perfective;Preventive.
At the same time, I learned that how a system is designed and implemented can greatly impact the cost of performing maintenance. The number of unknown errors in a system when it is installed is a primary factor in determining the cost of maintenance.
There are four steps in the maintenance process, and they are obtaining maintenance requests, transforming requests into changes, designing changes, and implementing changes, which matches SDLC phases correspondingly which are planning, analysis, design, implementation, and maintenance. Maintenance is basically like going through mini versions of the SDLC, since we need to ensure that everything is running as it should. Any changes that need to be made to the system during maintenance need to be considered as a whole, not just as one aspect of the system itself.
According to the article of the Chapter 14 “Maintaining Information Systems of MSAD, I am interested in the content about the governance of the system, which has the following steps:
At the beginning, to accept the request of maintenance from the system users.
In addition, to change the maintenance request to become the action of revising some parts of the system.
Thirdly, to establish a plan to design in the field of revising the parts of the system.
At last, to perform the plan in order to handle the problems exist in the system in the real environment.
Maintenance is the last stage of SDLC, which makes it a complete cycle. Maintenance includes all activities performed after the software is installed, mainly involving the following four main aspects: 1.obtaining maintenance requests, 2.transforming requests into changes, 3.designing changes, 4.implementing changes.
Maintenance is a vital activity that connects the user’s or customer’s experience with the product delivery organization. Maintenance may be the longest stage in the SDLC, because the speed of technical changes is fast, and system maintenance must be carried out for each update. For example, for large systems, it is very difficult to eliminate all faults before delivery. Correcting these errors due to involvement, coding or implementation becomes extremely important. At the same time, adaptive maintenance (solving changes to the system and platform due to changes in the operating environment or business requirements), comprehensive maintenance (optimizing, deleting or adding new functions to change system functions) and preventive maintenance (executing activities to prevent errors and system failure) are necessary for the success and development of the system.
The final start does not mean the end of the life of the information system, but should be kept up to date and continue to achieve the expected goals.
The Process of Maintaining Information Systems. The maintenance phase is the last phase of the SDLC. It is here that the SDLC becomes a cycle, with the last activity leading back to the first. This means that the process of maintaining an information system is the process of returning to the beginning of the SDLC and repeating development steps until the change is implemented.
1. Obtain a maintenance request 2. Convert the request into a change 3. Design change 4. Implement a change When a user submits a system change request using SSR (System Service Request), request new development, report a problem, or request a new existing system You can get the maintenance request in the “Features”. After receiving the request, an analysis will be performed to understand the scope of the request and how the request/change will affect the system. After the change request is converted into a formal design change, it can be submitted to the maintenance implementation phase. The maintenance process reflects the SDLC and returns to the change implementation process, and continuous development is carried out on the basis of each change request.
The seventh and final stages involve maintenance and regular updates. In this step, the end user can fine-tune the system as needed to improve performance, add new features or meet other user needs.
Software operation and maintenance phase: It is the longest phase in the software life cycle, including error-correcting maintenance and improving maintenance.
Once an information system is installed, the system is
essentially in the maintenance phase of the systems development life cycle (SDLC). When a system is in the maintenance phase, some person within the systems development
group is responsible for collecting maintenance requests
from system users and other interested parties, such as
system auditors, data center and network management
staff, and data analysts. Once collected, each request is
analyzed to better understand how it will alter the system
and what business benefits and necessities will result from
such a change. If the change request is approved, a system
change is designed and then implemented. As with the
initial development of the system, implemented changes
are formally reviewed and tested before installation into
operational systems.
Chapter 14 reveals that the maintenance process of SDLC is the last stage and that SDLC is therefore a cyclic process. In the beginning, we will do system coding and testing. Moreover, in system maintenance, code changes and testing are still required if system changes are approved. Another maintenance issue involves understanding how to measure the quality of maintenance work. Most organizations track the frequency, timing, and type of failure and compare performance over time. This is the best way to achieve the best effect. Due to limited resources, the organization is unable to perform all maintenance requests, so some formal review request processes must be established to ensure that only those requests that are considered to be consistent with the organization and information system plans are executed. Central resources (usually the project manager) are used to collect maintenance requests. After submitting the request, the person forwards each request to the committee that evaluates its value. After the evaluation is completed, the project manager assigns higher priority activities to the maintenance staff.
Chapter 14 introduces the process of maintaining information systems, the final phase of the systems development life cycle.
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 me 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.
The maintenance phase is the last phase of SDLC. There are four main activities:
1. Obtain maintenance request: A formal process needs to be established through which users can submit system change requests. Most companies have some SSR-like documents that are used to request new development, report problems, or request new features in existing systems.
2. Convert the request into a change: Once the request is received, it must be analyzed to understand the scope of the request. It must be determined how the request will affect the current system and how long such a project will take. Next, the change request can be converted into a formal design change, and then sent to the maintenance implementation phase.
3. Design changes: Because most organizations file previous versions of the system, all previous programs and documents must be saved to ensure correct version control of the system. This allows the previous version of the system to be recreated when needed.
4. Implementation changes: maintenance reuses most of the existing system modules when generating new system versions
Then four kinds of maintenance are introduced:
Maintenance: Changes made to the system to repair defects in design, coding, or implementation.
1.Adaptive maintenance: Changes made to the system to develop its functions to adapt to changing business needs or technologies.
2.Completed maintenance: Changes made to the system to add new features or improve performance.
3.Corrective maintenance: refers to changes made to repair defects in system design, coding, or implementation.
4.Adaptive maintenance: involves making changes to the information system to develop its functions to adapt to changing business needs, or to migrate it to a different operating environment.
Ying Cheng says
From chapter 14, I know that there is no single reason why software is maintained; however, most reasons relate to a desire to evolve system functionality in order to overcome internal processing errors or to better support changing business needs. Thus, maintenance is a fact of life for most systems. This means that maintenance can begin soon after the system is installed. As with the initial design of a system, maintenance activities are not limited only to software changes, but include changes to hardware and business procedures. A question many people have about maintenance relates to how long organizations should maintain a system. Five years? Ten years? Longer? There is no simple answer to this question, but it is most often an issue of economics. In other words, at what point does it make financial sense to discontinue evolving an older system and build or purchase a new one? The focus of a great deal of upper IS management attention is devoted to assessing the trade-offs between maintenance and new development. In this chapter, we will provide you with a better understanding of the maintenance process and describe the types of issues that must be considered when maintaining systems.
Lei Tian says
The 14 chapter reveals that the maintenance process of SDLC is the last stage, and reveals that SDLC is therefore a cyclic process, so we must enter the first process of the SDLC process to make it a complete cycle. The maintenance process is divided into four stages. This article will further introduce and explain these four stages for understanding. It must also be pointed out that these stages are very important, and any stage cannot be ignored for the success of the maintenance process. Obtaining a repair request is the first procedure, and it is conditional to satisfy it. It uses a formal process where users can submit system change requests. The SSR mentioned earlier in this lesson is a user request for each user of the system. Many companies have a form similar to SSR, they use it for many reasons, and they use this feature extensively to request new features in existing systems. The procedure does require the company to formally declare or designate a person responsible for collecting requests and managing their distribution to maintenance personnel. When a request is received, it must be analyzed to determine how the new request will affect the existing system and how long it will exist. The other process at this stage is to convert the request into a change, then design the change, and finally implement the change. They are implemented in a cycle to achieve the desired changes in the system.
Yu Hu says
In the process of maintaining the information system, there are actually four activities in the maintenance process. 1. Get maintenance request 2. Convert a request to a change 3. Design change 4. Implement a change When a user submits a system change request using SSR (System Service Request), requests new development, reports a problem, oe requests a new feature in an existing system, you can obtain a maintenance request. Once a request is received, an analysis is performed to understand the scope of the request and how the request/change will affect the system. When a change request is converted to a formal design change, it can be submitted to the maintenance implementation phase. This maintenance process reflects the SDLC and returns to the implementation of the change and is consistently developed on a per-change request basis.
Chang Cui says
Once an information system is installed, the system is essentially in the maintenance phase of the systems development life cycle (SDLC). When a system is in the maintenance phase, some person within the systems development group is responsible for collecting maintenance requests from system users and other interested parties, such as system auditors, data center and network management staff, and data analysts.
Yijing Zhan says
For the maintenance cost of the information system, I am more interested in the part in Chapter 14. Because for many companies, they do not have the ability to independently develop information systems and can only use authorized software. This means that there is no dedicated information system maintenance department within the company, and it needs to be handed over to the supplier for update and maintenance. Most of the fees are more expensive, and this is a cost that many companies cannot avoid. The potential defects of the system, the number of customers that can accommodate him, the quality of system files, maintenance personnel, tools, and well-structured projects will all have a large or small impact on the maintenance cost.
Xiaohan Chen says
The use of automated maintenance tools in the process of maintaining information systems can improve work efficiency. In the development process of information system, the most time-consuming work is system coding and testing. Moreover, in system maintenance, if the system changes are approved, the code changes and tests are still carried out.In order to solve these problems, many companies have developed automation tools to support system maintenance, which can realize the synchronization of code modification and document update, and provide support for system maintenance. Especially when using some comprehensive CASE development environment, the system can automatically generate all the documentation for system analysis, design, and maintenance. Furthermore, if changes are made to the system design document, the system automatically modifies the code and generates a new version.
Yujia Hu says
This chapter discuss the final phase in the SDLC.During maintenance, systems are changed to rectify internal processing errors or to extend the functionally of the system.How a system is designed and implemented can greatly impact the cost of performing maintenance.The number of unknown errors in a system when it is installed is a primary factor in determining the cost of maintenance,Other factors ,such as the number of separate customers and the quality of documentation, significantly influence maintenance costs.
Another maintenance issue relates to understanding how to measure the quality of the maintenance effort.Most organizations track the frequency ,time, and type of failure and compare performance over time. Because limited resources preclude organizations form performing all maintenance requests, some formal process for reviewing requests must be established to make sure that only those requests deemed consistent with organizational and information systems plans are preformed.
Maintenance personal must be prevented from making unapproved changes to a system,Automated tools are actively employed during maintenance to enable maintenance to be performed on design documents rather than on low-level source code.Reverse engineering and re-engineering tools are used to cover design specifications of older systems.Once recovered,those older systems can then be changed at the design level rather than the source code level,yielding a significant improvement in maintenance personal productivity.
Haoyu Bai says
It is during maintenance that the SDLC becomes a life cycle because requests to change a system must first be approved, planned, analyzed, designed, and then implemented.
The Maintenance Process:
1. Obtaining Maintenance Requests
2. Transforming Requests into Changes
3. Designing Changes
4. Implementing Changes
Yiqiong Zhang says
There are several types of maintenance on an information system. Corrective maintenance ,Adaptive maintenance, Adaptive maintenance, and Preventive maintenance. Also. managing maintenance is critical process, As maintenance activities consume more and more of the systems development budget, maintenance management has become increasingly important. Team managers should pay attention to several concerns when they manage maintenance, Managing Maintenance Personnel, Measuring Maintenance Effectiveness, Controlling Maintenance Requests. and Configuration Management. Anyway, Maintenance is the final phase in the SDLC. During maintenance, systems are changed to rectify internal processing errors or to extend the functionality of the system.
Yalin Zou says
There is no single reason for maintaining software; most have to do with changing business requirements. The maintenance process for the SDLC is the last stage, and the SDLC is therefore a circular process. The maintenance process is divided into four phases including obtaining a maintenance request, transforming the request into a change, designing a change, and implementing a change. Especially with some full-blown CASE development environments, the system can automatically generate all the documentation for system analysis, design, and maintenance.
Xiaomeng Chen says
Maintenance is the final phase in the SDLC. During maintenance, systems are changed to rectify internal processing errors or to extend the functionality of the system. Maintenance is where a majority of the financial investment in a system occurs and can span more than 20 years. More and more information systems professionals have devoted their careers to systems maintenance and, as more systems move from initial development into operational use, it is likely that even more professionals will in the future. It is during maintenance that the SDLC becomes a life cycle because requests to change a system must first be approved, planned, analyzed, designed, and then implemented.
Tianyu Zhang says
The maintenance phase is the last phase of the SDLC. It is here that the SDLC becomes a cycle, with the last activity leading back to the first. This means that the process of maintaining an information system is the process of returning to the beginning of the SDLC and repeating development steps until the change is implemented.
There are four major activities occurring within maintenance:
1. Obtaining maintenance requests
2. Transforming requests into changes
3. Designing changes
4. Implementing changes
Zhiyuan Lian says
There are four major activities occur within maintenance: obtaining maintenance requests, transforming requests into changes, designing changes, implementing changes. Obtaining maintenance requests requires that a formal process be established
whereby users can submit system change requests. Most companies have some sort of document like an SSR to request new development, to report problems, or to request new features within an existing system. When developing the procedures for obtaining maintenance requests, organizations must also specify an individual within the organization to collect these requests and manage their dispersal to maintenance personnel.
Shengyuan Yu says
The chapter 14 described several factors that influence the cost of maintaining an information system and apply these factors to the design of maintainable systems.
The process of maintaining an information system is the process of returning to the beginning of the SDLC and repeating development steps until the change is implemented. Four major activities occur within maintenance:
1. Obtaining maintenance requests
2. Transforming requests into changes
3. Designing changes
4. Implementing changes
Yongheng Luo says
Chapter14 discusses systems maintenance which is the largest systems development expenditure for many organizations. Maintenance is the final stage of the SDLC. During maintenance, the system is changed to correct internal processing errors or to extend the functionality of the system .It is during maintenance that the SDLC becomes a life cycle, as requests to change the system must first be approved, planned, analyzed, designed, and then implemented. Maintenance requests can be one of four types: Corrective, Adaptive, Perfection, and Preventive. How a system is designed and implemented can greatly affect the cost of performing maintenance. When installing a system, the number of unknown errors is a major factor in determining maintenance costs. Other factors, such as the number of unique customers and the quality of documentation, significantly affect maintenance costs. Another maintenance management issue involves measuring the quality of the maintenance effort. Most organizations track the frequency, time, and type of each failure and compare performance over time. Because limited resources prevent the organization from executing all maintenance requests, some formal process for reviewing requests must be established to ensure that only those requests are executed that are deemed to be consistent with the organization’s and information systems plans. A central source (typically the project manager) is used to collect maintenance requests. When requests are submitted, this person forwards each request to a committee that evaluates its value. Once the assessment is done, the project manager assigns higher priority activities to the maintenance staff.
Yuting Yang says
There are four activities in maintaining an information system. You can obtain a maintenance request when a user submits a system change request using SSR (System Service Request), requesting new development, reporting problems, or requesting new “features” in an existing system. Once the request is received, it is analyzed to understand the scope of the request and how the request/change will affect the system. Once the change request has been transformed into a formal design change, it can be submitted to the maintenance implementation phase. This maintenance process reflects the SDLC and goes back to the implementation of the changes and is developed on a per-change request basis.
Yanxue Li says
Maintenance is the final phase in the SDLC. During maintenance,systems are changed to rectify internal processing errors or to extend the functionality of the system.There are four major activities occur within maintenance:1)Obtaining maintenance requests; 2)Transforming requests into changes; 3)Designing changes; 4)Implementing changes.
There are four types of maintenance:Corrective;Adaptive;Perfective;Preventive.
At the same time, I learned that how a system is designed and implemented can greatly impact the cost of performing maintenance. The number of unknown errors in a system when it is installed is a primary factor in determining the cost of maintenance.
Zijie Yuan says
There are four steps in the maintenance process, and they are obtaining maintenance requests, transforming requests into changes, designing changes, and implementing changes, which matches SDLC phases correspondingly which are planning, analysis, design, implementation, and maintenance. Maintenance is basically like going through mini versions of the SDLC, since we need to ensure that everything is running as it should. Any changes that need to be made to the system during maintenance need to be considered as a whole, not just as one aspect of the system itself.
Yutong Sun says
According to the article of the Chapter 14 “Maintaining Information Systems of MSAD, I am interested in the content about the governance of the system, which has the following steps:
At the beginning, to accept the request of maintenance from the system users.
In addition, to change the maintenance request to become the action of revising some parts of the system.
Thirdly, to establish a plan to design in the field of revising the parts of the system.
At last, to perform the plan in order to handle the problems exist in the system in the real environment.
Xuemeng Li says
Maintenance is the last stage of SDLC, which makes it a complete cycle. Maintenance includes all activities performed after the software is installed, mainly involving the following four main aspects: 1.obtaining maintenance requests, 2.transforming requests into changes, 3.designing changes, 4.implementing changes.
Maintenance is a vital activity that connects the user’s or customer’s experience with the product delivery organization. Maintenance may be the longest stage in the SDLC, because the speed of technical changes is fast, and system maintenance must be carried out for each update. For example, for large systems, it is very difficult to eliminate all faults before delivery. Correcting these errors due to involvement, coding or implementation becomes extremely important. At the same time, adaptive maintenance (solving changes to the system and platform due to changes in the operating environment or business requirements), comprehensive maintenance (optimizing, deleting or adding new functions to change system functions) and preventive maintenance (executing activities to prevent errors and system failure) are necessary for the success and development of the system.
The final start does not mean the end of the life of the information system, but should be kept up to date and continue to achieve the expected goals.
Yue Ma says
The Process of Maintaining Information Systems. The maintenance phase is the last phase of the SDLC. It is here that the SDLC becomes a cycle, with the last activity leading back to the first. This means that the process of maintaining an information system is the process of returning to the beginning of the SDLC and repeating development steps until the change is implemented.
Dacheng Xu says
1. Obtain a maintenance request 2. Convert the request into a change 3. Design change 4. Implement a change When a user submits a system change request using SSR (System Service Request), request new development, report a problem, or request a new existing system You can get the maintenance request in the “Features”. After receiving the request, an analysis will be performed to understand the scope of the request and how the request/change will affect the system. After the change request is converted into a formal design change, it can be submitted to the maintenance implementation phase. The maintenance process reflects the SDLC and returns to the change implementation process, and continuous development is carried out on the basis of each change request.
Shengjie Zhang says
The seventh and final stages involve maintenance and regular updates. In this step, the end user can fine-tune the system as needed to improve performance, add new features or meet other user needs.
Software operation and maintenance phase: It is the longest phase in the software life cycle, including error-correcting maintenance and improving maintenance.
Lisheng Lin says
Once an information system is installed, the system is
essentially in the maintenance phase of the systems development life cycle (SDLC). When a system is in the maintenance phase, some person within the systems development
group is responsible for collecting maintenance requests
from system users and other interested parties, such as
system auditors, data center and network management
staff, and data analysts. Once collected, each request is
analyzed to better understand how it will alter the system
and what business benefits and necessities will result from
such a change. If the change request is approved, a system
change is designed and then implemented. As with the
initial development of the system, implemented changes
are formally reviewed and tested before installation into
operational systems.
Ziqiao Wang says
Chapter 14 reveals that the maintenance process of SDLC is the last stage and that SDLC is therefore a cyclic process. In the beginning, we will do system coding and testing. Moreover, in system maintenance, code changes and testing are still required if system changes are approved. Another maintenance issue involves understanding how to measure the quality of maintenance work. Most organizations track the frequency, timing, and type of failure and compare performance over time. This is the best way to achieve the best effect. Due to limited resources, the organization is unable to perform all maintenance requests, so some formal review request processes must be established to ensure that only those requests that are considered to be consistent with the organization and information system plans are executed. Central resources (usually the project manager) are used to collect maintenance requests. After submitting the request, the person forwards each request to the committee that evaluates its value. After the evaluation is completed, the project manager assigns higher priority activities to the maintenance staff.
Weiwei Zhao says
Chapter 14 introduces the process of maintaining information systems, the final phase of the systems development life cycle.
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 me 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.
Hang Zhao says
The maintenance phase is the last phase of SDLC. There are four main activities:
1. Obtain maintenance request: A formal process needs to be established through which users can submit system change requests. Most companies have some SSR-like documents that are used to request new development, report problems, or request new features in existing systems.
2. Convert the request into a change: Once the request is received, it must be analyzed to understand the scope of the request. It must be determined how the request will affect the current system and how long such a project will take. Next, the change request can be converted into a formal design change, and then sent to the maintenance implementation phase.
3. Design changes: Because most organizations file previous versions of the system, all previous programs and documents must be saved to ensure correct version control of the system. This allows the previous version of the system to be recreated when needed.
4. Implementation changes: maintenance reuses most of the existing system modules when generating new system versions
Then four kinds of maintenance are introduced:
Maintenance: Changes made to the system to repair defects in design, coding, or implementation.
1.Adaptive maintenance: Changes made to the system to develop its functions to adapt to changing business needs or technologies.
2.Completed maintenance: Changes made to the system to add new features or improve performance.
3.Corrective maintenance: refers to changes made to repair defects in system design, coding, or implementation.
4.Adaptive maintenance: involves making changes to the information system to develop its functions to adapt to changing business needs, or to migrate it to a different operating environment.