Abstract
A Methodology for the Integration of Service Repositories
Highlights
The service development lifecycle usually follows stages in a pipeline that may include exploration, planning, design, production, and management, where a service catalogue or repository is a recognized enabler of standardization, more effective service discovery and composition source of knowledge, better management of stakeholder expectations, cost transparency, and pricing mechanisms (Fisher 2008)
In the service development lifecycle it is worthwhile to distinguish between a conceptual phase, whose goal is the modeling of abstract services, and an implementation phase, that produces concrete services
We focus on the area of conceptual database design, seen in comparison to abstract service design; the similarities among the two areas stem from the fact that conceptual schemas and repositories of abstract services have similar structures, since is- a and part-of relationships are the pillars of models adopted for both of them
Summary
The service development lifecycle usually follows stages in a pipeline that may include exploration, planning, design, production, and management, where a service catalogue or repository is a recognized enabler of standardization, more effective service discovery and composition source of knowledge, better management of stakeholder expectations, cost transparency, and pricing mechanisms (Fisher 2008). Lago 2011), consider two levels of services, that, according to the approach followed, are called respectively business/technological, or abstract/concrete. It is consolidating a view in the service life cycle that. The proliferation of abstract service repositories, in the same organization or in cooperating organizations, will require methodologies for the integration of service repositories. Further we analyze the possible correspondences and conflicts among service properties, and we propose an integration methodology guided by the discovery of correspondences between services in different repositories. SMART project, highlighting similarities between service design and database design, while in Section 4 we provide the model defined in SMART to represent services and service repositories.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
