Topic
User story
About: User story is a research topic. Over the lifetime, 1078 publications have been published within this topic receiving 23717 citations.
Papers published on a yearly basis
Papers
More filters
••
27 Apr 2016TL;DR: Evaluating a novel agile agent-oriented modelling (AAOM) method for requirements engineering that links goal-model creation techniques taken from agentoriented modelling and connects goals intuitively to user stories fills the gap.
Abstract: The use of agile methods during software development is a standard practice and user stories are an established
way of breaking complex system requirements into smaller subsets. However, user stories do not suffice for
understanding the bigger picture of system goals. While methods exists that try to solve this problem, they lack
visual tool support and are too heavy for smaller projects. This article fills the gap by evaluating a novel agile
agent-oriented modelling (AAOM) method for requirements engineering. The AAOM-method comprises a
visual approach to agile requirements engineering that links goal-model creation techniques taken from agentoriented
modelling and connects goals intuitively to user stories. A case study based evaluation explores the
applicability of AAOM for requirements engineering in an agile software development process.
6 citations
••
[...]
TL;DR: The UM on a Key that combined a user modeling server and mediation mechanism will allow the user to explicitly select what information to disclose to service provider and to do that at the right format.
Abstract: Provision of personalized services to users requires accurate modeling of their interests and needs. However, such information may not be available to the service provider. Previously suggested solutions, such as user modeling servers and user modeling mediation demonstrate technological possible solution to the problem. However, at the same time they introduce privacy problem. This paper proposes a general framework for enhancing the privacy of user modeling in personalization systems by keeping the user "in control" of his/her personal information. The UM on a Key that combined a user modeling server and mediation mechanism will allow the user to explicitly select what information to disclose to service provider and to do that at the right format.
6 citations
••
TL;DR: The development of user interfaces is a mixture of the development of an expert system and a normal user interface and the impact of the new user interface on the changing user task has to be taken into account in the development process.
Abstract: Research institutes and universities have developed many programs which have been used up until now mainly by specialists. The input preparation, the interpretation of the output, and the use of the program are often too complicated to be suitable for a wider group of users. A part of the knowledge necessary for the use of a scientific program can be included in a user interface. The development of such user interfaces is a mixture of the development of an expert system and a normal user interface. The impact of the new user interface on the changing user task has to be taken into account in the development process.
6 citations
••
18 Jun 2020
TL;DR: This article presents an approach based on Behavior-Driven Development to provide automated assessment for task models, which are intended to model the flow of user and system tasks in an interactive system.
Abstract: Evaluating and ensuring the consistency between user requirements and modeling artifacts is a long-time issue for model-based software design. Conflicts in requirements specifications can lead to many design errors and have a decisive impact on the quality of systems under development. This article presents an approach based on Behavior-Driven Development (BDD) to provide automated assessment for task models, which are intended to model the flow of user and system tasks in an interactive system. The approach has been evaluated by exploiting user requirements described by a group of experts in the domain of business trips. Such requirements gave rise to a set of BDD stories that have been used to automatically assess scenarios extracted from task models that were reengineered from an existing web system for booking business trips. The results have shown our approach, by performing a static analysis of the source files, was able to identify different types of inconsistencies between the user requirements and the set of task models analyzed.
6 citations
••
TL;DR: Discusses one of the most basic topics in user-interface design: how to run a user test, and tools, techniques and concepts to optimize user interfaces are described, and ethical issues are discussed.
Abstract: Discusses one of the most basic topics in user-interface design: how to run a user test. No matter how good we are at designing a user interface, we must always test it with real users to see whether it is as usable as we hope. The three main rules of user testing are: get real users, have them do real tasks, and shut up while they are trying. Tools, techniques and concepts to optimize user interfaces are described, and ethical issues are discussed.
6 citations