Systems Maintenance
Systems Maintenance
David L Story
CMGT 555
July 27, 2015
MANNIL KRISHNAKUMAR
Systems Maintenance
As advances in technology occur, maintenance of systems and software become more prevalent. The design or upgrade of a system will tell what type of maintenance will be needed in the future, because the upgrade will have failure as equipment is replaced, and new designs will have configurations or tweaks that need to be done after implement.
In previous weeks we touched on system developments, feasibility study, entities and attributes, design and security, and now system maintenance. System maintenance is a very important aspect of any infrastructure and consumes 60 to 80% of I.T.’s budget. It is the hardware and software that has to be maintained in order to keep everything running smoothly and keep the company profitable.
Functionality, reliability, usability, efficiency, scalability and maintainability are what drive up the cost of maintenance. And what I mean by this is, in order to keep a system or the software on the system running at peak performance, CM’s (change management) need to be done on a regular basis. When I worked for Amazon, they were always making changes to the system or the software so the customers and the employee’s would have the system to use without any issues.
Though planning and feasibility, which is the start of any project, a designer can make the system low maintenance and efficient and still keep with in the budget. But with any new system or software, there is no way to keep them unaltered throughout the life cycle. This is why there will always be changes and or upgrades of the system and software throughout the development phase.
According to Mallach (2013, July 3), “An information system consists of five components,” e.g., hardware, software, data, procedures and people who are the end-users of the system. The two components: the hardware and software require consistent maintenance as they are susceptible to faults (Kadel,
David L Story
CMGT 555
July 27, 2015
MANNIL KRISHNAKUMAR
Systems Maintenance
As advances in technology occur, maintenance of systems and software become more prevalent. The design or upgrade of a system will tell what type of maintenance will be needed in the future, because the upgrade will have failure as equipment is replaced, and new designs will have configurations or tweaks that need to be done after implement.
In previous weeks we touched on system developments, feasibility study, entities and attributes, design and security, and now system maintenance. System maintenance is a very important aspect of any infrastructure and consumes 60 to 80% of I.T.’s budget. It is the hardware and software that has to be maintained in order to keep everything running smoothly and keep the company profitable.
Functionality, reliability, usability, efficiency, scalability and maintainability are what drive up the cost of maintenance. And what I mean by this is, in order to keep a system or the software on the system running at peak performance, CM’s (change management) need to be done on a regular basis. When I worked for Amazon, they were always making changes to the system or the software so the customers and the employee’s would have the system to use without any issues.
Though planning and feasibility, which is the start of any project, a designer can make the system low maintenance and efficient and still keep with in the budget. But with any new system or software, there is no way to keep them unaltered throughout the life cycle. This is why there will always be changes and or upgrades of the system and software throughout the development phase.
According to Mallach (2013, July 3), “An information system consists of five components,” e.g., hardware, software, data, procedures and people who are the end-users of the system. The two components: the hardware and software require consistent maintenance as they are susceptible to faults (Kadel,
References: Kadel, L. A. (2004, March 24). Designing and Implementing an Effective Information. Genoa, WI: Sans Institute. Mallach, E. G. (2013, July 3). Chapter 5: Information System Conversion Strategies, A Unified View. Retrieved from http://www.irma-international.org/viewtitle/54377/ wiseGEEK, (2015). What is System maintenance? Retrieved from: http://www.wisegeek.org/what-is-system-maintenance.htm Systems Analysis and Design, 9e Chapter 16: Systems Analysis and Design, 9e ISBN: 9780133023442 Author: Kenneth E. Kendall Copyright © Pearson Education, Inc. (2014)