In Autumn 2020, DOAJ will be relaunching with a new website with updated functionality, improved search, and a simplified application form. More information is available on our blog. Our API is also changing.

Hide this message

An Approach for Multi-Artifact Testing Through an Ontological Perspective for Behavior-Driven Development

Complex Systems Informatics and Modeling Quarterly. 2016;0(7):81-107 DOI 10.7250/csimq.2016-7.05


Journal Homepage

Journal Title: Complex Systems Informatics and Modeling Quarterly

ISSN: 2255-9922 (Online)

Publisher: Riga Technical University

LCC Subject Category: Technology: Technology (General): Industrial engineering. Management engineering: Information technology

Country of publisher: Latvia

Language of fulltext: English

Full-text formats available: PDF



Thiago Rocha Silva (ICS-IRIT, Université Paul Sabatier, 118 Route de Narbonne, Toulouse)

Jean-Luc Hak (ICS-IRIT, Université Paul Sabatier, 118 Route de Narbonne, Toulouse)

Marco Winckler (ICS-IRIT, Université Paul Sabatier, 118 Route de Narbonne, Toulouse)


Blind peer review

Editorial Board

Instructions for authors

Time From Submission to Publication: 10 weeks


Abstract | Full Text

In a user-centered development process, artifacts 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 new requirements are 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 Task Models, Prototypes, and Final User Interfaces is presented to demonstrate the feasibility of this approach from the 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 are made.