[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-240856-105":3,"doc-detail-240856-en":81,"detail-sidebar-cat-1-en-105":99},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","bridge-between-agile-and-traditional-methods-agile-requirements-documentation-structuring-ardocs","Bridge Between Agile and Traditional Methods - Agile Requirements Documentation Structuring (ARDocS)","","Software Requirements Engineering (SRE) differs substantially between agile and traditional development, especially in how requirements are documented. Traditional methods typically require a single structured Software Requirements Specification, while agile relies on multiple artefacts with less upfront documentation. In hybrid environments where teams from both approaches collaborate, these mismatches can create communication and understanding challenges. This paper presents ARDocS, translating agile artefacts into structured documentation compatible with traditional practices through metamodeling and concept mapping. The approach is validated via a case study combining Scrum with the VOLERE template.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/bridge-between-agile-and-traditional-methods-agile-requirements-documentation-structuring-ardocs/240856/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/bridge-between-agile-and-traditional-methods-agile-requirements-documentation-structuring-ardocs/240856.png","ImageObject",442,249,{"name":42,"@type":43},"Ben Jamin","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-28","2026-09-11",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",15,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What is ARDocS and what problem does it address?","Question",{"text":63,"@type":64},"ARDocS is an approach that bridges agile and traditional requirements documentation. It addresses communication challenges in hybrid development by converting agile artefacts into structured documentation compatible with traditional methods.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How does ARDocS translate agile artefacts for traditional documentation usage?",{"text":68,"@type":64},"ARDocS uses metamodeling to define and specify agile and traditional documentation across multiple abstraction levels, then maps concepts between the two metamodels.",{"name":70,"@type":61,"acceptedAnswer":71},"What validation was used to evaluate ARDocS?",{"text":72,"@type":64},"The approach was validated through a case study applying ARDocS to Scrum (agile) and the VOLERE template (traditional) to consolidate information into understand-able structured documentation for both teams.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},240856,1791480471,{"code":4,"msg":82,"data":83},"success",{"doc_id":79,"user_id":84,"nickname":42,"user_avatar":85,"doc_module":22,"category_id":86,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":87,"file_id":88,"file_url":89,"file_type":90,"file_size":91,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":92,"language":93,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":94,"faqs":95,"seo_title":96,"seo_description":12,"update_tm":97,"read_time":98},2336478466772,"https://ap-avatar.wpscdn.com/davatar_3d24733baf745e90a7e4bdd5f77d97b2",11,"Ingénierie des Systèmes d’Information  \nVol. 29 , No. 6, December, 2024, pp. 2091-2104  \nJournal homepage: [http://iieta.org/journals/isi](http://iieta.org/journals/isi)  \n\n| Bridge Between Agile and Traditional Methods: Agile Requirements Documentation Structuring (ARDocS)\u003Cbr>Hind Wissam Kalfat1,2* , Mourad Oussalah2 , Azeddine Chikh1\u003Cbr>1 Computer Sciences Department, LRIT Laboratory, Tlemcen University, Tlemcen 13000, Algeria\u003Cbr>2 LS2N, CNRS, Ecole Centrale Nantes, Nantes Université, UMR 6004, Nantes F-44000, France [Corresponding Author Email: hind-wissam.kalfat@univ-nantes.fr](Corresponding Author Email: hind-wissam.kalfat@univ-nantes.fr) | |\n| --- | --- |\n| Copyright: ©2024 The authors. This article is published by IIETA and is licensed under the CC BY 4.0 license\u003Cbr>([http://creativecommons.org/licenses/by/4.0/](http://creativecommons.org/licenses/by/4.0/)). |  |\n\n[https://doi.org/10.18280/isi.290601](https://doi.org/10.18280/isi.290601) ABSTRACT  \n\n| Received: 2 September 2024\u003Cbr>Revised: 13 November 2024\u003Cbr>Accepted: 26 November 2024\u003Cbr>Available online: 25 December 2024 | 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. |\n| --- | --- |\n| Keywords:\u003Cbr>software requirements engineering, traditional requirements, agile requirements documentation, hybrid documentation, meta-modeling |  |\n\n1. INTRODUCTION  \nSoftware requirements engineering (SRE) is considered asthe most important aspect of software development as it consists on understanding the product to be developed.  \nSRE is a process that differs from one method to another: in traditional approaches like waterfall, SRE is carried out at the very beginning of the project, enabling an upstream planning of the entire product. The plan is then strictly followed by the development team throughout the rest ofthe project [1] . These approaches are highly effective in safety-critical systems. According to Martins and Gorchek they are preferred in such domains because the new ones are not yet mature or not convincing enough [2] . Indeed, projects in defence or healthcare need a strict regulatory standard that takes every detail into account; to insure they stay within budget and time while addressing the correct requirements. On the other side, in agile approaches, SRE is informal and highly dependent on individuals’ knowledge and skills. It is carried out throughout all the Software Development Life Cycle (SDLC) and requirements evolve as the project progresses [3] . These approaches are widely adopted by companies that prioritize customer feedback and adaptability. For instance, Microsoft’s commitment to agile principles helped the company to continuously evolve, stay at the forefront of technological innovation and respond to market demands. By embedding SRE throughout","cbCaioPHlL5QaofC","https://ap.wps.com/l/cbCaioPHlL5QaofC","pdf",1495670,14,"English","# Introduction\n## Software Requirements Engineering in Traditional and Agile Methods\n## Documentation as a Communication Tool in Hybrid Development","[{\"question\":\"What is ARDocS and what problem does it address?\",\"answer\":\"ARDocS is an approach that bridges agile and traditional requirements documentation. It addresses communication challenges in hybrid development by converting agile artefacts into structured documentation compatible with traditional methods.\"},{\"question\":\"How does ARDocS translate agile artefacts for traditional documentation usage?\",\"answer\":\"ARDocS uses metamodeling to define and specify agile and traditional documentation across multiple abstraction levels, then maps concepts between the two metamodels.\"},{\"question\":\"What validation was used to evaluate ARDocS?\",\"answer\":\"The approach was validated through a case study applying ARDocS to Scrum (agile) and the VOLERE template (traditional) to consolidate information into understand-able structured documentation for both teams.\"}]","Bridge Between Agile and Traditional Methods - Agile Requirements Documentation Structuring (ARDocS) | PDF",1789166537,5,{"code":4,"msg":82,"data":100},[101,104,109,113,117,122,127,132,136],{"id":86,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":102,"slug":103},90,"presentations",{"id":105,"doc_module":22,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},12,"Resumes",80,"resumes",{"id":92,"doc_module":22,"doc_module_name":25,"category_name":110,"show_sort_weight":111,"slug":112},"Invoices",70,"invoices",{"id":55,"doc_module":22,"doc_module_name":25,"category_name":114,"show_sort_weight":115,"slug":116},"Posters",60,"posters",{"id":118,"doc_module":22,"doc_module_name":25,"category_name":119,"show_sort_weight":120,"slug":121},16,"Social Media",50,"social-media",{"id":123,"doc_module":22,"doc_module_name":25,"category_name":124,"show_sort_weight":125,"slug":126},17,"Forms",40,"forms",{"id":128,"doc_module":22,"doc_module_name":25,"category_name":129,"show_sort_weight":130,"slug":131},18,"Letters",30,"letters",{"id":133,"doc_module":22,"doc_module_name":25,"category_name":134,"show_sort_weight":98,"slug":135},21,"Paper Templates","papers-templates",{"id":137,"doc_module":22,"doc_module_name":25,"category_name":138,"show_sort_weight":4,"slug":139},158,"General","general-158"]