Reasoning with Design Rationale

Burge, Janet E.; Brown, David C.

doi:10.1007/978-94-011-4154-3_30

Cited by 37 publications

(31 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This knowledge can be useful at various stages such as design verification, evaluation, reuse, teaching, communication, documentation, and maintenance [11].…”

Section: Design Rationalementioning

confidence: 99%

Revisiting the design intent concept in the context of mechanical CAD education

Otey

Contero

Camba

2017

Computer-Aided Design and Applications

View full text Add to dashboard Cite

Design intent is generally understood simply as a CAD model's anticipated behavior when altered. However, this representation provides a simplified view of the model's construction and purpose, which may hinder its general understanding and future reusability. Our vision is that design intent communication may be improved by recognizing the multifaceted nature of design intent, and by instructing users to convey each facet of design intent through the better-fitted CAD resource. This paper reviews the current understanding of design intent and its relationship to design rationale and builds on the idea that communication of design intent conveyed via CAD models can be satisfied at three levels provided that specialized instruction is used to instruct users in selection of the most suitable level for each intent.Keywords: design rationale, design intent, CAD model quality, CAD education. INTRODUCTIONFeature-based parametric CAD is a commonly deployed 3D modeling technology that is widely used in industrial settings. In these systems, the 3D CAD model is created by gradually and sequentially adding geometric features through parent/child relationships, which creates an interconnected structure that, when defined properly, allows for more flexible and reusable models. This process is recorded in a structure known as a design tree, feature tree, or history tree. Parent/child interdependencies are the basic elements that facilitate CAD reusability and alteration of parametric models. When these dependencies are defined properly, changes in the artifact can be performed efficiently, as alterations propagate automatically from parent to child nodes. However, parent/child dependencies can also be the root of numerous regeneration problems, which often forces designers to rebuild the CAD model entirely, costing time and money.Previous researchers have determined that 48% of CAD models fail during design exploration [38] and according to the 2013 State of 3D Collaboration and Interoperability Report, 49% of engineers spend more than 4 hours per week repairing design data with 14% spending more than 24 hours per week [39]. The same report states that 32% of organizations miss deadlines due to design data problems [39]. Gerbino states that data exchange issues result from poor modeling strategies [28]. González-Lluch and colleagues echo these sentiments stating that erroneous CAD models that filter toward downstream applications require effort to rework the models to remove data corruption [29]. Poor understanding and/or communication of design rationale and design intent are commonly argued to cause most of those failures. But the concepts of design rationale and design intent are complex in themselves.Describing the purpose of a design and the justifications for specific decisions made when creating it are essential tasks for engineers and design professionals. Design rationale can be defined as the explicit documentation of the reasons behind the decisions made when designing a system or artifact [52]. Although d...

show abstract

“…This knowledge can be useful at various stages such as design verification, evaluation, reuse, teaching, communication, documentation, and maintenance [11].…”

Section: Design Rationalementioning

confidence: 99%

Revisiting the design intent concept in the context of mechanical CAD education

Otey

Contero

Camba

2017

Computer-Aided Design and Applications

View full text Add to dashboard Cite

show abstract

“…JANUS (Fischer, et al, 1995) critiques the design and provides the designers with rationale to support the criticism SYBIL (Lee, 1990) and InfoRat (Burge and Brown, 2000) both check that the rationale behind each decision is complete. C-Re-CS (Klein, 1997) performs consistency checking on requirements and recommends a resolution strategy for detected exceptions.…”

Section: Rationale Usementioning

confidence: 99%

An Integrated Approach for Software Design Checking Using Design Rationale

Burge

Brown

2004

Design Computing and Cognition ’04

Self Cite

View full text Add to dashboard Cite

Abstract. Design Rationale (DR), the reasons behind decisions made while designing, offers a richer view of both the product and the decision-making process by providing the designer's intent behind the decisions. DR is also valuable for checking to ensure that the intent was adhered to throughout the design, as well as pointing out any unresolved (or undocumented) issues that remain open. While there is little doubt of the value of DR, it is typically not captured during design. SEURAT (Software Engineering Using RATionale) is a system we have developed to explore uses of design rationale. It supports both the display of and inferencing over the rationale to point out any unresolved issues or inconsistencies. SEURAT is tightly integrated with a software development environment so that rationale capture and use can become integrated into the software development process.

show abstract

“…As discussões realizadas durante o decorrer de um projeto com o intuito de serem tomadas decisões, bem como as razões pelas quais as decisões foram ou não tomadas, ou ainda, informações que foram utilizadas para embasar tal atividade, são denominadas Design Rationale (Burge e Brown, 2000).…”

Section: Objetivosunclassified

“…Denomina-se Design Rationale as informações que explicam ou descrevem as razões, os motivos, por quais determinadas decisões foram tomadas em um projeto (Burge e Brown, 2000).…”

Section: Wikis E Design Rationaleunclassified

Wikis para suporte à documentação de processo de software livre

Filho¹,

da²

View full text Add to dashboard Cite

Reasoning with Design Rationale

Cited by 37 publications

References 12 publications

Revisiting the design intent concept in the context of mechanical CAD education

Revisiting the design intent concept in the context of mechanical CAD education

An Integrated Approach for Software Design Checking Using Design Rationale

Wikis para suporte à documentação de processo de software livre

Contact Info

Product

Resources

About