需求与敏捷的结合：无人区还是机遇之地？

IF 3.3 4区计算机科学 Q2 COMPUTER SCIENCE, SOFTWARE ENGINEERING IEEE Software Pub Date : 2024-04-05 DOI:10.1109/ms.2024.3363248

Fabiano Dalpiaz, Jan-Philipp Steghöfer

{"title":"需求与敏捷的结合：无人区还是机遇之地？","authors":"Fabiano Dalpiaz, Jan-Philipp Steghöfer","doi":"10.1109/ms.2024.3363248","DOIUrl":null,"url":null,"abstract":"How are requirements managed in agile software development? While practitioners are widely adopting industry-pushed innovations to cope with requirements in agile settings, research at this intersection is still too limited. Based on first-hand experience, we review some core aspects of this industry-academia gap (e.g., user stories vs. requirements, management tools like JIRA, requirements-as-code) and we conclude with a call for action for intensifying joint research between academia and the software industry.","PeriodicalId":55018,"journal":{"name":"IEEE Software","volume":"28 1","pages":""},"PeriodicalIF":3.3000,"publicationDate":"2024-04-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Where Requirements and Agility Meet: No-Man’s-Land or a Land of Opportunity?\",\"authors\":\"Fabiano Dalpiaz, Jan-Philipp Steghöfer\",\"doi\":\"10.1109/ms.2024.3363248\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"How are requirements managed in agile software development? While practitioners are widely adopting industry-pushed innovations to cope with requirements in agile settings, research at this intersection is still too limited. Based on first-hand experience, we review some core aspects of this industry-academia gap (e.g., user stories vs. requirements, management tools like JIRA, requirements-as-code) and we conclude with a call for action for intensifying joint research between academia and the software industry.\",\"PeriodicalId\":55018,\"journal\":{\"name\":\"IEEE Software\",\"volume\":\"28 1\",\"pages\":\"\"},\"PeriodicalIF\":3.3000,\"publicationDate\":\"2024-04-05\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"IEEE Software\",\"FirstCategoryId\":\"94\",\"ListUrlMain\":\"https://doi.org/10.1109/ms.2024.3363248\",\"RegionNum\":4,\"RegionCategory\":\"计算机科学\",\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"Q2\",\"JCRName\":\"COMPUTER SCIENCE, SOFTWARE ENGINEERING\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"IEEE Software","FirstCategoryId":"94","ListUrlMain":"https://doi.org/10.1109/ms.2024.3363248","RegionNum":4,"RegionCategory":"计算机科学","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"Q2","JCRName":"COMPUTER SCIENCE, SOFTWARE ENGINEERING","Score":null,"Total":0}

引用次数: 0

摘要

如何在敏捷软件开发中管理需求？尽管实践者们正在广泛采用业界推动的创新技术来应对敏捷环境下的需求，但对这一交叉领域的研究仍然非常有限。基于第一手经验，我们回顾了产学差距的一些核心方面（如用户故事与需求、JIRA 等管理工具、需求即代码），最后呼吁加强学术界与软件行业之间的联合研究。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

查看原文

微信好友朋友圈 QQ好友复制链接

本刊更多论文

Where Requirements and Agility Meet: No-Man’s-Land or a Land of Opportunity?

How are requirements managed in agile software development? While practitioners are widely adopting industry-pushed innovations to cope with requirements in agile settings, research at this intersection is still too limited. Based on first-hand experience, we review some core aspects of this industry-academia gap (e.g., user stories vs. requirements, management tools like JIRA, requirements-as-code) and we conclude with a call for action for intensifying joint research between academia and the software industry.

求助全文

通过发布文献求助，成功后即可免费获取论文全文。去求助

来源期刊

IEEE Software 工程技术-计算机：软件工程

CiteScore

5.50

自引率

6.10%

发文量

182

审稿时长

6-12 weeks

期刊介绍： IEEE Software delivers reliable, useful, leading-edge software development information to keep engineers and managers abreast of rapid technology change. Its mission is to build the community of leading software practitioners. The authority on translating software theory into practice, this magazine positions itself between pure research and pure practice, transferring ideas, methods, and experiences among researchers and engineers. Peerreviewed articles and columns by seasoned practitioners illuminate all aspects of the industry, including process improvement, project management, development tools, software maintenance, Web applications and opportunities, testing, and usability. The magazine''s readers specify, design, document, test, maintain, purchase, engineer, sell, teach, research, and manage the production of software or systems that include software. IEEE Software welcomes articles describing how software is developed in specific companies, laboratories, and university environments as well as articles describing new tools, current trends, and past projects'' limitations and failures as well as successes. Sample topics include geographically distributed development; software architectures; program and system debugging and testing; the education of software professionals; requirements, design, development, testing, and management methodologies; performance measurement and evaluation; standards; program and system reliability, security, and verification; programming environments; languages and language-related issues; Web-based development; usability; and software-related social and legal issues.