Software engineering (3rd ed.): a practitioner's approach
Software engineering (3rd ed.): a practitioner's approach
Object-oriented modeling and design
Object-oriented modeling and design
Refactoring object-oriented frameworks
Refactoring object-oriented frameworks
Object-oriented metrics that predict maintainability
Journal of Systems and Software - Special issue on object-oriented software
An investigation into coupling measures for C++
ICSE '97 Proceedings of the 19th international conference on Software engineering
A Unified Framework for Coupling Measurement in Object-Oriented Systems
IEEE Transactions on Software Engineering
A Metrics Suite for Object Oriented Design
IEEE Transactions on Software Engineering
Reengineering the Class - An Object Oriented Maintenance Activity
COMPSAC '98 Proceedings of the 22nd International Computer Software and Applications Conference
An Incremental Class Reorganization Approach
ECOOP '92 Proceedings of the European Conference on Object-Oriented Programming
Design Metrics in the Reengineering of Object-Oriented Systems
ECOOP '98 Workshop ion on Object-Oriented Technology
Application frameworks: how they become your enemy
Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion
| Hi-index | 0.00 |
This paper addresses the problem of reengineering object-oriented systems that have incurred increased maintenance cost due to long development time-span and project lifecycle. When an Incremental Approach is used to develop an object-oriented system, there is a risk that the class design and the overall object model will deteriorate in quality with each increment. A recent research work suggested a process activity (Class Deterioration Detection and Resurrection - CDDR process activity) and a technique for the detection and resurrection of deteriorated classes [5]. That work focussed on one particular aspect of object-oriented software maintenance - Class Quality Deterioration due to lack of cohesion induced by high coupling. This paper addresses the problem of deteriorating object-oriented design due to code and class growth (increase in the number of classes) within a system. A Code/Class Growth Control process activity (CGC) is suggested to avoid and eliminate Repetitions Code and Classes within the evolving system. The CDDR and CGC process activities are used to build an evolving Maintenance process model for object-oriented systems. The presented maintenance process model is an effective way to periodically assess and resurrect the quality of an object-oriented design during incremental development.