%0 Conference Proceedings
%T Testing Prototypes and Final User Interfaces Through an Ontological Perspective for Behavior-Driven Development
%+ Université Toulouse III - Paul Sabatier (UT3)
%A Silva, Thiago, Rocha
%A Hak, Jean-Luc
%A Winckler, Marco
%Z Part 2: Usability Evaluation and Testing
%< avec comité de lecture
%( Lecture Notes in Computer Science
%B 6th International Conference on Human-Centred Software Engineering (HCSE) / 8th International Conference on Human Error, Safety, and System Development (HESSD)
%C Stockholm, Sweden
%Y Cristian Bogdan
%Y Jan Gulliksen
%Y Stefan Sauer
%Y Peter Forbrig
%Y Marco Winckler
%Y Chris Johnson
%Y Philippe Palanque
%Y Regina Bernhaupt
%Y Filip Kis
%I Springer International Publishing
%3 Human-Centered and Error-Resilient Systems Development
%V LNCS-9856
%P 86-107
%8 2016-08-29
%D 2016
%R 10.1007/978-3-319-44902-9_7
%K Automated requirements checking
%K Behavior-Driven Development
%K Ontological modeling
%K Prototyping
%K Multi-artifact testing
%Z Computer Science [cs]Conference papers
%X 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 User Interfaces 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.
%G English
%Z TC 13
%Z WG 13.2
%Z WG 13.5
%2 https://inria.hal.science/hal-01647702/document
%2 https://inria.hal.science/hal-01647702/file/430524_1_En_7_Chapter.pdf
%L hal-01647702
%U https://inria.hal.science/hal-01647702
%~ UNIV-TLSE3
%~ IFIP-LNCS
%~ IFIP
%~ IFIP-WG
%~ IFIP-TC13
%~ IFIP-HCSE
%~ IFIP-WG13-2
%~ IFIP-LNCS-9856
%~ IFIP-HESSD
%~ IFIP-WG13-5
%~ UNIV-UT3
%~ UT3-INP
%~ UT3-TOULOUSEINP