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
Proceedings ArticleDOI
12 Nov 2015
TL;DR: This work considers also, in the construction of the user interests, what he is looking for and what the user doesn't want to find in the future results to build interests that best match his information needs.
Abstract: User profiles and interests have become essential for personalizing information search and retrieval. Indeed, traditional Information Retrieval Systems (IRS) don't integrate the user in the search process. Also, users do not always find what they need after a single query. Instead, they often issue multiple queries, incorporating what they learned from the previous results to iterate and refine how they express their information needs. So we rely on this process to learn the user information needs without asking him explicitly. This is achieved by capturing his judgments on the retrieved results. We consider also, in the construction of the user interests, what he is looking for and what the user doesn't want to find in the future results to build interests that best match his information needs.

1 citations

Book ChapterDOI
24 Mar 2020
TL;DR: It is found that, in general, the different requirements representations have no statistically significant impact on the number of derived tests, but specific affordances of the representation effect test quality, e.g., traditional textual requirements make it easier to derive less abstract tests, whereas goal models yield less inconsistent test purpose descriptions.
Abstract: [Context and Motivation] One must test a system to ensure that the requirements are met, thus, tests are often derived manually from requirements. However, requirements representations are diverse; from traditional IEEE-style text, to models, to agile user stories, the RE community of research and practice has explored various ways to capture requirements. [Question/problem] But, do these different representations influence the quality or coverage of test suites? The state-of-the-art does not provide insights on whether or not the representation of requirements has an impact on the coverage, quality, or size of the resulting test suite. [Results] In this paper, we report on a family of three experiment replications conducted with 148 students which examines the effect of different requirements representations on test creation. We find that, in general, the different requirements representations have no statistically significant impact on the number of derived tests, but specific affordances of the representation effect test quality, e.g., traditional textual requirements make it easier to derive less abstract tests, whereas goal models yield less inconsistent test purpose descriptions. [Contribution] Our findings give insights on the effects of requirements representation on test derivation for novice testers. Our work is limited in the use of students.

1 citations

Journal ArticleDOI
TL;DR: The research proposes to improve the requirement elicitation process by combining i*organizational models with standard Agile-Scrum methodology through a real-life health service provider scenario to ensure the social aspects of the organizational actor’s strategic dependency and rationale are considered.
Abstract: Eliciting requirements is one of the key aspects of the software development life cycle. Incorrect determination of the requirements can lead to the failure of the projects. Traditional waterfall method does not accommodate changing requirements easily while agile methodology welcomes the changing requirements even at the later phases of the development life cycle. The aim of the research is to improve the agile requirement elicitation process to ensure quality product is developed that aligns to the organizational strategy and its high value initiatives. Requirement elicitation process within agile projects should consider organisational actor’s strategic dependency and rationale to ensure alignment with organisational strategy. We propose to improve the requirement elicitation process by combining i*organizational models with standard Agile-Scrum methodology through a real-life health service provider scenario. The aim of our methodology is to ensure the social aspects of the organizational actor’s strategic dependency and rationale are considered. We argue the requirement process could be significantly improved by combining these two aspects; Agile-Scrum methodology will address the requirements through user stories, vision document, epics and i*organizational model will include the social aspects of the organization to reduce the gap between the project goal and organization goal.

1 citations

Journal Article
TL;DR: User stories – the common artefacts used in many agile software development techniques – were used in the early stage of the WAVES project to shape future developments of existing software for authoring and playing virtual scenarios.
Abstract: Interactive virtual scenarios and simulations in scenario-based learning are recognised by many teaching and learning communities as effective tools for developing reasoning, and for safe training in workplace competency. The WAVES project takes scenario-based learning ‘out-of-the-box’, to make it more accessible for a wide range of professions. User stories – the common artefacts used in many agile software development techniques – were used in the early stage of the WAVES project to shape future developments of existing software for authoring and playing virtual scenarios. The use of a specific template of a user story together with a gaming activity for sorting of all obtained user stories helped to simplify and accelerate the creation of user requirement specification document.

1 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