D.B6a Use Case Specification eGovernment – M17
In this document we describe the main requirements and a first architectural hypothesis for the application (eGovernment use case) of the SLA@SOI framework in the context of the Healthcare System of the Italian region of Trentino.
The use case focuses on the implementation of a system for the reservation of medical treatment services.
We plan to realize it in two main steps. In a first step we will analyse and reimplement a portion of the reservation process “as is” and manage its SLAs and related resources by SLA@SOI results. In a second step we will try to understand how extending the medical treatment reservation process with the integration of a mobility reservation service might affect SLAs and open new possibilities. In particular, while currently the mobility providers are statically chosen, we plan to explore the possibility to dynamically select mobility providers.
The present document concerns mainly with the first step of this plan and provide just an high level view of the mobility reservation process. Here we mainly describe SLAs at business level as these are the SLAs treated in the current situation. A specification of low level SLAs and more details on the integration of the mobility service reservation will be provided in future documents.
The main expected contribution of the SLA@SOI framework to this use case are the improvement of the monitoring capability and the optimisation of resource consumption.
With respect to other use cases considered in SLA@SOI, the eGovernment use case is very peculiar in that several activities involved in the business processes are human based. Actually the quality of the booking process mainly depends from the quality of these human based services, therefore we aim to use the SLA@SOI framework to manage such services.
This necessitates a generalization of the concepts of resource and infrastructure to make them applicable to both IT and human based services. Therefore the main technical requirement of this use case is that the SLA@SOI framework remains as open as possible regarding the kind of resources and QoS parameters to manage. Other important challenges concern the kind of constraints (i.e. guarantee terms) involved in e-Government use case. For example statistical constraints and constraints depending from the input data.
Section 3.4 give a formal specification of the e-Government demonstrator. The paragraph 3.4.3 gives a description of the more challenging requirements that the e-Government demonstrator imposes on the SLA@SOI framework. A complete list of all requirements is provided in paragraph 3.6. To complete the description of what it is expected from the SLA@SOI framework, paragraph 3.5 gives a first draft of the e-Government demonstrator architecture.
Due the complexity of the e-Government context we expect the comprehension of the requirements and also the specification of the architecture will change as long as the analysis of the business process and of the implemented SLA@SOI framework will advance.
