Requirements Engineering in an Agile Environment

The Requirements Engineering (RE) process typically dominates the quality of a project. The requirement methods in a project team are supposed to be a crucial part of the whole application development process. Nowadays lean and agile development is becoming more and more popular in industry. A lot of project teams work in an agile environment so that they can have speedy delivery of high-quality software. Normally the work of the teams implementing an agile methodology is versatile and changeable. This suggests that the requirements of the projects may also be regularly modified, which is a variant to the traditional RE Requirements Engineering that relies upon long and detailed documentation. This project (Requirements Engineering in an Agile Environment) looks into how to conduct a RE Requirements Engineering process under an agile environment – so that there exist relatively formal but agile and changeable requirements within a project. The strategy planned to be utilized are literature study, a case study carried out in 2 software development teams in the Test Tool & Support Section at SonyEricsson Mobile Communications AB, and one pilot in each team based on the case study. There were 11 workers surveyed, which includes 8 developers, 2 product owners and one scrum master. The evaluation on the pilots was primarily based on the feedback from the interviewees on the pilot. The end result of the assessment was that one of the teams (BRAT team) should adopt user experiences for user-related requirements, “done criteria” and non-functional requirements….

Contents: Requirements Engineering in an Agile Environment

1  Introduction
1.1  Background
1.2  Problem description
1.3  Purposes
1.4  Delimitations
2  Method
2.1  Design of the study
2.1.1  Literature study
2.1.2  Interviews
2.1.3  Observations
2.2  Research Quality
2.3  Time Frame
3  Theoretical Framework
3.1  Requirements Engineering
3.1.1  Functional requirements and non functional requirements (NFRs)
3.1.2  Use cases VS. User stories
3.2  Agile Software Development
3.2.1  Introduction
3.2.2  Agile development process VS. Waterfall process
3.2.3  Requirements Engineering in Agile environments
3.2.4  Software Testing in an Agile Environment
3.3  Scrum
3.3.1  Process
3.3.2  Roles
3.3.3  Characteristics
4  Case study
4.1  Background of the organization
4.1.1  Background of SEMC
4.1.2  Background of Test Tools & Support Section
4.2  Teams and Products
4.2.1  BRAT
4.2.2  QC
4.3  Current situations
4.3.1  Product process
4.3.2  Meeting composition
4.3.3  Sprints distribution
4.3.4  Customer Involvement
4.3.5  Documentation
4.3.6  Testing
4.3.7  Tools
5  Analysis
5.1  Reflected problems
5.1.1  Requirements not detailed enough
5.1.2  Mixed formats of requirements
5.1.3  Unclear bug description
5.1.4  QC team not always understanding the requirements
5.1.5  No formal documentations
5.1.6  No non functional requirements (NFRs)
5.1.7  No full time testers
5.1.8  Developers rather than PO demonstrating the product to customers
5.2  Possible improvements
5.2.1  BRAT team
5.2.2  QC team…

Source: Uppsala University Library

Download URL 2: Visit Now

Leave a Comment