User story

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

An Ontology-based Approach to Automate the Software Development Process

Abstract: Ontologies are well-known for representing knowledge of a particular domain and an upcoming trend in the field of Computer Science to produce intelligent systems. Further, they help to solve traceability issues and transitive dependencies. Creation of software applications and use of software applications are increased due to new and innovative customer requirements and technologies. Development teams are following several Software Development methodologies to support and to produce quality software applications to the outer world. Agile methodologies are becoming more popular in small organizations and development teams to support the feature by feature development with less throughput. User Stories represent the actual user requirements in Agile. This paper proposes a solution named Sponto, which to automate the software development process using ontology-based approaches to produce reliable boilerplates to the developers and the communities to reuse the base and to build the software applications without spending a considerable amount of time on recreating the artifacts. The proposed solution supports and generates database scripts, Business Process Model diagrams, Java code snippets, and test cases from user stories.

Off-Shore agile software development

Abstract: Off-shore development is increasing in popularity. Off-shoring affects many things in our environment: what and where we build and deploy; how we budget and deliver services; and how and when we communicate. Can the high touch, high bandwidth model that Agile purports be applied to a situation where one of the fundamental tenants – a co-located team – is shattered? This panel will offer a forum to share and learn from industry practitioners and researchers on how to make off-shore software development work in an agile context.

Overview of Agile Software Development

Abstract: Agile thinking is an attempt to simplify things by reducing complexity of planning, by focusing on customer value, and by shaping a fruitful climate of participation and collaboration. There are a vast number of methods, techniques, best practices, that claim to be “agile.” In this chap. we want to give an overview of the most common ones. The five principles of a fractal team, which we introduced in Chap. 1, apply to most of them: self-similarity, goal orientation, self organization, self improvement, and vitality are cornerstones when implementing an organization capable of executing software projects in an agile way. The desire to establish flexible and efficient development processes which produce high quality results is not new and has not only been applied to software development: More than two decades ago, the manufacturing industry underwent dramatic changes, when the traditional production concepts of Taylor and Ford were challenged by extremely successful Japanese enterprises such as Toyota. The Western hemisphere was puzzled at how the competition from Far East seemed to be able to produce better quality at lower cost and quickly began to outperform the rest of the world. What happened? What was the secret of the amazing efficiency and innovation?

Estimation of Project Size Using User Stories

Abstract: There exist no concrete models for project size estimation in agile, contrary to traditional projects. In agile, contrasting approaches like standard component estimation, wideband-Delphi or expert consensus and function points technique do not proof much workable for early estimation of size, cost and duration due to uncertain initial requirements. Estimation in agile projects is important regardless of the immature nature of the requirements, on which they work. Next is the translation of effort estimates to project size or vice versa, which is equally important. Technique researched in this paper follows the user stories, which get us most possible accurate estimates. Number of story points with a story matter as well for correct size of story. There are certain specific metrics contained in a story which help in identification of its size and reliability. These factors, in weight age of story point are used to calculate sizing of an agile project.

User stories collection via interactive chatbot to support requirements gathering

Abstract: Nowadays, software products have become an essential part of human life. To build software, developers must have a good understanding of the requirements of the software. However, software developers tend to jumpstart system construction without having a clear and detailed understanding of the requirements. The user story concept is one of the practices of the requirements elicitation. This paper aims to present the work conducted to develop an Android chatbot application to support the requirements elicitation activity in software engineering, making the work less time-consuming and structured even for users not accustomed to requirements engineering. The chatbot uses Nazief & Adriani stemming algorithm to pre-process the natural language it receives from the users and artificial mark-up language (AIML) as the knowledge base to process the bot’s responses. A preliminary acceptance test based on the technology acceptance model results in an 83.03% score for users’ behavioral intention to use.