Software Maintenance and Change Control in an OrganizationSoftware Maintenance and Change Control in an OrganizationSoftware Maintenance and Change Control in an OrganizationProgramming Concepts POS/370October 3, 2005AbstractThe research done for this paper represents an attempt to describe the type and distribution of activities within software maintenance and change control. Software maintenance activities span a system’s productive life and consume a major portion of the total life cycle costs of a system. However, what is actually done to systems in maintenance is sometimes a mystery to many organizations. Thus, software maintenance remains an activity that is difficult and expensive to manage. With this paper, we intend to open the mystery of software maintenance and explain some of the activities involved in this procedure.
The Role of Programmers in the Maintenance of Software. Abstract A program’s operation remains the sole focus when it comes to the maintenance of software, and it’s job is to maintain that state of affairs well. A developer of software may be able to ensure that all its state of affairs continues to be maintained in a timely manner, but other users can’t. If a developer who does this for you knows nothing about software maintenance, and you’re happy to provide him with a list of programs (a directory), it might be difficult to tell how much of your schedule has been compromised, given the nature of these programs’ business. In other words, once you know about software maintenance programs, you can make better decisions about how to utilize them more effectively, and also, better, make better decisions about how to pay the bills. Moreover, program managers are involved in all the steps of software maintenance. In fact, they have direct control of, and control over, all aspects of the maintenance of software. The system administrators make, implement, and manage software maintenance programs at a high level. Many large organizations have various programs such as the web server manager, the backup client, and the security-manager. The user is the manager of all software maintenance programs. The program manager should coordinate software maintenance efforts according to the activities of different program managers (i.e., the program manager’s personal priorities, a program manager’s program’s job priorities, program management’s program objectives, program management’s objectives, and program scheduling’s priorities). The program agent should have the best technical judgment and skills to make a plan for the most comprehensive, best planning and maintenance of software. The program manager should also have confidence in the reliability and availability of the data provided by program agents. Software managers should be aware that the various software maintenance programs are closely tied to each other. In fact, some program managers may have higher degrees of technical expertise. Such higher degree of expertise provides program managers a more complete insight into the program organization and of software maintenance programs by making more of this information available throughout the organization. The software maintenance program agent should have knowledge of systems management, maintenance planning and maintenance management processes such as group or business events, project management, and program management and decision-making. Finally, program agents should have a background in program management, program management and program management processes. Program managers do not expect their program managers to have specialized knowledge of programs at all. They need their program managers to have strong and strong opinions about various programs, and a broad perspective on the programs that they perform. Program agents should take note of the programming they do perform, which can help inform the program managing process and the maintenance and change management of programs. Program managers should also know whether other programs are performing well. For instance, there might be a program agent who is very knowledgeable about programs, particularly software management programs. Program managers should also have a strong appreciation of the benefits of software maintenance programs. Moreover, program managers should consider the programs that are associated with specific programs. For example, for a program management program, program managers might find some applications that are “best managed,” which means they might have a well-developed maintenance plan that ensures continuity between each program, and also has a good plan to avoid significant program changes. Also, programs on the Web server management front might be a good candidate for some programs on which program managers can be knowledgeable. Program managers must use programs that demonstrate a good ability to perform certain maintenance actions
The Role of Programmers in the Maintenance of Software. Abstract A program’s operation remains the sole focus when it comes to the maintenance of software, and it’s job is to maintain that state of affairs well. A developer of software may be able to ensure that all its state of affairs continues to be maintained in a timely manner, but other users can’t. If a developer who does this for you knows nothing about software maintenance, and you’re happy to provide him with a list of programs (a directory), it might be difficult to tell how much of your schedule has been compromised, given the nature of these programs’ business. In other words, once you know about software maintenance programs, you can make better decisions about how to utilize them more effectively, and also, better, make better decisions about how to pay the bills. Moreover, program managers are involved in all the steps of software maintenance. In fact, they have direct control of, and control over, all aspects of the maintenance of software. The system administrators make, implement, and manage software maintenance programs at a high level. Many large organizations have various programs such as the web server manager, the backup client, and the security-manager. The user is the manager of all software maintenance programs. The program manager should coordinate software maintenance efforts according to the activities of different program managers (i.e., the program manager’s personal priorities, a program manager’s program’s job priorities, program management’s program objectives, program management’s objectives, and program scheduling’s priorities). The program agent should have the best technical judgment and skills to make a plan for the most comprehensive, best planning and maintenance of software. The program manager should also have confidence in the reliability and availability of the data provided by program agents. Software managers should be aware that the various software maintenance programs are closely tied to each other. In fact, some program managers may have higher degrees of technical expertise. Such higher degree of expertise provides program managers a more complete insight into the program organization and of software maintenance programs by making more of this information available throughout the organization. The software maintenance program agent should have knowledge of systems management, maintenance planning and maintenance management processes such as group or business events, project management, and program management and decision-making. Finally, program agents should have a background in program management, program management and program management processes. Program managers do not expect their program managers to have specialized knowledge of programs at all. They need their program managers to have strong and strong opinions about various programs, and a broad perspective on the programs that they perform. Program agents should take note of the programming they do perform, which can help inform the program managing process and the maintenance and change management of programs. Program managers should also know whether other programs are performing well. For instance, there might be a program agent who is very knowledgeable about programs, particularly software management programs. Program managers should also have a strong appreciation of the benefits of software maintenance programs. Moreover, program managers should consider the programs that are associated with specific programs. For example, for a program management program, program managers might find some applications that are “best managed,” which means they might have a well-developed maintenance plan that ensures continuity between each program, and also has a good plan to avoid significant program changes. Also, programs on the Web server management front might be a good candidate for some programs on which program managers can be knowledgeable. Program managers must use programs that demonstrate a good ability to perform certain maintenance actions
Requirements AnalysisThe requirements analysis is possibly the most crucial step in the software maintenance realm, as this step alone can determine the effectiveness of all following activities and the customer’s evaluation of the final product. “Requirements analysis is the process of understanding the customers needs, and capturing them in a formal document.” (Icarus, p. 2) This formal document, when working with an existing program, is normally known as a change request form. The change request can come in the form of a formal document or in the form of a heated e-mail from your superiors. If it is the latter, you need to take steps to produce a formal change request document. This document will outline the constraints, commonly referred to as the triple constraint, scope, time, and money.
The first of these three, scope, is quite difficult to define, early in the process. However, the scope of the project must be defined in terms that can evolve into a pseudo-checklist. This document will be reviewed constantly throughout the process to determine whether a particular fits with the customer needs and wants. One way of determining the customer’s needs is to develop a questionnaire. This can alleviate several communications problems between the development team and the customer. The questionnaire can be used to develop the change request document. Other ways to develop a change request document is to conduct a walkthrough with the main stakeholders of the change. This function will allow the development team to get a feel for the work environment and aid in the development of the program changes. A combination of these steps strengthens the change request document. By conducting a questionnaire and then conducting a walkthrough, the requested changes can be illustrated within the work environment, the development team will determine a level of necessity for each of the requested changes. This need-level will help to dictate which of the changes will become higher or lower priority. Prioritizing needs will aid the project team by giving them a guideline to build off of. Once the Change request document has been finalized and then signed by both the customer and the project manager, the development team can begin the next phase of the development process.
DesignThe Design Phase is the problem-solving process whose objective is to find and describe a way to implement the systems functional requirements, while respecting the constraints imposed by the non-functional requirements, and while adhering to general principles of good quality. This phase also determines how components will be implemented in a system. There are a number of goals in the in this phase;
Increasing profit by reducing cost and increasing revenue.Ensuring that we actually conform with the requirements, thus solving the customers problems.Accelerating development, which helps reduce short-term costs, and may also ensure the software reaches the market soon enough to effectively compete.Increasing qualities such as usability, efficiency, reliability, maintainability, and reusability which can help reduce costs and also increase revenues.
ImplementationAlthough this section of system maintenance is widely overlooked, it is extremely important. Without proper and speedy implementation of the desired changes, the customer would realize the product of your work. Implementation consists of the coding phase of the system development life cycle. This stage requires several Quality Assurance procedures to take place during this stage. This is not the testing phase however, it is a self governing