Applying use cases: a practical guide
Applying use cases: a practical guide
A vector space model for automatic indexing
Communications of the ACM
Making Use: Scenario-Based Design of Human-Computer Interactions
Making Use: Scenario-Based Design of Human-Computer Interactions
Mastering AspectJ: Aspect-Oriented Programming in Java
Mastering AspectJ: Aspect-Oriented Programming in Java
Usability Basics for Software Developers
IEEE Software
Understanding How the Requirements Are Implemented in Source Code
APSEC '03 Proceedings of the Tenth Asia-Pacific Software Engineering Conference Software Engineering Conference
Analyzing Interaction Orderings with Model Checking
Proceedings of the 19th IEEE international conference on Automated software engineering
Testing Scenario Implementation with Behavior Contracts
COMPSAC '06 Proceedings of the 30th Annual International Computer Software and Applications Conference - Volume 01
UML 2 Certification Guide: Fundamental & Intermediate Exams (The OMG Press)
UML 2 Certification Guide: Fundamental & Intermediate Exams (The OMG Press)
Koala: capture, share, automate, personalize business processes on the web
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
| Hi-index | 0.00 |
Interactions between users and software are usually described as scenarios so that it is easy to reflect users' viewpoints in software development. In many cases, scenarios are written in a natural language so that users can communicate with software developers smoothly. However, it is difficult to validate correspondences between the flows of operations written in scenarios and those in software. We assume that the flows of software can be expressed by the flows of Graphical User Interface (GUI) operations. In this paper, we propose a method for validating the correspondences between the flows of operations in scenarios and those of actual GUIs. This validation can be performed by analyzing the historic data of GUI operations heuristically. The label names on widgets are extracted from the histories, terms corresponding to label names on widgets are extracted from scenarios, and then the orders of appearance of label names and f terms are validated.