Top PDF A behavior-driven approach for specifying and testing user requirements in interactive systems
A behavior-driven approach for specifying and testing user requirements in interactive systems
... our approach can support such a traceability and consistency checking, Figure 66 presents the successive mapping of a less refined Balsamiq prototype, a PANDA prototype, and ...
344
Definition of a Behavior-Driven Model for Requirements Specification and Testing of Interactive Systems
... Model for testable requirements ...Multi-Artifact Testing Fig. 3. gives a general view of how testing integration can occur in multiple artifacts, given an example of ...
8
Definition of a Behavior-Driven Model for Requirements Specification and Testing of Interactive Systems
... side, User Stories are typ- ically used to describe requirements in agile ...[9] and provides in the same artifact a Narrative, briefly describing a feature in the ...
7
Extending Behavior-Driven Development for Assessing User Interface Design Artifacts
... ONCLUSION AND F UTURE W ORKS This paper summarizes the new results we got by applying our approach for specifying and checking the consistency of user requirements on core ...
5
Towards Automated Requirements Checking Throughout Development Processes of Interactive Systems
... The user-centered development process of interactive systems is iter- ative and, during multiple iterations, users have the opportunity to bring new requirements that are very likely to ...
4
A Rule-driven Approach for Defining the Behavior of Negotiating Software Agents
... as a form of interaction made of protocols and ...game, and, for a given protocol, a participant (human or software) uses a strategy ...(i.e., a plan of action) to ...
21
Model-Based Testing for Building Reliable Realtime Interactive Music Systems
... therefore a reactive system, interacting with the out- side environment (the musicians) under strong timing constraints: the output (generally messages passed to an external audio application such as MAX [32]) ...
54
A multi-formalism approach for model-based dynamic distribution of user interfaces of critical interactive systems.
... 3.1. Requirements for a user interface generation and distribution process for dynamic partly automated system As presented in Section 2 , in the area of complex ...
24
An Approach for Multi-Artifact Testing Through an Ontological Perspective for Behavior-Driven Development
... system in terms of tasks that may be accomplished. This is particularly true in early phases of the development process when the Prototypes are rudimentary samples of interactive ...systems. ...
28
A FORMAL ONTOLOGY FOR DESCRIBING INTERACTIVE BEHAVIORS ON USER INTERFACES
... implement Behavior-Driven Development (BDD) as a mean of automating the test of interactive systems under ...Automated testing helps to simulate user’s actions on the User ...
26
Model-Based Testing of Interactive Systems
... Post-WIMP interactive systems do not consider widgets as first-class components but pre- fer the use of concepts that reduce the gap between the user and the ...system. For instance, ...
52
Towards Automated Requirements Checking Throughout Development Processes of Interactive Systems
... Automated Requirements Checking, Behavior-Driven Develop- ment, Multi-Artifact ...of Requirements Engineering encompass cycles of meetings and in- terviews with clients, users ...
3
A behavior-based ontology for supporting automated assessment of interactive systems
... ONCLUSION In this paper we have presented a behavior-based ontology aiming at test automation that can help to validate functional requirements when building interactive ...as a ...
9
A behavior-based ontology for supporting automated assessment of interactive systems
... CONCLUSION In this paper we have presented a behavior-based ontology aiming at test automation that can help to validate functional requirements when building interactive ...as a ...
10
A Formal Ontology for Describing Interactive Behaviors and Supporting Automated Testing on User Interfaces
... involved in the development of web applications where we have observed certain patterns of low level behaviors that are recurrent when writing BDD Scenarios for testing functional requirements ...
29
REFAS: A PLE Approach for Simulation of Self-Adaptive Systems Requirements
... define a simulation as a sequence of scenarios where a scenario is the definition of a partial mapping of the model’s context variables to corresponding ...running a simulation means to ...
6
Testing Prototypes and Final User Interfaces Through an Ontological Perspective for Behavior-Driven Development
... is a summary of the basic concepts to explain how the approach ...2.1 User Stories and Scenarios A large set of requirements can be expressed as stories told by the ...term ...
24
Rationalizing the Need of Architecture-Driven Testing of Interactive Systems
... flow for a given type of input ...requires a separate “Input Device ...the user (e.g. a mouse or a finger on a ...which, in turn, makes this information available to ...
24
Testing Prototypes and Final User Interfaces Through an Ontological Perspective for Behavior-Driven Development
... Conclusion and Future Works In this paper we have presented an approach aiming test automation that can help to validate functional requirements through multiple artifacts used to build ...
23
A Formal Ontology for Describing Interactive Behaviors and Supporting Automated Testing on User Interfaces
... domains. For example, high level Steps like ``When I search for °ights to ``Destination"" encapsulate all low level behaviors referring to individual clicks, selections, ...(i.e. behavior ...
28