Agile Requirements Engineering

Question 1

Challenges in RE

Answer 1

• Reqs change over time
• Devs and reqs engineers often misinterpret/fail to capture user needs
• Stakeholders are not clear about their needs
• Conflicting stakeholder needs

Question 2

Agile RE Concepts/Practices

Answer 2

• Evolutionary reqs
• Minimal big reqs up front
• Incremental/iterative implementation of reqs
• Accommodate change late in dev life cycles
• Minimal requirements documentation
• Just-in-time reqs

Question 3

Agile RE Process

Answer 3

1. Identify high level features
2. Prioritize features
3. For each feature, gather details JIT from stakeholders
4. With gathered details, proceed to dev (Test Driven Testing) and acceptance testing

Question 4

Test Driven Development

Answer 4

• Create test cases before writing code
• Used in agile dev

Question 5

Problem Formulation/Education

Answer 5

**Objectives: **
* establish rapport among stakeholders
* learn business process of customer
* identify user classes
Output: Producer concept statement

Question 6

Agile RE Features

Answer 6

1. Features
2. Stories
3. Tasks
4. Development

Question 7

Advantages of Agile RE

Answer 7

• Accommodates change even late in dev cycle
• Reduces reqs risks and resolves conflict
• Cost-effective

Question 8

Disadvantages of Agile RE

Answer 8

• Minimal process/decompostion of activities in RE phase
• Non-functional reqs aren’t well defined