Bridge Between Agile and Traditional Methods: Agile Requirements Documentation Structuring (ARDocS)
Résumé
Software Requirements Engineering (SRE) varies significantly between agile and traditional methods, particularly in documentation practices. In traditional methods, for instance, the team is required to produce one structured and detailed document which is the software requirements specification. While agile methods require less documentation, which is spread over several artefacts. These differences can lead to communication challenges in hybrid development environments, where both agile and traditional teams collaborate. In such contexts, documentation can serve as a crucial communication tool, bridging the gap between the two methods. This paper proposes ARDocS approach, which translates agile artefacts into a structured document compatible with traditional methods. ARDocS involves defining and specifying agile and traditional documentation through multiple abstraction levels using metamodeling, and mapping the concepts between these two metamodels. We validate our approach through a case study that applies ARDocS to the Scrum method for agile and the VOLERE template for traditional. ARDocS effectively consolidates information from various agile artefacts into structured documentation that can be understood and used by both agile and traditional teams.