This paper outlines a structured set of development controls and directives for building a new software application to replace an existing one. It argues that a new system must address all usability shortcomings of the old system while delivering greater effectiveness, efficiency, and accuracy. The paper walks through ten key development steps — from initial business requirements gathering and analysis of the legacy system, through design, team coordination, user acceptance testing, and ongoing maintenance — demonstrating how disciplined process control reduces business risk and ensures the final product meets organizational standards.
In developing a new application to replace an existing one, it is important that the new system encompass all the essential functionalities of the old application that users depend on. Technically, in terms of usability, the new system must address all the shortcomings of the old application that led to its replacement. Moreover, the new application must be characterized by greater effectiveness, efficiency, accuracy, and overall performance. In view of this, the development process must follow a rigid set of rules and standards laid out in a detailed course of action. Through this discipline, it can be assured that the newly developed software product does not expose the business to unnecessary risk.
A set of development controls and directives is necessary to ensure that all business control issues receive sufficient attention during the development process. As Rachelle Benson states in her article Information Technology can Manage Routine Business Processes:
A well-designed and implemented system can run the routine side of the business 'like clockwork', managing processes and leaving managers and employees with more time to develop new business, find new customers and spend longer with existing customers.
The following sections outline the ideal steps for a simple development process when creating a new system to replace an old one.
Gather all business requirements applicable to the system. Gathering requirements — particularly the business requirements of the organization where the system will be implemented — is always the foremost step in every new system and application development. Through this process, developers gain an overview of what approach they will take throughout development.
Gather all existing requirements of the old system that are still necessary and must exist in the new system. Anticipating the possibility that the system being replaced is, in some way, still useful and effective to users is essential, especially when the development process is intended to produce a replacement. Through analysis, review, and evaluation of the old application, developers gain a clearer idea of how to make the new system better. The practice of legacy system analysis is a well-established step in ensuring continuity and improvement.
Gather all business issues in relation to the old system. After gathering business information and analyzing the old application, identifying the business issues that exist in the old system is essential, since those issues are the very reasons a new application is being developed. This process provides the developer and project team with a concrete list of problems requiring solutions.
Gather the system's required input and output needs. After gaining an overview of the purpose of the new application, collecting all necessary data is important to allow development to begin. This phase partially transitions the project into the main development process.
"System design, team contact, and regular project meetings"
"Testing, error correction, and ongoing system maintenance"
You’re 56% through this paper. Sign up to read the remaining 2 sections.
Sign Up Now — Instant Access Already a member? Log inAlways verify citation format against your institution’s current style guide requirements.