HEAL DSpace

Root cause analysis and diagnosis in SOA and cloud environments

DSpace/Manakin Repository

Show simple item record

dc.contributor.author Mankovski, S en
dc.contributor.author Kontogiannis, K en
dc.contributor.author Muller, H en
dc.contributor.author Wong, K en
dc.date.accessioned 2014-03-01T02:52:06Z
dc.date.available 2014-03-01T02:52:06Z
dc.date.issued 2009 en
dc.identifier.uri https://dspace.lib.ntua.gr/xmlui/handle/123456789/35846
dc.subject.other Business needs en
dc.subject.other Business Process en
dc.subject.other Business solutions en
dc.subject.other Enterprise applications en
dc.subject.other Enterprise business process en
dc.subject.other Implementation changes en
dc.subject.other Integration of services en
dc.subject.other Integration technologies en
dc.subject.other IT applications en
dc.subject.other Root cause analysis en
dc.subject.other Service interfaces en
dc.subject.other Software component en
dc.subject.other Information services en
dc.subject.other Information technology en
dc.subject.other Service oriented architecture (SOA) en
dc.title Root cause analysis and diagnosis in SOA and cloud environments en
heal.type conferenceItem en
heal.identifier.primary 10.1145/1723028.1723092 en
heal.identifier.secondary http://dx.doi.org/10.1145/1723028.1723092 en
heal.publicationDate 2009 en
heal.abstract Modern information technology (IT) is comprised of a complex mix of infrastructure components provisioning enterprise applications performing tasks in various enterprise business processes. Over the years these components were integrated into overall business processes using various integration technologies and architectures. In recent years, service-oriented architecture (SOA) approaches have emerged which separate the service implementations from its interfaces. Stable service interfaces allow for the integration of services at a higher level and orchestration of services into ever more complex business solutions. However, the implementation of a service can change at any time, and this is considered a good thing because of its flexibility. Sometimes a services implementation is comprised of a single software component, but in an enterprise setting, a service might be composed of multiple IT applications, systems, networks and databases interconnected in elaborate ways. Since business needs change, components of a service implementation change and evolve to meet changing business needs. © Copyright held by author. en
heal.journalName Proceedings of the 2009 Conference of the Center for Advanced Studies on Collaborative Research, CASCON '09 en
dc.identifier.doi 10.1145/1723028.1723092 en
dc.identifier.spage 335 en
dc.identifier.epage 336 en


Files in this item

Files Size Format View

There are no files associated with this item.

This item appears in the following Collection(s)

Show simple item record