2010Unpublished venueRequires access

Applying user stories for requirements specification

Rok Doltar

Open publisher page 0 citations

Abstract

My thesis describes a variety of methods for writing software specifications with intention to examine possible improvements of user requirements acquisition and software development efficacy. User stories, as one of the most promising among agile methods of user requirements acquisition, are described in greater detail. The course of development with user stories is described on a typical project, that I was working on in an enterprise named RRC. The comparison of the internal method of RRC enterprise and user stories shows that savings in time and amount of work are possible if we decide to switch from the currently used method to user stories, but we have more difficulties solving disagreements with our customer, when he cannot or will not participate in the process. User stories offer by all means a great deal of benefits, therefore their application in practice is reasonable and enterprises should be acquainted with this relatively new method of user requirements acquisition.

About this research paper

What this paper is about

My thesis describes a variety of methods for writing software specifications with intention to examine possible improvements of user requirements acquisition and software development efficacy. User stories, as one of the most promising among agile methods of user requirements acquisition, are described in greater detail. The course of development with user stories is described on a typical project, that I was working on in an enterprise named RRC. The comparison of the internal method of RRC enterprise and user stories shows that savings in time and amount of work are possible if we decide to switch from the currently used method to user stories, but we have more difficulties solving disagreements with our customer, when he cannot or will not participate in the process. User stories offer by all means a great deal of benefits, therefore their application in practice is reasonable and enterprises should be acquainted with this relatively new method of user requirements acquisition.

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

My thesis describes a variety of methods for writing software specifications with intention to examine possible improvements of user requirements acquisition and software development efficacy. User stories, as one of the most promising among agile methods of user requirements acquisition, are described in greater detail. The course of development with user stories is described on a typical project, that I was working on in an enterprise named RRC. The comparison of the internal method of RRC enterprise and user stories shows that savings in time and amount of work are possible if we decide to switch from the currently used method to user stories, but we have more difficulties solving disagreements with our customer, when he cannot or will not participate in the process. User stories offer by all means a great deal of benefits, therefore their application in practice is reasonable and enterprises should be acquainted with this relatively new method of user requirements acquisition.

Key concepts: User story, User requirements document, Agile software development, Computer science, Requirement, Process (computing), Software engineering, Variety (cybernetics)

Related papers

Back to paper searchBrowse research topicsOriginal source
Applying user stories for requirements specification — Research Paper | ScholarLens