Common use of Conclusions and Future Work Clause in Contracts

Conclusions and Future Work. ‌ Since existing specifications for creating agreements for services, such as WS–Agreements, WSLA, and SLA*, were developed to capture the technical aspects of Web services, we developed Linked USDL Agreement, an extension to the Linked USDL service description fam- ily, to capture business aspects, compensations and time constraints, among others. The new specification is to be used to establish and share agreements between customers and providers who seek to automatically perform service trading over the Web. The evaluation of Linked USDL Agreement was two- fold. On the one hand, we evaluated its capabilities to model services such as EC2 made available by Amazon AWS. On the other hand, we showed how our proposal covers the SLA lifecycle compared to existing ones, focusing on actually used features in common SLAs. Furthermore, we discuss how the information captured by our model can be automatically used by tools to perform validity checking, for instance. Future work requires to build a proof-of-concept pro- totype to illustrate how a service marketplace could au- tomatically provision services to consumers with regards to their requirements and preferences [16] coping with heterogeneity issues, as well as to establish contracting using Linked USDL Agreement, and to automatically detect service level objectives’ violations, which would be reported to customers and trigger compensation actions.

Conclusions and Future Work. ‌ Since existing specifications for creating agreements for services, such as WS–Agreements, WSLA, and SLA*, were developed to capture the technical aspects of Web services, we developed Linked USDL Agreement, an extension to the Linked USDL service description fam- ily, to capture business aspects, compensations and time constraints, among others. The new specification is to be used to establish and share agreements between customers and providers who seek to automatically perform service trading over the Web. The evaluation of Linked USDL Agreement was two- fold. On the one hand, we evaluated its capabilities to model services such as EC2 made available by Amazon AWS. On the other hand, we showed how our proposal covers the SLA lifecycle compared to existing ones, focusing on actually used features in common SLAs. Furthermore, we discuss how the information captured by our model can be automatically used by tools to perform validity checking, for instance. Future work requires to build a proof-of-concept pro- totype to illustrate how a service marketplace could au- tomatically provision services to consumers with regards to their requirements and preferences [168] coping with heterogeneity issues, as well as to establish contracting using Linked USDL Agreement, and to automatically detect service level objectives’ violations, which would be reported to customers and trigger compensation actions.

Conclusions and Future Work. ‌ Since existing specifications specifications for creating agreements for services, such as WS–Agreements, WSLA, and SLA*, were developed to capture the technical aspects of Web services, we developed Linked USDL Agreement, an extension to the Linked USDL service description fam- ily, to capture business aspects, compensations and time constraints, among others. The new specification specification is to be used to establish and share agreements between customers and providers who seek to automatically perform service trading over the Web. The evaluation of Linked USDL Agreement was two- fold. On the one hand, we evaluated its capabilities to model services such as EC2 made available by Amazon AWS. On the other hand, we showed how our proposal covers the SLA lifecycle compared to existing ones, focusing on actually used features in common SLAs. Furthermore, we discuss how the information captured by our model can be automatically used by tools to perform validity checking, for instance. Future work requires to build a proof-of-concept pro- totype to illustrate how a service marketplace could au- tomatically provision services to consumers with regards to their requirements and preferences [16] coping with heterogeneity issues, as well as to establish contracting using Linked USDL Agreement, and to automatically detect service level objectives’ violations, which would be reported to customers and trigger compensation actions.

Conclusions and Future Work. ‌ Since existing specifications for creating agreements for services, such as WS–Agreements, WSLA, and SLA*, were developed to capture the technical aspects of Web services, we developed Linked USDL Agreement, an extension to the Linked USDL service description fam- ily, to capture business aspects, compensations and time constraints, among others. The new specification is to be used to establish and share agreements between customers and providers who seek to automatically perform service trading over the Web. The evaluation of Linked USDL Agreement was two- fold. On the one hand, we evaluated its capabilities to model services such as EC2 made available by Amazon AWS. On the other hand, we showed how our proposal covers the SLA lifecycle compared to existing ones, focusing on actually used features in common SLAs. Furthermore, we discuss how the information captured by our model can be automatically used by tools to perform validity checking, for instance. Future work requires to build a proof-of-concept pro- totype to illustrate how a service marketplace could au- tomatically provision services to consumers with regards to their requirements and preferences [16] coping with heterogeneity issues, as well as to establish contracting using Linked USDL Agreement, and to automatically detect service level objectives’ violations, which would be reported to customers and trigger compensation actions.