Abstract
Maintenance is the important phase in software development lifecycle which initiates after the software has been deployed for use. Reusability is an important area of concern which depicts the extent to which a module can be used again in different applications with slight or no modification. Maintainability is one of the contributing factors for assessing Reusability. So, assessment of Reusability is preferred over Maintainability. This paper has been split into Introduction, Role of Maintainability, Role of reusability and conclusion. In the introduction section the concept that how the software evolves has been discussed. The second section focuses on the Role ofMaintainability. The third second emphasizes on the Role of Reusability within the domains of Object-Oriented Programming and Aspect-Oriented Programming. In the last section we have concluded that assessment of Reusability must be given more preference over the assessment of Maintainability.
Highlights
In this internet era it has been noticed that society has become software dependent
According to IEEE, maintainability can be defined as “The ease with which a software system or Component can be modified to correct faults, improve performance or other attributes, or adapt to a changed environment” [9].The changes occurring due to modification have effect on interfaces, components and features
Core concerns are the functional requirements of the system. Some concerns such as logging, security etc. are scattered throughout the code, which affects reusability and maintainability. Such concerns are called crosscutting concerns In Aspect oriented programming (AOP) languages concern is encapsulated in an aspect and is connected to main classes by using pointcuts
Summary
In this internet era it has been noticed that society has become software dependent. Software can be seen being used in everyday life. Errors may occur in software which needs to be corrected so that its performance is not affected. The software lifecycle may consist of following phases: specification, design, implementation, testing, installation, and maintenance. In the waterfall model the last phase of software’s lifecycle is the maintenance which starts after the product is implemented and tested and continues until the software is useless. Maintenance is actions to correct errors in software that has occurred in the testing phase. According to IEEE, maintainability can be defined as “The ease with which a software system or Component can be modified to correct faults, improve performance or other attributes, or adapt to a changed environment” [9].The changes occurring due to modification have effect on interfaces, components and features
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
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 call
