Design rationale capture in software architecture

Schubanz, Mathias

doi:10.1145/2601328.2601329

Cited by 1 publication

(1 citation statement)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some of these systems have focused on capturing design rationale based on traceability of requirements [6], argumentation [7], and decision-making processes [8]. While each of these systems propose a valuable approach for capturing design rationale, design practitioners are yet to adopt tools with this purpose [9]. One reason for this is that designers customize existing tools to their own practices [1].…”

Section: Context and Backgroundmentioning

confidence: 99%

Helaba: A System to Highlight Design Rationale in Collaborative Design Processes

Lopez

Haesen

Luyten

et al. 2015

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Design activities associated to the ideation phase of design processes require mutual understanding and clear communication based on artefacts. However, this is often a challenge for remote and multidisciplinary teams due to the lack of ad hoc tools for this purpose. Our approach is to solve these limitations by explicitly connecting pieces of information related to design rationale, feedback, and evolution with the artefacts that are subject of communication. We propose Helaba, a system that creates a shared workspace to support communication revolving around design artefacts and activities within multidisciplinary teams. Helaba supports design communication and rationale, and potentially leads to more satisfying outcomes from the design process.Keywords: Design, design rationale, remote / multidisciplinary communication IntroductionModern design has evolved into a complex knowledge activity that more often than not involves multidisciplinary teams. However, these teams often lack the tools for efficient collaboration and communication, specifically because the different roles involved also have different work practices and focus, and use domain specific languages. We tackle two main challenges in communication within a design team and with their stakeholders. First, issues with mutual understanding and clear communication during the ideation phase of the design process, which leads to suboptimal results, loss of time and thus money and sometimes frustrations and difficulties in collaboration. Second, design processes often involve asynchronous and remote communication, which we found has many disadvantages if there is no domain-specific system to mediate and support this type of communication. We discovered that explicitly connecting pieces of information with the artefacts that are the subject of communication can help a great deal to improve this.In this paper we introduce Helaba, a semi-functional prototype that aims to reduce the challenges faced in remote, multidisciplinary design communication. The word Helaba is used in the Flemish spoken language to greet someone, but also to attract the

show abstract

Section: Context and Backgroundmentioning

confidence: 99%