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
13 Sep 2021
TL;DR: In this paper, an effort estimation method for agile software development projects is presented. But, all these approaches have many problems that need to be addressed, and one of the most difficult aspects of software engineering is estimating effort in agile development.
Abstract: In every software development project, the software effort estimating procedure is an important process in software engineering and always critical. The consistency of effort and timeline estimation, along with several factors, determines whether a project succeeds or fails. Both academics and professionals worked on the estimation approaches in software engineering. But, all these approaches have many problems that need to be addressed. One of the most difficult aspects of software engineering is estimating effort in agile development. This study aims to provide an effort estimation method for agile software development projects. Because in software engineering, the agile method is widely used for the development of software applications. The development and usage of the agile method are described in depth in this study. The framework is configured with empirical data gathered by projects from the software industry. The test findings reveal that the estimation method has great estimation accuracy in respect of mean magnitude of relative error (MMRE) and Prediction of Error PRED (n). The suggested approach achieves more accuracy for effort estimation as compare to others.
6 citations
01 Jan 2009
TL;DR: Three development principles for and changes to the Extreme Programming development process to make it suitable for the development of rule-based systems are proposed and discussed.
Abstract: Recently, with the large-scale practical use of business rule systems and the interest of the Semantic Web community in rule languages, there is an increasing need for methods and tools supporting the development of rule-based systems. Existing methodologies fail to address the challenges posed by modern development processes in these areas, namely, the increasing number of end-user programmers and the increasing interest in iterative methods. To address these challenges, we propose and discuss the adoption of agile methods for the development of rule-based systems. The main contribution of this paper is three development principles for and changes to the Extreme Programming development process to make it suitable for the development of rule-based systems.
6 citations
01 Jan 2010
TL;DR: This chapter illustrates some of the typical challenges that were met during real-world commercial projects, and how they were solved.
Abstract: Two trends are becoming widespread in software development work—agile development processes and global delivery, both promising sizable benefits in productivity, capacity and so on. Combining the two is a highly attractive possibility, even more so in fast-paced and constrained commercial software engineering projects. However, a degree of conflict exists between the assumptions underlying the two ideas, leading to pitfalls and challenges in agile/distributed projects which are new, both with respect to traditional development and agile or distributed efforts adopted separately. Succeeding in commercial agile/distributed projects implies recognizing these new challenges, proactively planning for them, and actively put in place solutions and methods to overcome them. This chapter illustrates some of the typical challenges that were met during real-world commercial projects, and how they were solved.
6 citations
TL;DR: In this paper, a method for performing safety analysis based on user stories in an agile setting is described, using the input-Focused FMEA from the HiP-HOPS project to handle failure propagation in an efficient and easy-tounderstand way.
Abstract: In this paper, we describe a method for performing safety analysis based on user stories in an agile setting. The chosen analysis method is a generic hazards list, combined with FMEA -- both because it is simple and intuitive to use and because it is efficient. In order to handle failure propagation in an efficient and easy-tounderstand way, we have chosen to use the input-Focused FMEA from the HiP-HOPS project.
6 citations
01 Jan 2016
TL;DR: This paper starts defining what a user story is, how to write and test it, and what are main differences compared to “traditional” documented requirements and use cases, and how it is transformed into a multidimensional Story Map that help to manage size and complexity.
Abstract: Agile methodologies for software development favor customer involvement and thus a rapid feedback cycle on realized product increments. Such involvement is implemented in the activities around requirements (elicitation, analysis, development, management, change, validation), which in turn are often sustained by—and expressed in—“user story” format. This paper aims to show our experience in developing software system representing functional requirements mainly with “user stories,” and capturing also nonfunctional requirements (e.g., availability, security) in demanding domains. This paper starts defining what a user story is, how we write and test it, and what are main differences compared to “traditional” documented requirements and use cases. Then, it focuses on techniques we use for splitting and grooming, and how we transform a linear backlog into a multidimensional Story Map that help us to manage size and complexity.
6 citations