15.11.2012 Views

icegov2012 proceedings

icegov2012 proceedings

icegov2012 proceedings

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

o Information. Represents any information the visitor should<br />

know e.g. “the execution of the service should be completed<br />

within ten working days”.<br />

o Value. Represents an amount the visitor should pay to<br />

invoke the service or receive after the service’s completion<br />

(e.g. in case of a social benefit service). There are three cases<br />

for a Value object:<br />

-­‐ Registration. Represents the amount that the visitor<br />

should pay as a lump sum (e.g. a 20 € fee).<br />

-­‐ Annual Subscription. Represents the amount that<br />

the visitor should pay annually (e.g. an annual<br />

subscription to a chamber of commerce).<br />

-­‐ Subsidy. Represents the amount that the visitor is<br />

entitled from the execution of a service (e.g.<br />

housing benefit).<br />

Value is a subcase of Information but we include it as<br />

separate object due to its particular importance to citizens<br />

and public authorities as well as its semantics (e.g. Values<br />

can be added).<br />

We call Question, Input Document, Information and Value<br />

internal nodes of the graph (diagram).<br />

Table 1. Notation for PSP IP Dialogue Diagrams<br />

Element and Description Symbol<br />

Start:<br />

� Portrays the beginning of the diagram.<br />

Question:<br />

� Is used to represent a question posed to<br />

citizens/businesses.<br />

Answer:<br />

� Is used to represent a possible answer to a<br />

question.<br />

Input Document:<br />

� Is used to represent a document required for<br />

invoking a public service.<br />

Information:<br />

� Is used to represent any additional information<br />

a citizen/business should know.<br />

Value:<br />

� Is used to represent any monetary amount (it is<br />

a special case of Information).<br />

Not Eligible:<br />

� Is used to stop all control flows (thus it<br />

represents an end node)<br />

� It suggests the citizen/business is not eligible<br />

for the service.<br />

Eligible:<br />

� Is used to stop all control flows (thus it<br />

represents an end node)<br />

� It suggests the citizen/business is eligible for<br />

the service.<br />

We should note that the arrow besides representing a Question is<br />

also used to link the Start node to the first Question (hence<br />

representing control flow without any question). We understand a<br />

136<br />

new symbol should have been introduced for that however for<br />

simplicity we decided to use the arrow.<br />

In developing PSP IP diagrams there are certain rules that need to<br />

be respected for the resulting diagram to be valid. These rules are<br />

derived from graph theory and the fact that the graph should be a<br />

directed acyclic one. The most important are presented in Table 2.<br />

Table 2. Rules of PSP IP Dialogue Diagrams<br />

1. There is only one Start node that contains only one<br />

outgoing arrow leading to the first Question.<br />

2. There are one or more End nodes. An End node has one<br />

or more incoming Arrows but no outgoing Arrow.<br />

3. All paths (representing potential dialogues) should end in<br />

an End node.<br />

4. An Arrow always connects two nodes which should be<br />

different.<br />

5. Arrows indicate the control flow of the dialogue.<br />

6. An Answer may lead to only one Question, Information,<br />

Input Document or End Node.<br />

7. Question nodes should have at least two outgoing Arrows.<br />

All other internal nodes should only have one outgoing<br />

Arrow.<br />

8. No node should be “orphan”, i.e. all nodes should have at<br />

least one incoming and one outgoing arrow (subject to<br />

other rules).<br />

9. The resulting graph should be acyclic, thus no cycling<br />

paths should exist.<br />

3.3 Public service indicators<br />

The current effort aims to facilitate, apart from citizens, public<br />

service providers in designing dialogues but also in managing PSP<br />

IP. For this purpose, we introduce a number of indicators. Using<br />

these indicators the domain expert who designs the diagram<br />

obtains interesting information on various aspects of the service.<br />

The indicators measure the behavior of the main objects (i.e.<br />

Question, Document, and Value) and the diagram in general. To<br />

derive these indicators, graph theory was reviewed in the context<br />

of public service provision according to the authors’ relevant<br />

experience. In the rest of this section, we present the proposed<br />

indicators.<br />

3.3.1 Number of Dialogues<br />

This indicator provides the number of different dialogues in a<br />

diagram, i.e. the number of unique paths in the graph. This is an<br />

indication of the service’s complexity, since an increased number<br />

of dialogues suggests an increased number of service’s versions.<br />

3.3.2 Number of Dialogues that Results in a not<br />

Eligible Node<br />

This indicator provides the number of different dialogues that<br />

result in a not eligible node i.e. in cases where the citizen does not<br />

meet the requirements for invoking the public service. This is an<br />

indicator of the number of preconditions that must be fulfilled for

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!