************************************************************ Go through the objectives, slightly expanding on them, as described in the Technical Annex
LIFE EVENTS REVISITED: CONCEPTUALIZATION AND REPRESENTATION USING GENERIC WORKFLOWS Efthimios Tambouris and Konstantinos Tarabanis CERTH/ITI & University of Macedonia Wojciech Izdebski and Mariusz Momotko Rodan Systems SA
For analysis purposes we suggest that a life-event is a profile-based (personalised) set of actions, including at least one public service, which, when executed in its appropriate workflow, fulfils a need of a citizen arising from a new life situation
“ In order to drive a car, you should have access to a car and a valid driving license. Since you already own a car but not a driving license, you will need to invoke the public service “issuing a driving license”. This service is provided by prefectures and since you live in Thessaloniki then the appropriate service provider is the prefecture of Thessaloniki. Since you are facing vision problems we will need to wear eyeglasses or contact lenses and obtain the relevant doctor certificate in order to invoke this service. You should note that driving with glasses will be mandatory once you obtain your driving license. Finally, you should take into account that the steps to be performed are as following: first you resolve your vision problem with a doctor and second you invoke the “issuing a driving license” public service at the prefecture of Thessaloniki”
Life-events is a term widely used, which however lack a widely-accepted definition
As a result, life-events are difficult to analyse and model and thus their potential in portal design is yet unexploited
A reason for this is the absence of a clear model for public service
A life-event can be considered as a profile-based (personalised) set of actions, including at least one public service, which, when executed in its appropriate workflow, fulfils a need of a citizen arising from a new life situation
Workflow technology seems suitable for the implementation of LE
The OneStopGov project aims to specify, develop and evaluate a life-event oriented , integrated , interoperable platform for online one-stop government. This platform will be accompanied by a coherent framework for realising and exploiting online one-stop government at all levels.
The guiding vision, challenge, innovation and unique selling proposition for the OneStopGov platform involve:
the inherent support of life-events (LE) ;
the active , citizen-centric approach ; and
the definition and use of generic models (e.g. generic workflows, generic reference models).
Comparison with other approaches Yes. Integration follows pre-defined forms (according to LE reference models) A complete set of LE reference models is specified and implemented using generic workflow technologies. LE instances are created dynamically. Active. A dialogue is performed with citizens to identify their needs and circumstances OneStopGov Yes. Life-events are dynamically created (on-the-fly) as compositions of back-office services. Services are created as compositions of Web Services. They can be also dynamically created based on their semantics and citizens circumstances. Dynamic. Info is dynamically fetched (e.g. using metadata) Dynamic binding Yes. Each service is implemented as a static workflow of components that may run in different PAs Services are hard-coded and often consist of components. Passive. Static info on LE is provided Hard-coded No. No services. Citizens are re-directed to other portals. Passive. Static Info on LE is provided Loosely-coupled No. Services are hard-coded at the portal. Passive. LE are lists of topics Monolithic back-office integration Services Portal (info provision)