[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-240416-105":3,"detail-sidebar-cat-1-en-105":73,"doc-detail-240416-en":118},{"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":66,"head_meta":68,"extra_data":70,"updated_unix":72},105,"en","modeling-tool-for-managing-requirements-and-backlogs-in-agile-software-development","Modeling Tool for Managing Requirements and Backlogs in Agile Software Development","","Jira is widely used for issue tracking and backlog management in agile software development, but its tooling often flattens key agile concepts, hindering precise alignment between user stories and business process semantics expressed by BPMN or UML. This work proposes a diagrammatic, DSML-based alternative to Jira that integrates agile project concepts with established modeling standards while providing interoperability with Jira. The solution is developed via Agile Modeling Method Engineering, progressively improving technological readiness.",{"@graph":14,"@context":65},[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/modeling-tool-for-managing-requirements-and-backlogs-in-agile-software-development/240416/",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/modeling-tool-for-managing-requirements-and-backlogs-in-agile-software-development/240416.png","ImageObject",442,249,{"name":42,"@type":43},"Himbo","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-11-03","2026-09-11",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",18,{"@type":57,"mainEntity":58},"FAQPage",[59],{"name":60,"@type":61,"acceptedAnswer":62},"How is the tool engineered and developed?","Question",{"text":63,"@type":64},"Engineering is based on the metamodeling approach called Agile Modeling Method Engineering, implemented as a Design Science treatment with iterative steps that increase technological readiness.","Answer","https://schema.org",{"og:url":32,"og:type":67,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":69,"canonical":32},"index,follow",{"doc_id":71,"site_id":7},240416,1790978946,{"code":4,"msg":74,"data":75},"success",[76,80,85,90,95,100,105,109,114],{"id":77,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":78,"slug":79},11,90,"presentations",{"id":81,"doc_module":22,"doc_module_name":25,"category_name":82,"show_sort_weight":83,"slug":84},12,"Resumes",80,"resumes",{"id":86,"doc_module":22,"doc_module_name":25,"category_name":87,"show_sort_weight":88,"slug":89},14,"Invoices",70,"invoices",{"id":91,"doc_module":22,"doc_module_name":25,"category_name":92,"show_sort_weight":93,"slug":94},15,"Posters",60,"posters",{"id":96,"doc_module":22,"doc_module_name":25,"category_name":97,"show_sort_weight":98,"slug":99},16,"Social Media",50,"social-media",{"id":101,"doc_module":22,"doc_module_name":25,"category_name":102,"show_sort_weight":103,"slug":104},17,"Forms",40,"forms",{"id":55,"doc_module":22,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},"Letters",30,"letters",{"id":110,"doc_module":22,"doc_module_name":25,"category_name":111,"show_sort_weight":112,"slug":113},21,"Paper Templates",5,"papers-templates",{"id":115,"doc_module":22,"doc_module_name":25,"category_name":116,"show_sort_weight":4,"slug":117},158,"General","general-158",{"code":4,"msg":74,"data":119},{"doc_id":71,"user_id":120,"nickname":42,"user_avatar":121,"doc_module":22,"category_id":77,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":122,"file_id":123,"file_url":124,"file_type":125,"file_size":126,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":127,"language":128,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":129,"faqs":130,"seo_title":131,"seo_description":12,"update_tm":132,"read_time":26},687197100911,"https://ap-avatar.wpscdn.com/avatar/a000239b6f1da00475?x-image-process=image/resize,m_fixed,w_180,h_180&k=1785132997149421697","Modeling Tool for Managing Requirements and Backlogs in Agile Software Development  \nCătălina Floruț 1 and Robert Andrei Buchmann 1  \n1 University Babeș-Bolyai, Faculty of Economics and Business Administration, Business Informatics Research Center, str. T. Mihali 58-60, Cluj Napoca, 400591, Romania  \nAbstract  \nContext and motivation. Jira is an established tool for issue tracking, requirements and backlog management. Its popularity has impact on how agile software projects are conceptualized by project team members, often dictated by the data structures being managed within the tool. Question/problem. Although user stories should be traceable to both software artifacts and business processes, both sides being well served by modeling standards (BPMN, UML), the diagrammatic semantics are not leveraged by issue tracking tools; conversely, modeling tools have been more interested in code generation than in supporting issue trackers and agile practices.  \nPrincipal ideas/results. We propose a diagrammatic alternative to Jira, a modeling tool built around a domain-specific modeling language that integrates Agile Software Project concepts with modeling standards (BPMN, UML), while also ensuring interoperability with Jira. The engineering effort was based on the metamodeling approach known as Agile Modeling Method Engineering.  \nContribution. The DSML underlying the tool is a conceptual bridge between modeling standards and Jira, and it is developed as a Design Science treatment, iteratively increasing its technological readiness.  \nKeywords  \nAgile project management, Metamodeling, Domain-specific Conceptual Modeling, ADOxx, User story conceptualization  \n1. Introduction  \nTheory and practice of agile software development are sometimes diverging – while the agile paradigm's strongly principled foundations introduced its key concepts (e.g. epic, story), the actual operationalization of those concepts is often distorted by the employed tooling. For example, the concept of \"epic\" was introduced in Cohn's seminal book [1] as a user story too large to be easily managed, i. e. determined by sizing and complexity and requiring further slicing; however, issue trackers treat it as a level of aggregation, a way of grouping user stories for reporting purposes - a potential obstacle in the way of vertical story slicing [2] . The original conceptualization is flattened or oversimplified by tooling decisions – e.g., in different contexts an epic may be considered a type of backlog item, a large user story, a \"container of initiatives\" [3] . Although the user story's structure is well known (\"as a ...., I want ... because ...\"), in practice they are sometimes conflated with \"features\"or even \"tasks\" – an oversimplification witnessed first-hand by the authors of this paper in the local industry, which triggered the development of the tool hereby reported.  \nDomain-specific metamodeling tailors granular and rich conceptualizations for specialized purposes and fields of activity, providing design spaces that reflect those conceptualizations. This paper promotes  \nIn: J. Fischbach, N. Condori-Fernández, J. Doerr, M. Ruiz, J.-P. Steghöfer, L. Pasquale, A. Zisman, R. Guizzardi, J. Horkoff, A. Perini, A. Susi, M. Daneva, A. Herrmann, K. Schneider, P. Mennig, F. Dalpiaz, D. Dell’Anna, S. Kopczyńska, L. Montgomery, A. G. Darby, and P. Sawyer (eds.): Joint Proceedings of REFSQ-2022 Workshops, Doctoral Symposium, and Poster \\& Tools Track, Birmingham, UK, 21-03-  \n2022, published at [http://ceur-ws.org](http://ceur-ws.org)  \nEMAIL: [catalinaiulia.florut@gmail.com](catalinaiulia.florut@gmail.com) (C. Florut); robert.buchmann@ubbcluj.ro (R. A. Buchmann)  \nORCID: 0000-0002-7385-1610 (R. A. Buchmann)  \nCopyright © 2022 for this paper by its authors.  \nUse permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0)  \nCEUR Workshop Proceedings ([CEUR-WS.org](CEUR-WS.org))  \na diagrammatic modeling alternative to Jira that captures a supersed","cbCaieDfMOWrB9aB","https://ap.wps.com/l/cbCaieDfMOWrB9aB","pdf",3340081,6,"English","# Abstract\n# 1. Introduction\n# 2. Background, Motivation and Novelty","[{\"question\":\"How is the tool engineered and developed?\",\"answer\":\"Engineering is based on the metamodeling approach called Agile Modeling Method Engineering, implemented as a Design Science treatment with iterative steps that increase technological readiness.\"}]","Modeling Tool for Managing Requirements and Backlogs in Agile Software Development | PDF",1789161076]