Maintenance support needs for object-oriented software

Crocker, Ron; Mayrhauser, A. von

doi:10.1109/cmpsac.1993.404216

Cited by 7 publications

(3 citation statements)

References 17 publications

(4 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Finally, the scope for tool support in assisting with inspection of object-oriented code has been demonstrated. An automated version of display method due to Parnas et al may be one possibility, whilst another may be in the use of tools used to support maintenance, such as the Valhalla system (Wilde et al, 1993) or the maintenance suite described by Crocker and Mayrhauser ( 1993). Finally, visualization tools may be of some help, such as the static Seesoft system (Eick et al, 1992) or the dynamic visualization system described by De Pauw et al (1993).…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

Applying Inspection to Object-Oriented Code

MacDonald

Miller

Brööks

et al. 1996

Softw. Test. Verif. Reliab.

View full text Add to dashboard Cite

Section: Discussionmentioning

confidence: 99%

“…Another example of such support for maintenance has been described by Crocker and Mayrhauser (1993). They describe a suite containing four types of tool.…”

Section: Tool Supportmentioning

confidence: 99%

Applying Inspection to Object-Oriented Code

MacDonald

Miller

Brööks

et al. 1996

Softw. Test. Verif. Reliab.

View full text Add to dashboard Cite

“…In his paper, he defined a set of different refractorings (program restructurings) for 00 programs, and proposed a systematic solution to deal with refractorings in an inheritance hierarchy (both generalization and specialization) and a class aggregation structure. Crocker and Mayrhauser (1993) discussed the needs and the necessary software tools that support and enhance the software maintenance effort for 00 programs. These include:…”

Section: Related Workmentioning

confidence: 99%

Identifying Polymorphism Change and Impact in Object-orientated Software Maintenance

Gao

Chen

Toyoshima

et al. 1996

J. Softw. Maint: Res. Pract.

View full text Add to dashboard Cite

SUMMARYSince polymorphism in object-orientated (00) programming is an important feature and tool to increase the reusability and extensibility of object-orientated programs, understanding and identifying polymorphism changes and their impacts in an object-orientated program is very important in software maintenance. Although many published research articles have addressed the polymorphism feature in object-orientated programs, almost none of them have discussed software maintenance issues on identification of polymorphism change and impact. This paper proposes a formal software maintenance model for polymorphism in object-orientated programs, and discusses a systematic approach to track different polymorphism changes and their ripple effects. In addition, it reports on the implementation of a relevant tool, OOTME, and its use on two case studies.

show abstract

Evaluating inheritance depth on the maintainability of object-oriented software

Daly

Brööks

Miller

et al. 1996

Empirical Software Engineering

140

View full text Add to dashboard Cite

This empirical research was undertaken as part of a multi-method programme of research to investigate unsupported claims made of object-oriented technology. A series of subject-based laboratory experiments, including an internal replication, tested the effect of inheritance depth on the maintainability of object-oriented software. Subjects were timed performing identical maintenance tasks on object-oriented software with a hierarchy of three levels of inheritance depth and equivalent object-based software with no inheritance. This was then replicated with more experienced subjects. In a second experiment of similar design, subjects were timed performing identical maintenance tasks on object-oriented software with a hierarchy of five levels of inheritance depth and the equivalent object-based software. The collected data showed that subjects maintaining object-oriented software with three levels of inheritance depth performed the maintenance tasks significantly quicker than those maintaining equivalent object-based software with no inheritance. In contrast, subjects maintaining the object-oriented software with five levels of inheritance depth took longer, on average, than the subjects maintaining the equivalent object-based software (although statistical significance was not obtained). Subjects' source code solutions and debriefing questionnaires provided some evidence suggesting subjects began to experience difficulties with the deeper inheritance hierarchy. It is not at all obvious that object-oriented software is going to be more maintainable in the long run. These findings are sufficiently important that attempts to verify the results should be made by independent researchers

show abstract

Maintenance support needs for object-oriented software

Cited by 7 publications

References 17 publications

Applying Inspection to Object-Oriented Code

Applying Inspection to Object-Oriented Code

Identifying Polymorphism Change and Impact in Object-orientated Software Maintenance

Evaluating inheritance depth on the maintainability of object-oriented software

Contact Info

Product

Resources

About