|RE02 Tutorials: T01 | T03 | T04 | T05 | T06 | T07 | T08 | T09 | T10
|T03: "Agile Requirements Engineering" (Petra Becker-Pechau, Holger Breitling, Stefan Roock)
Agile Requirements Engineering
Tuesday, September 10th from 900 - 1730Abstract:
For an agile software development project change is something normal. As change occurs without fail, agile processes do not gather all requirement details at the beginning of a project. Instead developers and users learn just enough about the requirements to state the overall goal of the project and to formulate the first requirements in as much detail as necessary. Agile processes replace exhaustively documented requirements by a combination of simple and short requirement descriptions along with high-bandwidth communication between the customer and the developers. This allows to collect the requirements during the complete project, even parallel to implementation. Agile processes provide the project team with techniques to deal with those new or changed requirements rapidly in an organized way.
Following these ideas, eXtreme Programming (XP) and other agile processes promise to remove the burden of unnecessary rules, documents and workflows: "Do the simplest thing that could possibly work".
The tutorial is about the chances and limitations of agile approaches, especially the approach of eXtreme programming. It presents proven adaptations for complex project situations which for example occur if more than one channel for requirements exists or if the project is highly innovative. We show which RE techniques are compatible with agile processes.
|Last updated: 2002-05-14