scholarly journals Modeling an Object Oriented for Maintenance Purposes

2012 ◽  
Vol 3 (3) ◽  
pp. 401-405 ◽  
Author(s):  
Hamed J. Al-Fawareh

Software maintenance is the last phase of the software life cycle. The aim of the software maintenance is to maintain the software system in accordance with advancement in software and hardware technology. In this paper, we discuss a maintenance system for object-oriented techniques. The paper therefore discusses about a problems in object oriented techniques under the maintenance environment. These problems include understanding object oriented system, complex dependencies in object-oriented system, inheritance, polymorphism and dynamic binding problem that maintainers and developers commonly face. Finally, we talk about the proposed object-oriented maintenance tool.

2019 ◽  
Vol 8 (4) ◽  
pp. 7032-7034

In modern era, Maintainability of object oriented software system will be report to 70-75% for all these efforts extended by the resource and efforts used for the design phase in development life cycle. To make better or maintain the maintenance, the analyst design this phase early. For designing the software system the system furter classified into the number of object metrics and the maintenance of the object oriented system having fewer changes required for the sub system. In this work, the maintainability metrics are used to calculate or measure the localized location that are being utilized in designing.


2013 ◽  
Vol 2013 ◽  
pp. 1-11 ◽  
Author(s):  
Kagiso Mguni ◽  
Yirsaw Ayalew

Software maintenance is an important activity in software development. Some development methodologies such as the object-oriented have contributed in improving maintainability of software. However, crosscutting concerns are still challenges that affect the maintainability of OO software. In this paper, we discuss our case study to assess the extent of maintainability improvement that can be achieved by employing aspect-oriented programming. Aspect-oriented programming (AOP) is a relatively new approach that emphasizes dealing with crosscutting concerns. To demonstrate the maintainability improvement, we refactored a COTS-based system known as OpenBravoPOS using AspectJ and compared its maintainability with the original OO version. We used both structural complexity and concern level metrics. Our results show an improvement of maintainability in the AOP version of OpenBravoPOS.


Author(s):  
Macario Polo ◽  
Mario Piattini ◽  
Francisco Ruiz

Software maintenance is the most expensive stage of the software life cycle. However, most software organizations do not use any methodology for maintenance, although they do use it for new developments. In this article, a methodology for managing the software maintenance process is presented. The methodology defines clearly and rigorously all the activities and tasks to be executed during the process and provides different sets of activities for five different types of maintenance (urgent and non-urgent corrective, perfective, preventive, and adaptive). In order to help in the execution of tasks, some techniques have been defined in the methodology. Also, several activities and tasks for establishing and ending outsourcing relationships are proposed, as well as several metrics to assess the maintainability of databases and their influence on the rest of the Information System. This methodology is being applied by Atos ODS, a multinational organization among whose primary business activities is the outsourcing of software maintenance.


2021 ◽  
Author(s):  
Z. Stojanov

Software maintenance has been recognized as the most demanding and costly phase in the software life cycle. Software maintenance tasks, although require a more complex set of skills and knowledge, are far less interesting to software engineers than software development tasks. In addition, insight into the scholarly literature revealed that the knowledge basis on software maintenance is significantly less than the knowledge base on software development. Due to the obvious constraints of small software companies, they do not have time, people, and other resources for assessing and improving their software maintenance practice. This paper presents the author’s reflections on experience in assessing and improving software maintenance practice in an indigenous micro software company.


2011 ◽  
Vol 57 ◽  
pp. 134-142
Author(s):  
Sigitas Dapkūnas ◽  
Valdemaras Zaramba

Programinės įrangos priežiūra suprantama kaip programinės įrangos modifikavimas atidavus naudotojui. Programos modifikuojamos taisant rastas klaidas, gerinant įvairius programinės įrangos parametrus, plečiant arba keičiant funkcionalumą. Programinės įrangos priežiūra yra viena iš programinės įrangos gyvavimo ciklo dalių. Ilgą laiką programinės įrangos priežiūrai buvo skiriamas mažesnis dėmesys nei jos kūrimui. Pastaruoju metu padėtis pasikeitė. Vertinant ir gerinant programinės įrangos kokybę bei priežiūrą, matuojamas tiek programinės įrangos procesas, tiek programinis produktas. Straipsnyje analizuojami programinės įrangos priežiūrumo, priežiūros proceso matai, taip pat šiam tikslui skirtos programinės priemonės.Software Maintainability and Maintenance MeasurementSigitas Dapkūnas, Valdemaras Zaramba SummarySoftware maintenance means software modification after its delivery to customers. The programs are modified with the purpose to correct faults, to improve performance or other program parameters, to enhance or change its functionality. Software maintenance is an integral part of a software life cycle. Historically, software maintenance received less attention than software development in most organizations. Recently, the situation has changed. For software quality or software maintenance assessment and improvement, software process or software product measurement is used. The paper deals with software maintenance measurement. It analyses software maintainability and maintenance measures, the measurement tools.


Sign in / Sign up

Export Citation Format

Share Document