User story

About: User story is a research topic. Over the lifetime, 1078 publications have been published within this topic receiving 23717 citations.

System and method for monitoring software development and program flow

Abstract: A system and method for monitoring software development and project flow in the insurance industry using user stories is disclosed. The system and method include a communication interface that receives information included in communications; a processor and memory to: identify from the monitored communication a plurality of user stories; estimate a priority and assign a value to each story; store each story and associated priority and value as a product backlog; calibrate the difference in the assigned value of each story by comparing each story and the associated assigned value, and iteratively adjusting the assigned value based on the calibrated difference; and update the product backlog of user stories and associated calibrated assigned value; and a display device for displaying the status of the software development and project flow based on the stories remaining in the product backlog as compared to the completed user stories.

Staying agile in government software projects

Abstract: Can government software projects be agile? What do Scrum and XP practices have to offer in this regulated and highly political environment? In this experience report, I will discuss some of the unique challenges in our environment and how we have had to adapt these practices to produce commercial-grade software. I will provide a "report card" on our progress in applying Scrum and XP practices to a clinical data management project over a two-year period. In addition, I will describe the practices that were accepted "religiously", adapted to get the job done, and abandoned completely. In particular, I will discuss how we got around bootstrapping, rational tools, documentation needs, and managing a product backlog for a diverse, decentralized user community. Putting these practices to work was hard, but they resulted in better team communication, a more usable product, and improved partnership between the users and the development team. In addition, staying agile is just as hard as becoming agile.

Waterfall and agile requirements-based model for automated test cases generation

Abstract: Requirements-based testing is a testing approach in which test cases are derived from requirements. Requirements represent the initial phase in software developments life cycle. Requirements are considered the basis of any software project. Therefore, any ambiguity in natural language requirements leads to major errors in the coming phases. Moreover, poorly defined requirements may cause software project failure. There exist many software development models as waterfall model, agile model, etc. In this paper, we propose a novel automated approach to generate test cases from requirements. Requirements can be gathered from different models either waterfall model (functional and non-functional) or agile model. SRS documents, non-functional requirements and user stories are parsed and used by the proposed approach to generate test cases in which requirements with different types are covered. The proposed approach uses text mining and symbolic execution methodology for test data generation and validation, where a knowledge base is developed for multi-disciplinary domains.

Agile Requirements Engineering: A Research Perspective

Abstract: Agile methodologies have impact not only on coding, but also on requirements engineering activities. In the paper agile requirements engineering is examined from the research point of view. It is claimed that use cases are a better tool for requirements description than user stories as they allow zooming through abstraction levels, can be reused for user manual generation, and when used properly can provide quite good effort estimates. Moreover, as it follows from recent research, parts of use cases (namely event descriptions) can be generated in an automatic way. Also the approach to non-functional requirements can be different. Our experience shows that they can be elicited very fast and can be quite stable.

User stories template for object-oriented applications

Abstract: User stories present the mean of communication between customer and development team in agile methods; this paper provides a new user stories voice aimed to ease and automate analysis of objects and their action from the user story using OOADARE (Object-oriented Analysis and Design Approach for the Requirements Engineering) approach [1]. OOADARE approach was also missing a communication mean with the customer; user stories with the new template will do the job.