Object-oriented software evolution

Lieberherr, Karl; Xiao, Cun

doi:10.1109/32.223802

Cited by 56 publications

(20 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Others have written on theoretical aspects of the evolution of designs (Hull, 1988, Steadman, 1979, Stebbins, 1971 and design knowledge (Gero, 1996, Kaplan, 2000. Some related work focuses on evolution in software design (Foote & Opdyke, 1995, Kemerer & Slaughter, 1999, Lieberherr & Xiao, 1993, Taylor, 2000b). Vernacularism appears to be robust and irrepressible.…”

Section: The Value Of Vernacularismmentioning

confidence: 99%

Vernacularism in Software Design Practice: does craftsmanship have a place in software engineering?

Taylor¹

2003

AJIS

View full text Add to dashboard Cite

Convention dictates that an information discipline matures from an informal shared practice to a defined and repeatable process through the externalisation and formal expression of its underlying theory. The inevitability of this progression should not be allowed to over-shadow the essential values, skills and knowledge transfer mechanisms of the superseded vernacular or craft-like practices. This paper examines the tension between software engineering's professionalisation of the software design role-exemplified by the software architect-and its antithesis, the software craftsperson, a characterisation that continues to emerge despite attempts to suppress reliance on individual skills and abilities through software engineering process. In other design disciplines, the professionalisation of design marks a distinct progression from ad hoc, unrepeatable, unselfconscious craft to a selfconscious, demarcated type of design found in most forms of engineering. Software engineering has partially failed to make this transition and this failure undermines the exclusivity of the engineering metaphor and engineering-based process models as a model of practical software design. Software methods must acknowledge and find ways of incorporating vernacularism and informality if the creative act of design is to be correctly characterised, supported in methods, and taught.

show abstract

Section: The Value Of Vernacularismmentioning

confidence: 99%

Vernacularism in Software Design Practice: does craftsmanship have a place in software engineering?

Taylor¹

2003

AJIS

View full text Add to dashboard Cite

show abstract

“…However, other technologies for separating concerns could be used. For example, using adaptive programming [14], the processing currently performed by a visitor could be localized within a propagation pattern and woven into the AST classes. Alternatively, using aspect-oriented programming [15], we could associate pointcuts with AST classes and define an aspect that performs the processing currently performed by a visitor; the aspect could then be woven into the AST classes using the pointcuts.…”

Section: Integration With Other Toolsmentioning

confidence: 99%

Inference graphs: a computational structure supporting generation of customizable and correct analysis components

Dillon

Stirewalt

2003

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Abstract-Amalia is a generator framework for constructing analyzers for operationally defined formal notations. These generated analyzers are components that are designed for customization and integration into a larger environment. The customizability and efficiency of Amalia analyzers owe to a computational structure called an inference graph. This paper describes this structure, how inference graphs enable Amalia to generate analyzers for operational specifications, and how we build in assurance. On another level, this paper illustrates how to balance the need for assurance, which typically implies a formal proof obligation, against other design concerns, whose solutions leverage design techniques that are not (yet) accompanied by mature proof methods. We require Amaliagenerated designs to be transparent with respect to the formal semantic models upon which they are based. Inference graphs are complex structures that incorporate many design optimizations. While not formally verifiable, their fidelity with respect to a formal operational semantics can be discharged by inspection.

show abstract

“…Research papers classify different software evolution and maintenance scenarios [8]. Many papers focus especially on objectoriented software development [9]. Some describe change support tools.…”

Section: Software Evolutionmentioning

confidence: 99%