Cockpit d1.3 interviews telcos

WP1: Governance Model for Next-Generation Public Service Delivery

D1.3: COCKPIT Toolkit Use Cases

WP4: Implementation of COCKPIT Toolkit

D4.1.0: Conceptual proof of concept

ICT 2009 FP7-248222

2

Applying RUP to COCKPIT

3

RUP artefacts employed within COCKPIT

4

QFD Approach

5

COCKPIT Toolkit Actors

uc Actors

Citizen

Role: End-User

Description: The “Citizen” is the actual user that will benefit from the service.

She/he is involved in the design process as a “tester” that evaluates the

designed service and expresses her/his opinion through specified

communication channels (e.g. forums, blogs, deliberation platform etc.).

uc Actors

Decision Maker

Role: Service Provider

Description: The “Decision Maker” is the executive of the public body that will

provide the service to be designed. The aforementioned public body is the one

responsible (in-charge) for the provision of the service.

The “Decision Maker” will set the boundaries of the service, design it by

implementing the cockpit methodological approach and software tools and

evaluate the opinion of its target users.

uc Actors

Cockpit System

Administrator

Role: Support

Description: The “System Administrator” is the person responsible for

performing support tasks, such as managing the Cockpit toolkit users. She / he

is not involved in the service model design process. The respective use cases

of the “System Administrator” are of medium importance so, if the consortium

decides not to implement them, the role can be discarded.

6

COCKPIT Toolkit Use Cases

Two Main Phases:

• Modelling Phase

• Deliberation Phase

7


Two Main Phases:

• Modelling Phase

• Deliberation Phase

8


Level of Importance:

• High: This Use Case is of high priority for the system and needs to be fulfilled

in the project phase.

• Medium: The implementation of Use Cases with a level of medium priority

will be decided in the development phase and according to the learning

experience the consortium will receive from the implementation of the high

level functionality.

• Low: This Use Case refers to the functionality that will need to be fulfilled

once the COCKPIT system comes to the commercialization phase. Therefore it

will not be covered by the existing project but needs to be taken into account in

the marketing and exploitation phases.

9

Cockpit Overview

Start Transformation

Define Service Concept

Invoke Opinion Mining

Decide the Stakeholders

Gather Stakeholders’ Requirements

Policy and Law Retrieval

Service Modeling

Define & Design

Alternatives

Cost & Value Estimation

Generate Simulation

Model

Simulation Visualization

Citizen’s Deliberation

Citizen Happy?

Co-Valuation

Model ready to

implement

The Cockpit Methodology

10

Defining Service Concept








Service Modeling

Define & Design

Alternatives


Generate Simulation

Model



Citizen Happy?

Co-Valuation

Model ready to

implement


11

Defining Service Concept – Screenshots

12

Defining Service Concept – Screenshots (cont.)

13


14


Invoke Opinion Mining Tool

Invoke Policy and Law Tool

15

•Government-to-Citizens•Government-to-Businesses•Government-to-Institutions(Organizations)•Government-to-Government

•license•certificate•registration•request•objection•payment•return•other (please specify)


16


17


•Full - Fully automated•Semi - Some steps are done manually•None - No support at all

18

Invoking Opinion Mining Tool








Service Modeling

Define & Design

Alternatives


Generate Simulation

Model



Citizen Happy?

Co-Valuation

Model ready to

implement


19

Invoking Opinion Mining Tool - Screenshots

20









Service Modeling

Define & Design

Alternatives


Generate Simulation

Model



Citizen Happy?

Co-Valuation

Model ready to

implement


21

Decide the Stakeholders - Screenshots

22

Gather Stakeholder’s Requirements








Service Modeling

Define & Design

Alternatives


Generate Simulation

Model



Citizen Happy?

Co-Valuation

Model ready to

implement


23

Gather Stakeholder’s Requirements. –

Screenshots

24

Gather Stakeholder’s Requirements. –

Screenshots (cont.)

25









Service Modeling

Define & Design

Alternatives


Generate Simulation

Model



Citizen Happy?

Co-Valuation

Model ready to

implement


26

Policy and Law Retrieval - Screenshots

27

Service Modeling








Service Modeling

Define & Design

Alternatives


Generate Simulation

Model



Citizen Happy?

Co-Valuation

Model ready to

implement

Service Modeling

28

Service Modeling – Screenshots

29

Service Modeling – Screenshots (cont.)

30









Service Modeling

Define & Design

Alternatives


Generate Simulation

Model



Citizen Happy?

Co-Valuation

Model ready to

implement


31

Cost & Value Estimations - Screenshots

32

Cost & Value Estimations - Screenshots(cont.)

33

Cost & Value Estimations - Screenshots(cont.)

34









Service Modeling

Define & Design

Alternatives


Generate Simulation

Model



Citizen Happy?

Co-Valuation

Model ready to

implement



35

Citizen’s Deliberation - Screenshots

Documents

Cockpit d1.3 interviews telcos