scispace - formally typeset
Search or ask a question
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
More filters
Journal ArticleDOI
TL;DR: A literature review aiming to identify how agile teams have integrated UCD tools into their agile software development process to a better understanding of the user requirements without losing sight of the agile values and principles finds approaches that could lead to a comprehensive user-centric software engineering.
Abstract: The lack of user engagement, the absence of user feedback, incomplete and continuously changing user requirements are among the critical concerns that cause projects to fail User-centered design (UCD) and agile software development are two iterative approaches that have been proposed to overcome such concerns UCD is a design process focusing on user research, user interface design and usability evaluation Introduced by software engineering practitioners, agile refers to a number of iterative and incremental software development practices that emphasize people’s needs, communication between developers and stakeholders and the ability to adapt to change In both the agile and UCD communities, however, a full understanding of user requirements is often seen as incompatible with early and quick development iterations We performed a literature review aiming to identify how agile teams have integrated UCD tools into their agile software development process to a better understanding of the user requirements without losing sight of the agile values and principles UCD tools adaptations and minimal-up-front design applied in agile development are among the approaches discovered in this study The findings could lead to a comprehensive user-centric software engineering that will overcome inherent problems faced by agile teams to understand user needs, priorities and goals

10 citations

Book ChapterDOI
01 Jan 2007

10 citations

Book ChapterDOI
Elena Tsiporkova1, Tom Tourwé1
31 Oct 2011
TL;DR: A prototype of a software tool implementing an entity resolution method for topic-centered expert identification based on bottom-up mining of online sources and a repository of user profiles to be used for technology scouting purposes is described.
Abstract: This paper describes a prototype of a software tool implementing an entity resolution method for topic-centered expert identification based on bottom-up mining of online sources. The tool extracts and unifies information extracted from a variety of online sources and subsequently builds a repository of user profiles to be used for technology scouting purposes.

10 citations

01 Jan 1996
TL;DR: A user requirement modeling vocabulary is described: a language to describe the necessary entities and their relationships to represent these user requirement models in a digital format.
Abstract: The Service Life/Asset Management project at the Institute for Research in Construction has identified "enabling" technologies critical to attaining the project objectives of optimizing the service life of building envelope components and systems The preliminary investigation concentrated on the need for close links between the enabling technology of user requirement modeling and those of service life prediction, life cycle economics, maintenance management, and risk analysis The integrating tool is an information technology (IT), namely product modeling The current research focuses on modeling of user requirementsThere is a rich history in the field of user requirement (performance concept) modeling in the research literature and existing standards documents However to date, there is no conceptual model and little vocabulary to represent the concepts described in much of this research literature and standards In addition, the language even in the applicable ISO standards needs additional refinement and more structureIn addition, to our knowledge, very little research has been done to represent these user requirement models in a digital format (ie product model) Although "performance" is identified as an attribute in the Building Construction Core Model, this representation is considered to be preliminary by the authors However, product models can provide the necessary structure and refinement for representing user requirements modelsThis paper describes a user requirement modeling vocabulary: a language to describe the necessary entities and their relationships The paper discusses similar systems developed to date; it identifies uses for a user requirement model, and it describes limitations of the proposed model

10 citations

01 Jan 2013
TL;DR: This demo introduces V:ISSUE:LIZER, a tool for exploring online communication and analyzing clarification of requirements over time and offers managers valuable information for their decision making.
Abstract: —This demo introduces V:I SSUE : LIZER , a tool forexploring online communication and analyzing clarication ofrequirements over time. V:I SSUE : LIZER supports managers anddevelopers to identify requirements with insufcient sharedunderstanding, to analyze communication problems, and toidentify developers that are knowledgeable about domain orproject related issues through visualizations. Our preliminaryevaluation shows that V:I SSUE : LIZER offers managers valuableinformation for their decision making. (Demo video: http://youtu.be/Oy3xvzjy3BQ).Index Terms —requirements clarication patterns; distributedrequirements engineering; communication of requirements I. I NTRODUCTION Large software projects often require collaboration acrossgeographically distributed sites and depend on online com-munication to perform activities related to clarifying require-ments. More frequently, teams are employing agile approachesthat aim to discover requirements iteratively and rely on fre-quent communication instead of requirements documentation.In such approaches, requirements are dened in the formof user stories, and ongoing discussions around these userstories serve as the main mechanism to clarify the meaningof requirements and to coordinate their implementation [1].Recording such discussions and decisions in online projectrepositories is an emerging best practice, not only in largeand distributed projects [2]. IBM

10 citations


Network Information
Related Topics (5)
Software development
73.8K papers, 1.4M citations
86% related
Component-based software engineering
24.2K papers, 461.9K citations
86% related
Software system
50.7K papers, 935K citations
84% related
Software construction
36.2K papers, 743.8K citations
84% related
Business process
31.2K papers, 512.3K citations
81% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
202334
202259
202157
202084
201991
201875