Automated reuse of design plans

Mostow, Jack; Barley, Michael; Weinrich, Timothy

doi:10.1016/0954-1810(89)90014-9

Cited by 46 publications

(13 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Their work is couched in a transformational framework. Two domains are addressed: circuit designs [22] and heuristic search algorithms [24, 231. 4 Related Work…”

Section: Resultsmentioning

confidence: 99%

Reusing software developments

Goldberg

1990

Proceedings of the Fourth ACM SIGSOFT Symposium on Software Development Environments

View full text Add to dashboard Cite

Software development environments of the future will be characterized by extensive reuse of previous work. This paper addresses the issue of reusability in the context in which design is achieved by the transformational development of formal specifications into efficient implementations. It,explores how an implementation of a modified specification can be realized by replaying the transformational derivation of the original and modifying it as required by changes made to the specification. Our approa.ch is to structure derivations using the notion of tactics, and record derivation histories as an execution trace of the application of tactics. One key idea is that tactics are compositional: higher level tactics are constructed from more rudimentary using defined control primitives. This is similar to the approach used in LCF[l2] and NuPR.L[l, 8j.Given such a derivation history and a modified specifica.tion, the correspondence problem [21,20] a.ddresses how during replay a correspondence between program parts of the origina.l and modified program is established.

show abstract

“…Their work is couched in a transformational framework. Two domains are addressed: circuit designs [22] and heuristic search algorithms [24, 231. 4 Related Work…”

Section: Resultsmentioning

confidence: 99%

Reusing software developments

Goldberg

1990

Proceedings of the Fourth ACM SIGSOFT Symposium on Software Development Environments

View full text Add to dashboard Cite

show abstract

“…They express a need to explore the concept of modularity in relation to 'knowledge management and modules seen as knowledge carriers'. Such exploration is essential to facilitate a 'design for reuse' modular methodology as it is well documented that previous solutions are rarely wholly re-usable [29], [30] & [3]. Without adequate provision for the knowledge related to how and why the final solution was derived, it is difficult to effectively facilitate the 'reuse' of partial solutions.…”

Section: Knowledge Modulesmentioning

confidence: 99%

Supporting `Design for Re-use' with Modular Design

Meehan

Duffy

Whitfield

2007

Concurrent Engineering

View full text Add to dashboard Cite

This version is available at https://strathprints.strath.ac.uk/4841/ Strathprints is designed to allow users to access the research output of the University of Strathclyde. Unless otherwise explicitly stated on the manuscript, Copyright © and Moral Rights for the papers on this site are retained by the individual authors and/or other copyright owners. Please check the manuscript for details of any other licences that may have been applied. You may not engage in further distribution of the material for any profitmaking activities or any commercial gain. You may freely distribute both the url (https://strathprints.strath.ac.uk/) and the content of this paper for research or private study, educational, or not-for-profit purposes without prior permission or charge.Any correspondence concerning this service should be sent to the Strathprints administrator: strathprints@strath.ac.ukThe Strathprints institutional repository (https://strathprints.strath.ac.uk) is a digital archive of University of Strathclyde research outputs. It has been developed to disseminate open access research outputs, expose data about those outputs, and enable the management and persistent access to Strathclyde's intellectual output.

show abstract

“…This information can be very difficult to access and is represented such that computers can provide little support for managing and utilising it. This design rationale information is critical, however, for supporting important collaborative design functions like structured design space exploration (Lee and Lai, 1991, MacLean, Young, Bellotti, and Moran, 1991, McCall, 1987, team memory (Balzer, 1984), conflict management Lu, 1991, Klein, 1997), and design retrieval (Mostow and Barley, 1987).…”

Section: The Challenge: Capturing Rationale For Design Geometrymentioning

confidence: 99%

Collaborative capture of geometry rationale

Klein¹

1999

Cooperative Knowledge Processing for Engineering Design

View full text Add to dashboard Cite

When an artefact is designed the typical output consists of documents describing the final result of a long series of deliberations and trade-offs by the participants of collaborative design (AKA concurrent engineering) teams. The underlying intent and logical support (i.e. the rationale) for the decisions captured therein is usually lost, or is represented at best as a scattered, difficult-to-access collection of paper documents and designers' recollections. This is particularly true for geometric, as opposed to preliminary, design rationale. Rationale information is critical, however, for important collaborative design functions such as team memory, design retrieval and negotiation. This paper describes an evolving web-based tool designed to greatly improve capture and access of preliminary and geometric design rationale in concurrent engineering teams, based on a marriage of rationale capture, worldwide web, CAD and feature-based design technology.

show abstract

Automated reuse of design plans

Cited by 46 publications

References 12 publications

Reusing software developments

Reusing software developments

Supporting `Design for Re-use' with Modular Design

Collaborative capture of geometry rationale

Contact Info

Product

Resources

About