Three Key Projects That Need Perfective Maintenance - Paper Example

Introduction

The life of a software product does not come to an abrupt end when it is finally implemented. The system is always evolving as long as it is being used. This is because there is a need to accommodate new changes since they operate in an ever-changing environment. Changes in the way software was designed to run might be triggered by many factors; to fix bugs, enhance functionality features, upgrade to the latest operating system, and to implement new changes to prevent the occurrence of future errors (Moonen and Pollock 2016, p.117). For this reason, software maintenance is an essential phase of the software development life cycle (SDLC). The case study has presented three key projects that need perfective maintenance.

Is your time best spent reading someone else’s essay? Get a 100% original essay FROM A CERTIFIED WRITER!

Order now

The three systems require the perfective type of software maintenance. The reason is that as users have become exposed to the system, they have thought of ways of expanding it (Abrahamsson et al. 2017, p. 23). First, the efficiency of the bank system needs to be enhanced by adding a functionality that allows all customer services to be included in one ticket. Secondly, to manage the whereabouts of the young children, the developer needs to disable the internet option and integrate an inbuilt feature that allows parents to track the locations of their kids via the use of Google maps and GPRS. Lastly, the customer relationship management needs to be re-designed to consider specific requirements of the organization' culture, especially in protecting customers data.

As a system analyst, I will involve some stakeholders when adding the new functionality in their bank system. The key stakeholders in this project will be bank clerks, risk assessment officers, investors, IT personnel team, and customers. Notably, the bank clerks are the users who often interact with the software. They will add insight on the various services that are offered to the customers. The risk assessment manager will identify the various risks associated with integrating the modules and provide appropriate advice. The investors will offer their views on whether an investment in the new functionality is worthwhile. The IT personnel team will assist in planning as well as offer technical support when implementing the new feature. Besides, they will work with the system developer to ensure that the system meets security standards to ensure seamless integration with the existing system. Lastly, the customers will provide ideas on how to develop an innovative functionality that will be tailored towards meeting their needs. Importantly, a high-fidelity prototype that allows mouse-keyboard interaction will be used to simulate the real system's functionality will be developed. Markedly, the perfective maintenance of the CRM system will also include many stakeholders ranging from customers, investors, risk assessment manager, IT personnel team, and the CRM end users (employees). They will play an analogous role to the one executed by the bank system stakeholders.

Similarly, many stakeholders will be involved in designing a system that disables the internet option and integrates an inbuilt feature that allows parents to track the locations of their kids via the use of Google maps and GPS. They include; parents, children, legal specialist, and GPS enabled watch list developers. As end users of the system, parents will provide their views as to why the internet option ought to be disabled. On the other hand, children will give their opinions on how they see view these GPS enabled devices. The legal specialist will implore on the legal issues surrounding such innovations-whether they curtail children's freedom of movement. The developers will help integrate the new functionality to the system. A low-fidelity prototype will be developed to collect testable ideas and feedback from the users

Conclusion

In my view, "maintaining awareness of the whereabouts of young active children" project has the best chance of success as an interaction design project. This is because the system is not complex as it involves the integration of GPS, Google maps, and internet connection. Again, few stakeholders are involved when designing the system. Besides, a low-fidelity prototype, drawn on a paper, can easily be used to explain how the system will operate. Moreover, the fact that children are key stakeholders in this project is an underpinning reason as to why the low-fidelity prototype is the most applicable in this project.

References

Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.

Moonen, L. and Pollock, L., 2016. Introduction to the special issue on software maintenance and evolution. Journal of Software: Evolution and Process, 28(7), pp.510-511.