中间SOA维护和发展

N. Chapin
{"title":"中间SOA维护和发展","authors":"N. Chapin","doi":"10.1109/MESOCA.2011.6049038","DOIUrl":null,"url":null,"abstract":"By the 2010–2011 time period, many organizations had started the paradigm transition to using service-oriented architecture (SOA), but few had competed that transition. In that time period, most organizations were intermediate somewhere between started and completed. While they were in that intermediate status and beginning to get some of the benefits of SOA use, they continued to have to maintain the legacy software that was still in use, as well as maintain the new SOA-using software. Each of the varieties of software also sometimes needed to be evolved to better meet the needs of the organization. The maintenance and evolution could be affected by the technologies, software tools, and governance that had been used, as well as by changes in them, and by new ones, such as SoaML and the Cloud. Avenues for additional research abounded.","PeriodicalId":305930,"journal":{"name":"2011 International Workshop on the Maintenance and Evolution of Service-Oriented and Cloud-Based Systems","volume":"17 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2011-10-20","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Intermediate SOA maintenance and evolution\",\"authors\":\"N. Chapin\",\"doi\":\"10.1109/MESOCA.2011.6049038\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"By the 2010–2011 time period, many organizations had started the paradigm transition to using service-oriented architecture (SOA), but few had competed that transition. In that time period, most organizations were intermediate somewhere between started and completed. While they were in that intermediate status and beginning to get some of the benefits of SOA use, they continued to have to maintain the legacy software that was still in use, as well as maintain the new SOA-using software. Each of the varieties of software also sometimes needed to be evolved to better meet the needs of the organization. The maintenance and evolution could be affected by the technologies, software tools, and governance that had been used, as well as by changes in them, and by new ones, such as SoaML and the Cloud. Avenues for additional research abounded.\",\"PeriodicalId\":305930,\"journal\":{\"name\":\"2011 International Workshop on the Maintenance and Evolution of Service-Oriented and Cloud-Based Systems\",\"volume\":\"17 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2011-10-20\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2011 International Workshop on the Maintenance and Evolution of Service-Oriented and Cloud-Based Systems\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/MESOCA.2011.6049038\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2011 International Workshop on the Maintenance and Evolution of Service-Oriented and Cloud-Based Systems","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/MESOCA.2011.6049038","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0

摘要

到2010-2011年期间,许多组织已经开始了向使用面向服务的体系结构(SOA)的范式转换,但很少有组织参与了这种转换。在那段时间里,大多数组织处于开始和完成之间。当他们处于中间状态并开始获得SOA使用的一些好处时,他们继续必须维护仍在使用的遗留软件,以及维护新的使用SOA的软件。软件的每一个变种有时也需要进化以更好地满足组织的需要。维护和发展可能受到已经使用的技术、软件工具和治理的影响,也可能受到这些技术、软件工具和治理中的变更以及新技术(如SoaML和Cloud)的影响。进一步研究的途径比比皆是。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
Intermediate SOA maintenance and evolution
By the 2010–2011 time period, many organizations had started the paradigm transition to using service-oriented architecture (SOA), but few had competed that transition. In that time period, most organizations were intermediate somewhere between started and completed. While they were in that intermediate status and beginning to get some of the benefits of SOA use, they continued to have to maintain the legacy software that was still in use, as well as maintain the new SOA-using software. Each of the varieties of software also sometimes needed to be evolved to better meet the needs of the organization. The maintenance and evolution could be affected by the technologies, software tools, and governance that had been used, as well as by changes in them, and by new ones, such as SoaML and the Cloud. Avenues for additional research abounded.
求助全文
通过发布文献求助,成功后即可免费获取论文全文。 去求助
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:604180095
Book学术官方微信