Systems Maintenance

Systems Maintenance

Empyra.com

Rick Rovnak

August 11th, 2014

Empyra.com has been working on developing and implementing a new CRM system. The system will be used to aid in daily business activities of the company and to cut down on costs and time that has been wasted doing basic business tasks. Since costs savings is a goal of Empyra.com’s CRM System, development of the system should be done carefully to reduce any current or future maintenance costs. Maintenance costs include things like bug fixing, system enhancements, system adaptations, system improvements and taking preventative measures to avoid possible problems. Maintenance costs but a large strain on Empyra.com’s ability to grow. It also eats up the time of employees who could better allocate time to market and design a better product. The new has to be designed so it can be easily scalable in the future and also be maintained.

One of the main reasons that Empyra.com ends up performing corrective maintenance is that the company’s testing procedure could use some improvement. The more in depth testing is the smaller the risk of latent defects. These defects not only damage the company’s image but waste lots of development time as well. In the software industry time is money, every second wasted on maintenance takes time away from future development and product improvements. Testing needs to be more structured and follow a more concise process. Empyra.com should create two development instances of the CRM system’s software package. One is for testing and the other is for production. Developers will also have their own personal development instance. In the development instances they will work on making assigned modules stable. When their individual module is completed a tester will check it out and sign off on it saying it is stable. After stability is confirmed the code from the developer instance will be built to the testing instance and check by testers