Ensuring the Consistency Between User Requirements and GUI Prototypes: A Behavior-Based Automated Approach

Silva, Thiago Rocha; Winckler, Marco; Trætteberg, Hallvard

doi:10.1007/978-3-030-29381-9_39

Cited by 4 publications

(2 citation statements)

References 27 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We argue that the benefits of using a high-level DSL for specifying BDD scenarios are twofold. First, it ensures that the scenarios are sticking to a domain specification, so BDD steps can be later automated and reused more easily for testing purposes [15], [16], [17], [18], [19]. Second, it lays the foundation to develop a low-code approach that handles software behaviour specification as BDD scenarios.…”

Section: Preliminary Evaluation and Next Stepsmentioning

confidence: 99%

Towards a Domain-Specific Language for Behaviour-Driven Development

Silva

2023

2023 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)

View full text Add to dashboard Cite

This paper introduces a high-level domain-specific language (DSL) and its rich editing environment to allow the specification of consistent and testable Behaviour-Driven Development (BDD) scenarios as user requirements at different levels of abstraction. We preliminary evaluated our approach by looking at its potential to support the writing of BDD scenarios in five open-source projects on GitHub. Results have shown the language was able to fully support, with minor adaptations, the specification of consistent user requirements, allowing also a complete mapping between domain and interactive behaviours through BDD scenarios.

show abstract

Section: Preliminary Evaluation and Next Stepsmentioning

confidence: 99%

Towards a Domain-Specific Language for Behaviour-Driven Development

Silva

2023

2023 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)

View full text Add to dashboard Cite

show abstract

“…Once we have initial design ideas for an IoT application we want to ensure that the proposed system will do what is required. Note we are not addressing requirements engineering here, other research has investigated the use of design specifications, such as behavioural specifications, within model-based engineering approaches [35], [36]. Such research could be integrated with the work we propose in this paper, but here, for simplicity, we assume a known set of requirements.…”

Section: A Benefits Of the Approachmentioning

confidence: 99%

Interaction Modelling for IoT

Turner

Bowen

Zandwijk

2021

2021 28th Asia-Pacific Software Engineering Conference (APSEC)

View full text Add to dashboard Cite

Informal design artefacts allow end-users and nonexperts to contribute to software design ideas and development. In contrast, software engineering techniques such as modeldriven development support experts in ensuring quality properties of the software they propose and build. Each of these approaches have benefits which contribute to the development of robust, reliable and usable software, however it is not always obvious how best to combine these two. In this paper we describe a novel technique which allows us to use informal design artefacts, in the form of ideation card designs, to generate formal models of IoT applications. To implement this technique, we created the Cards-to-Model (C2M) tool which allows us to automate the model generation process. We demonstrate this technique with a case study for a safety-critical IoT application called "Medication Reminders". By generating formal models directly from the design we reduce the complexity of the modelling process. In addition, by incorporating easy-to-use informal design artefacts in the process we allow non-experts to engage in the design and modelling process of IoT applications.

show abstract

Towards a Domain-Specific Language to Specify Interaction Scenarios for Web-Based Graphical User Interfaces

Silva

2022

Companion of the 2022 ACM SIGCHI Symposium on Engineering Interactive Computing Systems

Self Cite

View full text Add to dashboard Cite

The communication gap between software developers and subjectmatter experts is one of the foremost long-standing problems in software development. The level of formality of the user requirements specification has a strong impact on the ability of these two groups to communicate effectively. Domain-Specific Languages (DSLs) are seen as one of the potential solutions to address this issue by raising the abstraction level of the software specification while keeping the necessary formalism to allow for software analysis, design, and verification. This paper discusses the ongoing development of a high-level DSL and its rich editing environment to allow the specification of consistent and testable interaction scenarios as user requirements for web-based graphical user interfaces. The language grammar has been developed based on the Gherkin syntax that supports Behaviour-Driven Development (BDD). Results of a preliminary evaluation regarding the consistency of actions and states of interaction elements specified for web user interfaces showed that the grammar is able to support a consistent specification of BDD scenarios as user requirements at the interaction level. CCS CONCEPTS• Software and its engineering → Domain specific languages; • Human-centered computing → Interactive systems and tools.

show abstract

Ensuring the Consistency Between User Requirements and GUI Prototypes: A Behavior-Based Automated Approach

Cited by 4 publications

References 27 publications

Towards a Domain-Specific Language for Behaviour-Driven Development

Towards a Domain-Specific Language for Behaviour-Driven Development

Interaction Modelling for IoT

Towards a Domain-Specific Language to Specify Interaction Scenarios for Web-Based Graphical User Interfaces

Contact Info

Product

Resources

About