2012
DOI: 10.21236/ada585496
|View full text |Cite
|
Sign up to set email alerts
|

Best Practices for Artifact Versioning in Service-Oriented Systems

Abstract: This material has been approved for public release and unlimited distribution except as restricted below.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2014
2014
2024
2024

Publication Types

Select...
4
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(1 citation statement)
references
References 16 publications
(39 reference statements)
0
1
0
Order By: Relevance
“…However, it tends to be much more difficult than other types of systems because of the distributed nature of SOA development, including lack of centralised control, the ripple effect of change, and opacity stemmed from the separation of the service interface from service implementation [15]. No breakthrough has been made so far to address these issues and most of current efforts have largely focused on shrewd adaptation to existing SCM systems and workarounds [16].…”
Section: Introductionmentioning
confidence: 99%
“…However, it tends to be much more difficult than other types of systems because of the distributed nature of SOA development, including lack of centralised control, the ripple effect of change, and opacity stemmed from the separation of the service interface from service implementation [15]. No breakthrough has been made so far to address these issues and most of current efforts have largely focused on shrewd adaptation to existing SCM systems and workarounds [16].…”
Section: Introductionmentioning
confidence: 99%