Abstract
Software maintenance is the activity in which changes occur in the artifacts of a software after delivery, with the purpose of keeping it available, correcting its failures, improving its performance and adapting it to new or modified requirements, according to the needs of Your users. It is an indispensable activity, without which existing systems would quickly become lagging and inefficient for organizations. The objective of this work is to verify the adherence of existing software maintenance models and processes in an organization whose product is used by a large number of users. After identifying and evaluating the problems of the company's current situation, carried out through a case study, actions are suggested to improve its software maintenance process.
Highlights
The software development life cycle consists of a series of phases: planning, analysis and specification of requirements, design, implementation, testing, delivery and deployment, operation and maintenance
The E3 Element is one of Norma’s main goals, as it relies on all software maintenance processes, making it a complete flow for service in that industry
This paper presents the case study of an organization, whose problems in software maintenance are aggravated by the lack of a process for such activities and tasks within a business context
Summary
The software development life cycle consists of a series of phases: planning, analysis and specification of requirements, design, implementation, testing, delivery and deployment, operation and maintenance. In the scope of software changes occur when errors are corrected, when there is adaptation to a new environment, when the client requests new improvements or new functions and when the application goes through a reengineering process to provide benefits in a modern context (Sommerville, 2007). It becomes evident that software companies understand the need to research and relate more information about software maintenance activity. These need to highlight the main difficulties and challenges of the maintenance activity, the best practices and processes to be adopted, and the existing tools that support this maintenance activity. It is necessary to ensure the availability of systems and efficiency of care of software maintenance requests
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callMore From: Journal of Information Systems Engineering & Management
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
