Restructuring for style

Zimmer, Jürgen

doi:10.1002/spe.4380200404

Cited by 23 publications

(5 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In "Restructuring for Style" [21], I replaced the concepts of cohesion and coupling with a less subjective concept of data cobweb. That notion is revisited below in the section titled "Data Cobweb Graph".…”

Section: A Subjective Note On Refactoringmentioning

confidence: 99%

Graph Theoretical Indicators and Refactoring

Zimmer¹

2003

Extreme Programming and Agile Methods - XP/Agile Universe 2003

View full text Add to dashboard Cite

show abstract

Section: A Subjective Note On Refactoringmentioning

confidence: 99%

Graph Theoretical Indicators and Refactoring

Zimmer¹

2003

Extreme Programming and Agile Methods - XP/Agile Universe 2003

View full text Add to dashboard Cite

show abstract

“…The concept of the object module as a means of restructuring FORTRAN code into an object-oriented style was introduced in some papers [8]. While code structured as object modules is not truly object-oriented, it marked the beginning of research along that path.…”

Section: Object Extractionmentioning

confidence: 99%

Object Modeling to Re-Engineer Legacy Systems

Guo

Luqi

2000

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

This paper summarizes our experiences in using computer-supported methods to develop a software architecture to support the re-engineering of the Janus Combat Simulation System. We have analyzed the Janus FORTRAN source code, interviewed Janus domain experts, developed an object-oriented architecture for the Janus Combat Simulation subsystem, and validated the architecture with an executable prototype. In this paper, we propose methods to facilitate the evolution of the software component of these systems by recovering the behavior of the systems using systematic methods, and illustrate their use in the context of the Janus System.

show abstract

“…Applying the addition operation to an ordinal-scale measure is not a meaningful transformation. Zimmer (1990) demonstrated the conversion of a procedural program into an object-module program. Both the original and restructured program are implemented in FORTRAN.…”

Section: A Documentation-based Approachmentioning

confidence: 99%

A quantitative framework for software restructuring

Kang

Bieman

1999

J. Softw. Maint: Res. Pract.

View full text Add to dashboard Cite

Many existing software systems can benefit from restructuring to reduce maintenance cost and improve reusability. Yet, intuition‐based, ad hoc restructuring can be difficult and expensive, and can even make software structure worse. We introduce a quantitative framework for software restructuring. In the framework, restructuring decisions are guided by visualized design information and objective criteria. The design information can be extracted directly from code to restructure existing or legacy software. Criteria for comparing alternative design structures include measures of design‐level cohesion and coupling. Restructuring is accomplished through a series of decomposition and composition operations which increase the cohesion and/or decrease the coupling of individual system components. An example and a case study demonstrate the framework. The framework ensures that restructuring results in measurable improvements in design quality. Copyright © 1999 John Wiley & Sons, Ltd.

show abstract

Restructuring for style

Cited by 23 publications

References 8 publications

Graph Theoretical Indicators and Refactoring

Graph Theoretical Indicators and Refactoring

Object Modeling to Re-Engineer Legacy Systems

A quantitative framework for software restructuring

Contact Info

Product

Resources

About