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
01 Jul 1998
TL;DR: It appears that users found the procedural "what to do" aids useful, but aids designed to help the user understand the purpose and dynamics "why do it" of the task were not effective.
Abstract: : This research project explored the feasibility of improving user performance on manpower planning tasks by employing a "user coach." A user coach is a software aid, often built directly into software applications, that assists the user at critical stages. The user coach developed for this project closely resembles the "wizards" that are commonly used in commercial software today. The user coach was applied to a software tool known as SKIPPER, a manpower modeling tool that is employed by the Enlisted Community Managers (ECMs) at the Bureau of Navy Personnel (BUPERS). This report describes the user coach and documents a formal evaluation of its effectiveness. The evaluation compared the use and understanding of SKIPPER (1) with the coach, (2) with the coach and a visual metaphor (a hydraulic system representation of the enlisted personnel system), and (3) without the coach or the metaphor. All users (experienced and inexperienced) were able to complete their manpower plans significantly faster using the coach than using SKIPPER unaided. Neither performance on the manpower planning task, nor the user's understanding of the task, was influenced by providing a visual picture of the process. It appears that users found the procedural "what to do" aids useful, but aids designed to help the user understand the purpose and dynamics "why do it" of the task were not effective.

1 citations

Dissertation
01 Jul 2013
TL;DR: This system is expected to facilitate students in obtaining scholarship information and facilitate in obtaining the desired scholarship through AIS (Academic Information System) web.
Abstract: Technological developments allow people to create technology that can facilitate their work now, including information technology. Information technology can be petrified in speeding up the information to someone. Administrative information systems development scholarship aims to facilitate students in finding information on scholarships and get the scholarship. This information systems development methods using extreme programming. This method prioritizes client as a resource person who understands about the system being designed, from the client will be obtained user story. Steps of this method include: planning, design, coding, and testing. In addition, this information systems are designed with the concept of UML (Unified Modeling Language) and was developed using the PHP programming language that based on web and management using Oracle as its database. Administrative information system created has features to process data scholarship, offering scholarships, see scholarship offers, sign up scholarship, and recipients know the results. This system is expected to facilitate students in obtaining scholarship information and facilitate in obtaining the desired scholarship through AIS (Academic Information System) web. Keyword: Information System, Extreme Programming, UML, PHP, Oracle.

1 citations

Book ChapterDOI
01 Jan 2011
TL;DR: Here’s a shocker: your main quality objective in software development is to get a working program to your user that meets all their requirements and has no defects.
Abstract: Here’s a shocker: your main quality objective in software development is to get a working program to your user that meets all their requirements and has no defects. That’s right: your code should be perfect. It meets all the user’s requirements and it has no errors in it when you deliver it. Impossible, you cry? Can’t be done? Well, software quality assurance is all about trying to get as close to perfection as you can - albeit within time and budget. (You knew there was a catch, didn’t you?)

1 citations

Book ChapterDOI
01 Jan 2016
TL;DR: Two empirical studies in industry seem to confirm the assumption, that large interactive surface technologies could bring the support for the collaboration of Agile teams to a new level, potentially making the teams more productive.
Abstract: Agile software development is characterized by very intensive communication and collaboration among members of the software development team and external stakeholders. In this context, we look specifically at cardwalls, noting that despite the wide availability of digital cardwalls, most Agile teams still use physical cardwalls to support their collaborative events. This is true even though a physical cardwall hinders efficient distributed software development and causes extra effort to capture story artefacts into digital tools to meet traceability and persistence requirements. We conducted two empirical studies in industry to understand the use of existing digital Agile cardwalls and to find out the needs for an ideal digital Agile cardwall. The first study was with eight Agile teams of committed digital cardwall users. The study showed the reasons why some teams use projected digital cardwalls and their detailed experiences with them. The study showed that most digital cardwalls seem not be sufficient for the highly interactive and collaborative Agile workstyle. The second study was with eleven Agile companies. The study comprised of the development of aWall, a software prototype of a large interactive high-resolution multi-touch display that supports varied Agile meetings where cardwalls are used. The results of the study emerged with design considerations for digital Agile cardwalls from the evaluation of aWall in a user workshop. Both studies, which were conducted concurrently, began with an interest in new large interactive surface technologies which might have the potential to provide not only the required interaction possibilities to support intensive collaboration, but also the required large display format necessary for a collaborative space. The results of the studies collectively seem to confirm our assumption, that large interactive surface technologies could bring the support for the collaboration of Agile teams to a new level, potentially making the teams more productive.

1 citations

Journal Article
TL;DR: The key objective of this paper is to mainly focus on bridging the gap between the customer and end user needs to the final product by adapting agile type methodologies to check whether testing the requirements all the time thru the product design and development achieve the possible outcome like a quality product.
Abstract: Quality is a big concern and is becoming a challenge for the software organizations. About 60% of the projects are stalled for not fulfilling the quality norms. Customers or end users have some different expectation with them based on their perceptions and requirement and the product development is done with different perception. Hence this is building a gap between the end product and the end user. The reason for the failure is very simple. The key objective of this paper is to mainly focus on bridging the gap between the customer and end user needs to the final product. This can be achieved by concentrating on the requirements phase. And including the quality by testing the requirements are properly documented and are updated. A project manager is to mainly concentrate on bringing quality aspects right from the Requirement collection. A project manager is always the one who is aligned with all the phases of the software development life cycle. The methodology used is adapting agile type methodologies to check whether testing the requirements all the time thru the product design and development achieve the possible outcome like a quality product. A sample questionnaire is circulated to the software engineers, managers and a sample population and came to know that the procedure which we are adopting lead to deliver a successful quality product.

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