Change search
ReferencesLink to record
Permanent link

Direct link
Requirement Engineering: A comparision between Traditional requirement elicitation techniqes with user story
Linköping University, Department of Computer and Information Science.
Linköping University, Department of Computer and Information Science.
2011 (English)Independent thesis Advanced level (degree of Master (Two Years)), 30 credits / 45 HE creditsStudent thesis
Abstract [en]

Requirements are features or attributes which we discover at the initial stage of building a product. Requirements describe the system functionality that satisfies customer needs. An incomplete and inconsistent requirement of the project leads to exceeding cost or devastating the project. So there should be a process for obtaining sufficient, accurate and refining requirements such a process is known as requirement elicitation. Software requirement elicitation process is regarded as one of the most important parts of software development. During this stage it is decided precisely what should be built. There are many requirements elicitation techniques however selecting the appropriate technique according to the nature of the project is important for the successful development of the project.

Traditional software development and agile approaches to requirements elicitation are suitable in their own context. With agile approaches a high-level, low formal form of requirement specification is produced and the team is fully prepared to respond unavoidable changes in these requirements. On the other hand in traditional approach project could be done more satisfactory with a plan driven well documented specification. Agile processes introduced their most broadly applicable technique with user stories to express the requirements of the project. A user story is a simple and short written description of desired functionality from the perspective of user or owner. User stories play an effective role on all time constrained projects and a good way to introducing a bit of agility to the projects. Personas can be used to fill the gap of user stories.

Place, publisher, year, edition, pages
2011. , 90 p.
Keyword [en]
Requirement Engineering, Agile Methodology, Traditional Methodology, Requirement Elicitation, interview, Brainstorming, focus groups, questionnaire, observations, protocol analysis, contextual inquiry, Laddering, card sorting, requirement reuse, joint application development, prototyping, protocol analysis, user story, personas, INVEST Model
National Category
Engineering and Technology
URN: urn:nbn:se:liu:diva-70174ISRN: LIU-IDA/LITH-EX-A—11/023—SEOAI: diva2:436409
Subject / course
Computer and information science at the Institute of Technology
Available from: 2011-08-23 Created: 2011-08-23 Last updated: 2011-08-23Bibliographically approved

Open Access in DiVA

fulltext(939 kB)433 downloads
File information
File name FULLTEXT01.pdfFile size 939 kBChecksum SHA-512
Type fulltextMimetype application/pdf

Search in DiVA

By author/editor
Hussain, DostdarIsmail, Muhammad
By organisation
Department of Computer and Information Science
Engineering and Technology

Search outside of DiVA

GoogleGoogle Scholar
Total: 433 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

Total: 403 hits
ReferencesLink to record
Permanent link

Direct link