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
TL;DR: This paper presents an approach for sprint planning based on an integer linear programming model and proposes an effective Lagrangian heuristic based on a relaxation of the proposed model and some greedy and exchange algorithms.
24 citations
Patent•
26 Feb 1997TL;DR: In this article, an apparatus and method for separating the design and implementation of a user interface (the user interface logic) from the design of the functional portion of a software program (the core logic) is presented.
Abstract: An apparatus and method for separating the design and implementation of a user interface ("the user interface logic") from the design and implementation of the functional portion of a software program (the "core logic"). The present invention uses an object-oriented programming model in which one or more look and feel agents (304) act as servers for one or more logic objects (302). The look and feel agent (304) controls the appearance and behavior of the user interface, while logic objects (302) perform the functions of the software program. A look and feel agent (304) does not "know" what functions constitute the core logic and the logic objects (302) do not "know" what the user interface looks like or how it behaves.
24 citations
TL;DR: This research applied the cultural probes method to domestic ironing practices and communicated the narrative and pictorial data generated by this method to designers and asked them to interpret these data in terms of a new ironing board design.
Abstract: This paper reports an initial study using cultural probes to support design. Its aim was to provide designers and design students with ethnographic information not easily accessible via surveys, interviews, and user statistics. Our research applied the cultural probes method to domestic ironing practices. We communicated the narrative and pictorial data generated by this method to designers and asked them to interpret these data in terms of a new ironing board design. Finally, we conducted a content analysis to reveal how designers interpreted and used data from cultural probes to inform design ideas.
24 citations
TL;DR: The aim is to create an understanding about categorization practices in design through a case study about the virtual community, Habbo Hotel, and a qualitative analysis highlighted not only the meaning of the "average user," but also the work that both the developer and the category contribute to this meaning.
Abstract: The "user" is an ambiguous concept in human-computer interaction and information systems. Analyses of users as social actors, participants, or configured users delineate approaches to studying design-use relationships. Here, a developer's reference to a figure of speech, termed the "average user," is contrasted with design guidelines. The aim is to create an understanding about categorization practices in design through a case study about the virtual community, Habbo Hotel. A qualitative analysis highlighted not only the meaning of the "average user," but also the work that both the developer and the category contribute to this meaning. The average user a) represents the unknown, b) influences the boundaries of the target user groups, c) legitimizes the designer to disregard marginal user feedback, and d) keeps the design space open, thus allowing for creativity. The analysis shows how design and use are intertwined and highlights the developers' role in governing different users' interests.
24 citations
10 Jul 2019
TL;DR: The experimental results indicate that this conceptual model can extract user story from online news and manages to extract 105 user stories from 92 aspects of what/why candidate and 109 aspects of who candidate.
Abstract: To specify good requirements, system analysts need to understand the domain knowledge of the system. There are several techniques in requirements elicitation to improve domain knowledge understanding, such as user interviews, questioners, document analysis, and brainstorming. Most of these techniques require profound stakeholder involvement. However, not all software projects can do this task due to limited time or availability of stakeholders. In agile software development, the user story is the de facto standard used for capturing and writing functional requirements. The user story is an appropriate format and easy to understand for writing the results of requirements elicitation. This study purposes a conceptual model to extract user story from online news for improving domain knowledge understanding. The information in the online news contained lesson learned related to certain events. This information may improve the functionality of the software products. The user story consists of three aspects, namely: who, what, and why. Aspect of who represents the role or user, aspect of what shows the purpose or feature, while the aspect of why explains the reason. This format can summarize the lessons learned in the news. Our experimental results indicate that this conceptual model can extract user story from online news. The model manages to extract 105 user stories from 92 aspects of what/why candidate and 109 aspects of who candidate.
24 citations