Using collaborative methods effectively in requirements management

Typical issues in requirements management for software development characterised by domain-driven design are highlighted using a consistent practical example.

For each individual method, a concrete, consistent practical example is used to explain why which collaborative method is suitable when and which typical issues can be dealt with in a focussed manner.

The different perspectives and partial results or artefacts not only help to make more informed decisions in the project, but also to create more transparency and traceability in the project process.