Testing Prototypes and Final User Interfaces Through an Ontological Perspective for Behavior-Driven Development

Abstract

OATAO is an open access repository that collects the work of Toulouse researchers and makes it freely available over the web where possible. This is an author-deposited version published in : http://oatao.univ-toulouse.fr/ Eprints ID : 18842The contribution was presented at HCSE 2016:http://www.hcse-hessd.org/ Abstract. In a user-centered development process, prototypes evolve in iterative cycles until they meet users' requirements and then become the final product. Every cycle gives the opportunity to revise the design and to introduce new requirements which might affect the specification of artifacts that have been set in former development phases. Testing the consistency of multiple artifacts used to develop interactive systems every time that a new requirement is introduced is a cumbersome activity, especially if it is done manually. This paper proposes an approach based on Behavior-Driven Development (BDD) to support the automated assessment of artifacts along the development process of interactive systems. The paper uses an ontology for specifying tests that can run over multiple artifacts sharing similar concepts. A case study testing Prototypes and Final UserInterfaces is presented to demonstrate the feasibility of this approach in early phases of the design process, providing a continuous quality assurance of requirements, and helping clients and development teams to identify potential problems and inconsistencies before commitments with software implementation.

Ensuring the Consistency between User Requirements and Task Models: A Behavior-Based Automated Approach

“…The approach has also been extended and adapted to assess other early artifacts such as GUI prototypes and late artifacts such as final GUIs [39], [34], [37], [36], [40]. As an integrated approach, the same set of BDD stories is assigned to automatically assess task models, GUI prototypes in different levels of abstraction, and final GUIs, ensuring a consistent verification, validation and testing (VV&T) approach for interactive systems with high availability of tests and instantaneous feedback about the consistency of artifacts regarding the user requirements.…”

Interactive Behavior-driven Development: a Low-code Perspective

“…BDD builds on a combination of multiple existing methodologies and concepts, such as test-driven development (TDD) and ubiquitous languages from domain-driven design (DDD), 1 https://gtoolkit.com/ which enable teams to develop software systems collaboratively [4], [5], [6], [7]. The term ubiquitous language refers to the practice of building and using a common language between business and technical stakeholders [7].…”

“…The latest version of Gherkin supports background and data tables, which allow non-technical stakeholders to specify various combinations of input and corresponding expected outputs that can be provided to a single scenario. 4 Background and data tables help to reduce redundancy in textual scenarios. However, our manual inspection of 23 open-source projects on GitHub (with more than 500 stars and primary language Java) that use Gherkin specifications lead us to conclude that data tables are rather moderately used in scenario specifications.…”

Meeting Afoot – A Step Towards Transforming Work Practice By Design Of Technical Support

“…The mix of methods facilitated our understanding and provided means to gain knowledge how to proceed with the design in this unknown area of exploration (Bødker &Iversen, 2002;Silva, Hak, & Winckler, 2016). As described by Suchman (1993) work practice is a non-static activity and experience of the work tasks, generating of skills and knowledge is situated and complex.…”