Capturing Design Decision Rationale with Decision Cards

Lopez, Marisela Gutierrez; Rovelo, Gustavo; Haesen, Mieke; Luyten, Kris; Coninx, Karin

doi:10.1007/978-3-319-67744-6_29

Cited by 3 publications

(4 citation statements)

References 35 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Spaces for capturing design decisions should have a low threshold for usage and should not enforce a particular structure in order to accommodate the different strategies of design teams. We proposed and trialed one such format, the Decision Cards, reported in [19]. These cards are lightweight formats that have been used in design workshops to capture artefacts and their rationale in a standardized way, but without influencing the process.…”

Section: Design Direction #3 -Dedicate Space For Design Decisionsmentioning

confidence: 99%

Exploring the Role of Artefacts to Coordinate Design Meetings

Lopez¹,

Luyten²,

Vanacken³

et al. 2018

JoIS

Self Cite

View full text Add to dashboard Cite

Design artefacts are vital to communicate design outcomes, both in remote and co-located settings. However, it is unclear how artefacts are used to mediate interactions between designers and stakeholders of the design process. The purpose of this paper is exploring how professional design teams use artefacts to guide and capture discussions involving multidisciplinary stakeholders while they work in a co-located setting. An earlier draft of this paper was paper published in the Proceedings of the European Conference on Cognitive Ergonomics (ECCE 2017). This work adds substantial clarification of the methodology followed, further details and photographs of the case studies, and an extended discussion about our findings and their relevance for designing interactive systems. We report the observations of six design meetings in three different projects, involving professional design teams that follow a user-centered design approach. Meetings with stakeholders are instrumental for design projects. However, design teams face the challenge of synthesizing large amounts of information, often in a limited time, and with minimal common ground between meeting attendees. We found that all the observed design meetings had a similar structure consisting of a series of particular phases, in which design activities were organized around artefacts. These artefacts were used as input to disseminate and gather feedback of previous design outcomes, or as output to collect and process a variety of perspectives. We discuss the challenges faced by design teams during design meetings, and propose three design directions for interactive systems to coordinate design meetings revolving around artefacts.

show abstract

Section: Design Direction #3 -Dedicate Space For Design Decisionsmentioning

confidence: 99%

Exploring the Role of Artefacts to Coordinate Design Meetings

Lopez¹,

Luyten²,

Vanacken³

et al. 2018

JoIS

Self Cite

View full text Add to dashboard Cite

show abstract

“…Whilst decisions made by the development team occur iteratively throughout the process and will result in evolutions of multiple artefacts, the ISO standard 9241-210 is very silent about how to record and process such design decisions. Empirical observation [14] [15] have shown that development teams often make extensive use of annotations. Annotations are flexible, they can assume many forms (such as text, sketching, etc.)…”

Section: Introductionmentioning

confidence: 99%

“…and be attached to any type of artefacts, making them a suitable mechanism to provide complementary information throughout the development process. The study performed by Gutierrez et al [15] pointed out that annotations are used by members of development teams to: i) record the results of discussion including decisions and upcoming tasks, communicate and inform other team members of the work done, ii) gather internal and external feedback on artefacts stored in the workspace, iii) conduct usability evaluations by documenting information and by recording conversation between design teams and UX experts, and justify design choices, and document the design choices by describing them retrospectively. While previous work [15] argued for the use of annotations for user interface prototypes, this paper extends the use of annotations made over various artefacts (including prototypes) by providing a generic engineering solution to connect them across multiple artefacts.…”

Section: Introductionmentioning

confidence: 99%

“…Add semantics to the annotations: The integration of semantic annotations will help organizing information, building a structure for the information gathered and describing the interactive system being developed in its entirety instead of only considering localized annotations in artefacts as existing prototyping do tools do. The semantic annotations describing the relationship between artefacts, annotations for planning according to Bringay [19] as well as annotations for documenting the design process that are described by Gutierrez et al [15]. Our extended model aims to support both semantic annotations and non-semantic annotation on artefacts in the context of the design process of an interactive system.…”

mentioning

confidence: 99%

See 1 more Smart Citation

Engineering Annotations: A Generic Framework for Gluing Design Artefacts of Interactive Systems

Winckler

Palanque

Hak

et al. 2022

Proc. ACM Hum.-Comput. Interact.

View full text Add to dashboard Cite

Along the design process of interactive system multiple intermediate artefacts (such as user interface prototypes, task models, dialog models?) are created, tested, revised, and improved until the development team produces a full-fledged system. However, relevant information for describing the design solution and/or supporting design decisions (such as rational about the design, decisions made, recommendations, etc.) are not explicitly captured in the models/artefacts, hence the need for annotations. Many approaches argue against information duplication to increase maintainability of the artefacts. Nonetheless, annotations created on one artefact are usually relevant to other artefacts/models. So that, there is a need for tools and techniques to coordinate annotations across artefacts/models which is the contribution of the present work. In this paper, we propose a model-based approach that was conceived to handle annotations in a systematic way along the development process of interactive systems. As part of the solution, we propose an annotation model built upon the W3C's Web Annotation Data Model. The feasibility of the approach is demonstrated by means of a tool suite featuring a plugin, which has been deployed and tested over the multi-artefacts. The overall approach is illustrated on the design of an interactive cockpit application performing two design iterations. The contribution brings two main benefits for interactive systems engineering: i) it presents a generic pattern for integrating information in multiple usually heterogenous artefacts throughout the design process of interactive systems; and ii) it highlights the need for tools helping to rationalize and to document the various artefacts and the related decisions made during interactive systems design.

show abstract

Engineering Annotations to Support Analytical Provenance in Visual Exploration Processes

Tikat

Menin

Buffa

et al. 2022

Lecture Notes in Computer Science

View full text Add to dashboard Cite

This paper focuses on the fundamental role played by annotations to support provenance analysis in visual exploration processes of large datasets. Particularly, we investigate the use of annotations during the visual exploration of semantic datasets assisted by chained visualization techniques. In this paper, we identify three potential uses of annotations: (i) documenting findings (including errors in the dataset), (ii) supporting collaborative reasoning among teammates, and (iii) analysing provenance during the exploratory process. To demonstrate the feasibility of our approach, we implemented it as a tool support, while illustrating its usage and effectiveness through a series of use case scenarios. We identify the attributes and meta-data that describe the dependencies between annotations and visual representations, and we illustrate these dependencies through a domain-specific model.

show abstract

Capturing Design Decision Rationale with Decision Cards

Cited by 3 publications

References 35 publications

Exploring the Role of Artefacts to Coordinate Design Meetings

Exploring the Role of Artefacts to Coordinate Design Meetings

Engineering Annotations: A Generic Framework for Gluing Design Artefacts of Interactive Systems

Engineering Annotations to Support Analytical Provenance in Visual Exploration Processes

Contact Info

Product

Resources

About