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
••
01 Oct 2019TL;DR: The method called DEMOS focuses on end-users’ viewpoint concept to propose a participative and collaborative approach for information system co-construction and combines different participative tools such as photolanguage, mind map or User Story writing.
Abstract: This paper presents a method to support the design and the implementation of democratic information system in organizations. Ethical principle of democracy is today a challenge to propose a solution to the major issue of Shadow IT especially. Our method called DEMOS focuses on end-users’ viewpoint concept to propose a participative and collaborative approach for information system co-construction. It combines different participative tools such as photolanguage, mind map or User Story writing. This article presents strategies and intentions of DEMOS process with the MAP formalism and proposes a detailed description of DEMOS meta-model and key concepts. We conducted an experiment in 2018 with lifelong training service at the University Toulouse 1. A qualitative study evaluates the effectiveness of DEMOS.
1 citations
••
01 Jan 2016
TL;DR: This paper presents an agile requirements engineering approach to model multi-agent system requirements in the form of agent stories capturing skills and capabilities from the agent perspective that can be estimated, prioritized and traced separately.
Abstract: Agents and multi-agent systems are currently one of the most interesting research fields in the computer science community; especially the natural way of capturing the structure and the behavior of complex systems has stimulated this huge interest Lind (Issues in agent-oriented software engineering, 2000). As this paradigm advance, systematic methods are needed to support the development of multi-agent systems. General approaches for identifying, modeling, and analyzing user requirements for specific multi-agent software systems based on goal models have been suggested DeLoach (Multiagent systems engineering a methodology and language for designing agent systems, 1999), Tveit (A survey of agent-oriented software engineering, 2001). Nonetheless, those approaches suffer from rigidity and complexity for a customer to validate and review his needs as gathered by business analyst. In this paper, we present an agile requirements engineering approach to model multi-agent system requirements in the form of agent stories capturing skills and capabilities from the agent perspective. The agent stories can then be estimated, prioritized and traced separately. To illustrate the approach benefits, a Weapon Mass Destructive (WMD) system example is presented. The example is also used to compare our suggested approach with a goal-based one.
1 citations
••
01 Sep 2017TL;DR: The foundation for the career in the software engineering community is discussed, the overall strategy is to study programmer behavior in order to write algorithms that mimic that behavior, and a grounded theory study at a medium sized software company is proposed to determine whether factors outside the code influence source code summarization.
Abstract: Programmers rely on source code documentation to quickly understand what the source code does and how they would use it. Unfortunately, many programmers do not have the time to write and maintain source code documentation. A solution to this problem is to document and summarize source code automatically. Unfortunately, research efforts to automatically generate documentation have stalled recently because the research community does not know exactly what a summary of source code should include. To solve this problem, my overall strategy is to study programmer behavior in order to write algorithms that mimic that behavior. I have four key areas of work in which I execute that strategy: First, I determine what areas of code programmers read when they create documentation. Second, I find patterns in programmers' eye movements when they reading code. Third, I use recordings of developer-client meetings to extract user story information. Finally, I propose to conduct a grounded theory study at a medium sized software company to determine whether factors outside the code influence source code summarization. This paper discusses the foundation for my career in the software engineering community, and I seek the community's advice.
1 citations
••
30 Aug 2015TL;DR: This paper reflects the experiences encountered in a large-scale mission critical information system – ERICA, an information system for the emergency services in Finland – regarding design, implementation, and deployment and proposes more dynamic ways of system specification.
Abstract: Public tender processes typically start with a comprehensive specification phase, where representatives of the eventual owner of the system, usually together with a hired group of consultants, spend a considerable amount of time to determine the needs of the owner. For the company that implements the system, this setup introduces two major challenges: (1) the written down requirements can never truly describe to a person, at least to one external to the specification process, the true intent behind the requirement; (2) the vision of the future system, stemming from the original idea, will change during the specification process – over time simultaneously invalidating at least some of the requirements. This paper reflects the experiences encountered in a large-scale mission critical information system – ERICA, an information system for the emergency services in Finland – regarding design, implementation, and deployment. Based on the experiences we propose more dynamic ways of system specification, leading to simpler design, implementation, and deployment phases and finally to a better perceived quality.
1 citations
••
TL;DR: The hidden reasons behind the success of the agile strategy in software development projects are explained and how these factors are relevant to the agile project management strategy are described.
Abstract: — User satisfaction is a cornerstone indicator of any successful software project. Software projects are classified as successful only if the users are satisfied with the delivered software project result. Reducing the gap between users' expectations and the actual delivered software is one of the ultimate objectives of software project management. Therefore, it is essential to manage user expectations during the project, which is basically achieved by managing the user opinions related to the final performance of the software. However, this cannot be isolated from the adopted testing methodology, which is the way to guarantee the optimal user satisfaction. Furthermore, the stakeholder occupies a significant position in agile principles aligned with development teams. Flexibility to adapt stakeholders' late changes is also another gain in agility. Agility additionally focuses on the decentralized management approach to exploit any managing skills of the software project individuals. In this paper, we describe how these factors are relevant to the agile project management strategy. Our findings explain the hidden reasons behind the success of the agile strategy in software development projects.
1 citations