Wait a second!
More handpicked essays just for you.
More handpicked essays just for you.
Importance of software maintenance and change control
Don’t take our word for it - see why 10 million students trust us with their essay needs.
Software Maintenance and Change Control In today's world there is very unusual to have a program developed that will not have further development after release. The requirements of the time that we live are very dynamic and there is a need for constant adaptation. A basic requirement for any new software product is to be adaptable, easy to maintain and modify. Time factor and cost factor are ruling in the agitated competition and only those who are well organized and prepared are able to survive. The question for software maintenance and change control is taking key position in both perspectives: the perspective of the manufacturer of the software, and the perspective of the consumer. In the negotiation and management of these two major players is the complexity of the software maintenance and change control. In this paper we will focus on some important specifics of these processes. Thomas Pigoski in his "template for a software maintenance plan" defines software maintenance in the following way: "Software maintenance is the totality of activities required to provide cost-effective support to a software system. Activities are performed during the pre-delivery stage as well as the post-delivery stage. Pre-delivery activities include planning for post-delivery operations, supportability, and logistics determination. Post-delivery activities include software modification, training, and operating a help desk." Later on in the same material he describes some organizational requirements in the same context: "Maintenance is performed by the developer, a separate maintainer, or by a third-party organization. It is important that the organization responsible for maintenance be identified in writing with full responsibilities. The Maintenance Plan accomplishes this.
Windows Server 2012 is a dynamic piece of software as it is constantly evolving. These improvements are available to users in the form of Windows Updates and patches. The results of an audit can show that without proper monitoring our system can slowly become obsolete, less productive, and potentially out of Government compliance. Microsoft is constantly making improvements or fixing bugs through a series of updates. Some of the updates are very important to keep products like Windows Server 2012 up to date and secure. Other updates may be labeled as recommended or optional from Microsoft. “Microsoft routinely releases security updates on the second Tuesday of each month, commonly known as Patch Tuesday” (Regan, 2013) With the abundance and frequency of patches it’s important for our organization to manage them in an efficient and organized manner so that we maintain the highest levels of productivity while minimizing system downtime.
The Systems Development Life Cycle (SDLC) consists of phases used in developing a piece of software. It is the plan of how to develop and maintain software, and when necessary, replace that software. In 2007 during my hospital’s transition to a new software system, I was fortunate enough to be included in the process. I did not get involved until the implementation phase, but from then on, until now, I remain very active in the process. I decided to highlight the Waterfall Model of SDLC. The Waterfall Model is a “sequential development process” with each phase continuing in a line (McGonigle and Mastrian, 2012, p. 205).
Change is inevitable and bound to happen in all aspects of life including business. Although change is important in an organization, it can also be seen as a strength and weakness. Effective leadership is about mastering change. One must be willing to change in order to grow and be successful. This paper will compare and contrast Kotter and Kurt Lewin step in their change management models. Furthermore, it will elaborate on the concepts and explain whether these methods can be used at the same time. In addition, this paper will include a Christian worldview of the information discussed and how it relates to the change management models.
Early fixing of errors not only helps save cost but also helps in mitigating the various risks associated with software development and it also helps in improving and monitoring quality of the system etc. It has been proven that the cost to identify and mitigate the errors in the early stages of development of a software will be hundred times less than the cost of removing an error in the software system that has been distributed among hundreds of
The software maintenance process is a long-term support tier for any and all computer-based business systems. In the age of computer automation and electronic commerce, many businesses have become dependent upon scalable and error proof software platforms. The ongoing support of these systems by the software manufacturer is crucial for the business owner, and the software's longevity. Software Maintenance is a detailed process for weighing suggested program additions, making program updates, supporting user-related questions, and fixing latent errors. This process is both heavily time and resource consuming for software firms. This is why it is important for all software firms to have a strong and well-organized software maintenance plan, in which any changes to a given product are, to be followed.
Given the time, it takes to develop large sophisticated software systems it not possible to define the problem and build the solution in a single step. Requirements will often change throughout a projects development, due to architectural constraints, customer’s needs or a greater understanding of the original problem. Iteration allows greater understanding of a project through successive refinements and addresses a projects highest risk items at every stage of its lifecycle. Ideally each iteration ends up with an executable release – this helps reduce a projects risk profile, allows greater customer feedback and help developers stay focused.
When software updates are released, they often contain added features and uses, this may result in problems because it may make existing features harder to use, these features can be such as changing shortcuts or the position of the tool bar, this can reduce efficiency in the level of work produce in an organisation.
...rried out routinely throughout the life of an information system to correct previously undetected errors. Bender RBT Inc (1984) reported that there are three primary activities involved in the maintenance phase are: build a help desk to support the system users, perform system maintenance, provide an environment to support system changes.
The non-complying software is expected to increase of error which made by development and maintenance team.
Preventive maintenance can be defined as an activity performed on a certain schedule which is intended to prevent breakdowns or deterioration. These activities can include regular inspection along with solving any discovered problems or situations and regularly scheduled parts changes. Preventive maintenance involves the scheduled adjustment, inspection, replacement of wearable parts, calibrations, basic cleaning and lubrication of equipment or other recommendation made by the equipment manufacturer. These activities can help increase the equipment functional life and help decrease facilities deterioration. No equipment should, No equipment should reach the breaking point [1].
Cholasuke et al. (2004) A review article categorized the maintenance effectiveness measures into nine areas as follows: (1) Policy deployment and organization; (2) Human resources management; (3) Financial aspects; (4) Continuous improvement; (5) Contracting out maintenance; (6) Maintenance approach; (7) Task planning and scheduling; (8) Information management and CMMS; and (9) Spare parts
Break-fix and preventive maintenance: Supports complete work order management through its entire lifecycle. Schedule preventive maintenance based on time, condition or event-based triggers.
Past and current maintenance practices in both the private and Government divisions would infer that maintenance is the activities related with equipment repair after it is broken. The dictionary describes maintenance as: “the work of keeping something in proper condition; maintenance.” This would imply that maintenance ought to be taken to keep a gadget or part from failing or to repair ordinary gear degradation experienced
To put these terms in connection, Operation is the execution of work or benefits and the procurement of materials and energy to guarantee the everyday appropriate working of an advantage, e.g., the work exercises, related chemicals and power to run a water treatment plant. Accordingly, it has a direct yet straightforward effect on the expense of working a benefit. Support is the work performed on an advantage, for example, a street, building, utility or bit of hardware to protect it in as close to its unique condition as is down to earth and to understand its typical future. This Technical Information Document, as its name suggests, focuses on upkeep administration frameworks as it were. As a rule, support can be characterized into the following categories:
Maintenance is defined as the required processes and services undertaken to preserve, protect, enhance, and care for the building’s fabric and services after completion, in accordance with the prevailing standard to enable the building and services to serve their intended function throughout their entire life span without drastically upsetting their basic feature and uses (Lateef et al, 2010).