Implementations of service oriented architecture and agile software development: What works and what are the challenges?

2016 IEEE Tenth International Conference on Research Challenges in Information Science (RCIS) Pub Date : 2016-06-01 DOI:10.1109/RCIS.2016.7549345

M. Schramm, M. Daneva

{"title":"Implementations of service oriented architecture and agile software development: What works and what are the challenges?","authors":"M. Schramm, M. Daneva","doi":"10.1109/RCIS.2016.7549345","DOIUrl":null,"url":null,"abstract":"Today many organizations use service-oriented architecture and agile software development as their software paradigms. While both certainly have their advantages, in the fields of Empirical Software Engineering and Information Systems these have been treated in relative isolation and their impact on each other is not well understood. This paper performs a grounded theory research by empirically analyzing professional blog posts published in IBM's Developerworks platform, to find good practices and common pitfalls of using a service-oriented architecture and agile software development together. The perspective taken in this study is the one of service-oriented architecture practitioners involved in agile projects. We found that continuous integration, collaboration, governance and continuous improvement are good practices that result out of merging the two paradigms. We found that the challenges of the joint use of service-oriented architecture and agile lie in the engineering of non-functional requirements, compliance requirements as well as up-front architecture evaluation.","PeriodicalId":344289,"journal":{"name":"2016 IEEE Tenth International Conference on Research Challenges in Information Science (RCIS)","volume":"70 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2016-06-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2016 IEEE Tenth International Conference on Research Challenges in Information Science (RCIS)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/RCIS.2016.7549345","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 3

Abstract

Today many organizations use service-oriented architecture and agile software development as their software paradigms. While both certainly have their advantages, in the fields of Empirical Software Engineering and Information Systems these have been treated in relative isolation and their impact on each other is not well understood. This paper performs a grounded theory research by empirically analyzing professional blog posts published in IBM's Developerworks platform, to find good practices and common pitfalls of using a service-oriented architecture and agile software development together. The perspective taken in this study is the one of service-oriented architecture practitioners involved in agile projects. We found that continuous integration, collaboration, governance and continuous improvement are good practices that result out of merging the two paradigms. We found that the challenges of the joint use of service-oriented architecture and agile lie in the engineering of non-functional requirements, compliance requirements as well as up-front architecture evaluation.

查看原文

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

本刊更多论文

面向服务的体系结构和敏捷软件开发的实现:哪些是有效的，哪些是挑战?

今天，许多组织使用面向服务的体系结构和敏捷软件开发作为他们的软件范例。虽然两者都有各自的优势，但在经验软件工程和信息系统领域，它们被相对孤立地对待，彼此之间的影响也没有得到很好的理解。本文通过实证分析在IBM的Developerworks平台上发表的专业博客文章，进行了扎实的理论研究，以找到将面向服务的体系结构和敏捷软件开发结合使用的良好实践和常见缺陷。本研究采用的视角是敏捷项目中涉及的面向服务的体系结构实践者的视角。我们发现，持续集成、协作、治理和持续改进是合并这两种范例所产生的良好实践。我们发现，联合使用面向服务的体系结构和敏捷的挑战在于非功能需求的工程、遵从性需求以及预先的体系结构评估。

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

求助全文

约1分钟内获得全文去求助

来源期刊

2016 IEEE Tenth International Conference on Research Challenges in Information Science (RCIS)

自引率

0.00%

发文量