User story

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

A Methodological Approach to Identify Type of Dependency from User Requirements

Abstract: Agents exhibit a high degree of inter-agent cooperation to achieve designated goals. The success of Multi-Agent System (MAS) depends on how well these agents cooperate with each other. Modeling cooperation with a thrust in finding an appropriate agent for delegating a task is a challenging area of MAS as it requires thorough analysis of the dependencies that exist among agents. In MAS, an agent may exhibit various dependencies viz goal, task, soft goal or resource that may complicate the final system. To handle the intricacy of such a system, it is crucial to identify various inter-agent dependencies from user requirements during the early phases of requirements engineering. This work employs notion of user story, composed of users’ requirements in modeling the type of dependencies in an Agent Oriented System. A methodological approach using Fuzzy set theory, Lexical analysis and Vector Model is used to identify Type of Dependency (ToD) from user requirements well before the development of final system. Lexical analysis is applied to obtain index terms from User Stories that eventually are classified in various categories viz. (i) Quality requirements (ii) Supplementary guidelines and (iii) want of a Resource or Information. These index terms are analyzed on the basis of their physical occurrences in User Stories as well as the importance as perceived by users to identify inter-agent dependencies. The inter-agent dependencies, if identified at the requirements stage, assist the developers in addressing inter-agent coordination issues to reduce the trivial dependencies and thereby unnecessary communication overheads. A case study using Materials e-Procurement System is presented to illustrate the proposed approach.

Challenges of Gathering User Requirement in eXtreme Programming Project: A Case Study of Highway Construction Monitoring System

Abstract: The successfulness of a software development project is not only based on the tools and the technology used but also really depends on how the developed software meets the end user requirements. Involving end user as an active member of software development team, one of the popular agile methods known as eXtreme Programming (XP) had been selected as the software development methodology. This paper is focused on one of the main practices called on-site customer. The project under study is a web based Highway Construction Monitoring System (HIGHCONS). Challenges related to its implementation throughout the development process and also the suitable solutions in facing the challenges were also considered.

The User Environment Design

Abstract: A new product or feature set must have the appropriate function and structure to support a natural flow of interaction. For that, Contextual Design uses the User Environment Design. The User Environment Design is a floor plan of the new product showing the places in the product, the function in that place, and the links between one place and another. It shows the parts of the product from the user's point of view and helps the team think structurally about the product. In this chapter we describe the User Environment Design, show how it is represented, and lay out the process for building one from the storyboards.

Systems, methods and computer program products for analyzing agile scrum team efficiency

Abstract: A completion time is obtained for each phase of a plurality of phases in a user story. Completion times of phases are obtained for each user story of a plurality of user stories. A maximum completion time, a minimum completion time and a composite metric are determined for phases common among the user stories. A chart displays the phases common among the user stories over the sprint time period. Sprint time period is used to define a first axis and phase completion time is used to define a second axis. A vertical bar is displayed for each respective phase, parallel with the second axis, having a top end on the second axis based on a maximum completion time for the respective phase and a bottom end on the second axis based on a minimum completion time.

Developer Stories: Improving Architecture in Agile Practice

Abstract: Within the field of Software Engineering emergence of agile methods has been a hot topic since the late 90s. eXtreme Programming (XP) ([1]) was one of the first agile methods and is one of the most well-known. However research has pointed to weaknesses in XP regarding supporting development of viable architectures. To strengthen XP in this regard a new practice: Developer Stories ([2]) was introduced in 2006 - mainly based on a theoretical argumentation.