Testing Prototypes and Final User Interfaces Through an Ontological Perspective for Behavior-Driven Development
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 affec
- PDF / 5,060,917 Bytes
- 22 Pages / 439.37 x 666.14 pts Page_size
- 61 Downloads / 183 Views
)
ICS-IRIT, Université Paul Sabatier, Toulouse, France {rocha,jean-luc.hak,winckler}@irit.fr
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 auto‐ mated 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 require‐ ments, and helping clients and development teams to identify potential problems and inconsistencies before commitments with software implementation. Keywords: Automated requirements checking · Behavior-Driven Development · Ontological modeling · Prototyping · Multi-artifact testing
1
Introduction
It is a common understanding that in user-centered design (UCD) processes, users’ requirements and needs are not always identified at once but they are rather revised/ tuned and incrementally introduced along the multiple iterations through the use of Prototypes. When requirements are updated and/or new ones are introduced, the devel‐ opment team must cross-check their consistency with artifacts set in former development phases. Testing and tracing requirements during the development of interactive system is a daunting task specially because the development team has to deal with many cycles of iterations, multiple artifacts (such as Task Models, Prototypes, User Stories, Scenarios, etc.), and many design options for Prototypes that evolve until they reach the status of Final Product. The traceability of artifacts can be said as vertical and horizontal [19]. Vertical traceability describes the relationship between artifacts that can be derived from each © IFIP International Federation for Information Processing 2016 Published by Springer International Publishing Switzerland 2016. All Rights Reserved C. Bogdan et al. (Eds.): HCSE 2016/HESSD 2016, LNCS 9856, pp. 86–107, 2016. DOI: 10.1007/978-3-319-44902-9_7
Testing Prototypes and Final User Interfaces
87
other, for example from customer requirements to acceptance test cases. Horizontal traceability refers to the evolution of the same artifact. The artifacts traceability problem has been studied by several authors and a wide set of commercial tools have been devel‐ oped to address this problem in various approaches [16]. Nonetheless, solutions to promote vertica
Data Loading...
