DocumentCode
1873832
Title
Intermediate SOA maintenance and evolution
Author
Chapin, Ned
Author_Institution
InfoSci Inc., Menlo Park, CA, USA
fYear
2011
fDate
26-26 Sept. 2011
Firstpage
1
Lastpage
7
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.
Keywords
organisational aspects; service-oriented architecture; software maintenance; software tools; SOA; legacy software; organizations; service-oriented architecture; software evolution; software maintenance; software tools; Information systems; Maintenance engineering; Organizations; Personnel; Semiconductor optical amplifiers; Service oriented architecture; Cloud computing; IOA; SOA technology; SoaML; legacy software; service orientation; software evolution; software maintenance;
fLanguage
English
Publisher
ieee
Conference_Titel
Maintenance and Evolution of Service-Oriented and Cloud-Based Systems (MESOCA), 2011 International Workshop on the
Conference_Location
Williamsburg, VA
Print_ISBN
978-1-4577-0645-5
Electronic_ISBN
978-1-4577-0646-2
Type
conf
DOI
10.1109/MESOCA.2011.6049038
Filename
6049038
Link To Document