Show simple item record

dc.contributor.authorNoran, Ovidiuen_US
dc.contributor.authorBernus, Peteren_US
dc.contributor.editorR. Meersman, Z. Tari, and P. Herreroen_US
dc.date.accessioned2017-05-03T12:21:40Z
dc.date.available2017-05-03T12:21:40Z
dc.date.issued2008en_US
dc.date.modified2010-08-30T07:03:46Z
dc.identifier.issn03029743en_US
dc.identifier.doi10.1007/978-3-540-88875-8_51en_AU
dc.identifier.urihttp://hdl.handle.net/10072/24661
dc.description.abstractCurrently, Service Oriented Architecture (SOA) is still in its infancy, with no common agreement on its definition or the types and meaning of the artefacts involved in its creation and maintenance. Despite this situation, SOA is sometimes promoted as a parallel initiative, a competitor and perhaps even a successor of Enterprise Architecture (EA). In this paper, several typical SOA artefacts are mapped onto a reference framework commonly used in EA. The results show that the EA framework can express and structure SOA artefacts with minimal or no customisation and can help reason about and establish unambiguous meanings for SOA artefacts across the business. Further on, it is shown how an EA-specific approach can help scope the areas of the business that require attention as a result of the changes brought about by an SOA vision and design principles. This suggests that integrating the SOA effort into the ongoing EA initiative is a best practice that will greatly benefit all business units of the host organisation.en_US
dc.description.peerreviewedYesen_US
dc.description.publicationstatusYesen_AU
dc.languageEnglishen_US
dc.language.isoen_AU
dc.publisherSpringer-Verlagen_US
dc.publisher.placeBerlin Heidelbergen_US
dc.relation.ispartofstudentpublicationNen_AU
dc.relation.ispartofpagefrom304en_US
dc.relation.ispartofpageto312en_US
dc.relation.ispartofjournalLecture Notes in Computer Scienceen_US
dc.relation.ispartofvolume5333en_US
dc.rights.retentionYen_AU
dc.subject.fieldofresearchcode289999en_US
dc.subject.fieldofresearchcode350299en_US
dc.titleService Oriented Architecture vs. Enterprise Architecture: Competition or Synergy?en_US
dc.typeJournal articleen_US
dc.type.descriptionC1 - Peer Reviewed (HERDC)en_US
dc.type.codeC - Journal Articlesen_US
gro.date.issued2008
gro.hasfulltextNo Full Text


Files in this item

FilesSizeFormatView

There are no files associated with this item.

This item appears in the following Collection(s)

  • Journal articles
    Contains articles published by Griffith authors in scholarly journals.

Show simple item record