Requirements elicitation and documentation are complex activities. So, not only the requirements themselves but also the people involved and the means for managing the requirements will evolve during the project. For example, it might be necessary to add RE personnel, to document templates, or to change the requirements classification scheme. In summary, especially in participative RE, the underlying platform as well the RE approach must be flexible. As the well-known Wikipedia shows, wikis provide a flexible platform for asynchronous collaboration to create content in general. In this article, we investigate how to adapt this approach to support active stakeholder participation in RE. We include a document structure for wiki-based RE and discuss potential problems and solutions based on our experience

different involvements—for example, somestakeholders are entitled to make decisionsand others aren’t.It’s important to address these challenges byfostering communication and decision making.In particular, project participants need a way todetect misunderstandings and conflicts andsolve them as early as possible. This communi-cation can be synchronous—through face-to-face meetings and videoconferencing, for exam-ple—or asynchronous, which is our focus here.Requirements elicitation and documenta-tion are complex activities. So, not only the re-quirements themselves but also the people in-volved and the means for managing therequirements will evolve during the project.For example, it might be necessary to add REpersonnel, to document templates, or tochange the requirements classification scheme.In summary, especially in participative RE, theunderlying platform as well the RE approachmust be flexible.As the well-known Wikipedia shows, wikisprovide a flexible platform for asynchronouscollaboration to create content in general.