Life events Revisited: Conceptualization and Representation Using Generic Workflows
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Life events Revisited: Conceptualization and Representation Using Generic Workflows

on

  • 274 views

Paper presented at EGOV conference (within DEXA cluster), Krakow, 4-7 September 2006.

Paper presented at EGOV conference (within DEXA cluster), Krakow, 4-7 September 2006.

Statistics

Views

Total Views
274
Views on SlideShare
274
Embed Views
0

Actions

Likes
0
Downloads
4
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • ************************************************************ Go through the objectives, slightly expanding on them, as described in the Technical Annex

Life events Revisited: Conceptualization and Representation Using Generic Workflows Presentation Transcript

  • 1. 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
  • 2. Preamble
    • One of the aims of the IST OneStopGov project is to propose a number of reference models for life-events
    • For that purpose, it was essential that a definition of life-events was adapted and used
    • Our research however identified that in the literature the exact meaning of life-events is not clear
    • We therefore revisited life-events in an attempt to clarify the concept
  • 3. Table of Contents
    • Rationale: One-Stop Government and life-events
    • Defining life-events
    • Analysis of life-events
    • Modeling of life-events
    • Representation of life-events using workflows
    • Conclusions and Future Work
    • The OneStopGov project
  • 4. Rationale
    • Online one-stop government enables 24 hour, single point access to public services that are integrated around citizens needs (usually life-events - LE ).
    • Currently however, online one-stop government projects do not care about citizens needs and do not provide integrated services from different back-offices.
  • 5. Table of Contents
    • Rationale: One-Stop Government and life-events
    • Defining life-events
    • Analysis of life-events
    • Modeling of life-events
    • Representation of life-events using workflows
    • Conclusions and Future Work
    • The OneStopGov project
  • 6. LE definition
    • The concept seems intuitive …
    • … however no widely accepted definition exists
    • In fact definitions are sometimes significantly different
      • life events “ describe situations of human beings where public services may be required ” (IST eGov project)
      • “ the term life event refers to the government services needed at specific stages in life ” (European Commission The Role of eGovernment for Europe's Future, COM(2003) 567, Sept 2003)
  • 7. Table of Contents
    • Rationale: One-Stop Government and life-events
    • Defining life-events
    • Analysis of life-events
    • Modeling of life-events
    • Representation of life-events using workflows
    • Conclusions and Future Work
    • The OneStopGov project
  • 8. Citizens domain, PA domain and LE
    • LE are related to citizens lives and Public Services (PSs) but this relationship is not clear
    • The analysis is complicated as there is no widely accepted model of a PS
  • 9. Some basics
    • LE should be around citizens: “obtaining a driving license” in not a LE, it is a public service; “driving a car” is a LE
    • In the context of eGovernment, the Public Administration only cares for those life-events where public services are invoked
  • 10. Four Considerations
    • Citizens profile (e.g. “driving a car” may not trigger any PS if the user owns a driving license)
    • Some LE do not involve public services (e.g. “driving a car” in the case the user own a driving license)
    • Many public services have versions (e.g. “issuing a driving license” in the case of user with vision problems)
    • LE may have a conditional dimension (e.g. “getting thirsty” in the case of water shortage)
  • 11. Table of Contents
    • Rationale: One-Stop Government and life-events
    • Defining life-events
    • Analysis of life-events
    • Modeling of life-events
    • Representation of life-events using workflows
    • Conclusions and Future Work
    • The OneStopGov project
  • 12. Modeling LE
    • 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
  • 13. LE Conceptual model
    • Relationship between citizen’s needs, citizen’s profile, life events, and public services
  • 14. Example
    • “ I want to drive a car” is a citizen’s need.
    • We assume that the relevant citizen’s profile includes the following information:
      • I have a car,
      • I do not have a driving license,
      • I live in Thessaloniki, Greece
      • I am short-sighted.
  • 15. What is expected? - 1
    • “ 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”
  • 16. What is expected? - 2
  • 17. Table of Contents
    • Rationale: One-Stop Government and life-events
    • Defining life-events
    • Analysis of life-events
    • Modeling of life-events
    • Representation of life-events using workflows
    • Conclusions and Future Work
    • The OneStopGov project
  • 18. Generic Workflows
    • In a workflow , services are represented as activities ordered by transitions
    • If we agree that a life event is a composed service, represented as a process and implemented as a workflow then life‑event reference models can be represented using generic workflows
  • 19. Definition Phase
    • A workflow definition may be generic in two aspects.
      • Firstly, it covers all possible scenarios for a given life event reference model.
      • Secondly, it refers to the classes of services rather than concrete services
    • Benefits
      • Formal verification of correctness for all possible scenarios
      • Validation of legal rules and regulations compliance
      • Optimisation and redesign
  • 20. Execution Phase
    • before execution - generic workflow adjustment that takes place just after the user decides to really carry out his / her life event
    • during execution – the selection of the service (instances) to be invoked within individual activities should be done by evaluation selection rules
    • during execution - monitoring will be assured: if deadlines are violated then the citizen and appropriate PA representatives should be informed
  • 21. Table of Contents
    • Rationale: One-Stop Government and life-events
    • Defining life-events
    • Analysis of life-events
    • Modeling of life-events
    • Representation of life-events using workflows
    • Conclusions and Future Work
    • The OneStopGov project
  • 22. Conclusions
    • 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
    • More work is needed to model LE
  • 23. Table of Contents
    • Rationale: One-Stop Government and life-events
    • Defining life-events
    • Analysis of life-events
    • Modeling of life-events
    • Representation of life-events using workflows
    • Conclusions and Future Work
    • The OneStopGov project
  • 24. Project Fact Sheet
    • Project full title: A life-event oriented framework and platform for one-stop government
    • Project acronym: OneStopGov
    • Starting date: January 1st, 2006
    • Duration: 30 months
    • Web site : www.onestopgov-project.org
  • 25. OneStopGov Approach
    • 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).
  • 26. 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)
  • 27.
    • To specify the LE reference models that will enable modeling virtually any life-event.
    • To specify and develop the OneStopGov platform
    • To propose an all-inclusive framework for one-stop government
    • To evaluate and validate the results in four countries (Slovenia, Hungary, Romania and Poland)
    • To exploit and disseminate the project results
    Scientific and Technological Objectives
  • 28.
    • Thank you for your attention!!
    • Themis Tambouris
    • CERTH/ITI and University of Macedonia
    • [email_address]