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.

someone to be non-eligible for the service. When this indicator is<br />

equal to zero then everyone is eligible for invoking the service.<br />

3.3.3 Maximum/Minimum/Average Number of<br />

Questions<br />

These indicators provide the maximum, minimum and average<br />

number of questions that are asked to the citizen during the<br />

dialogue. The indicators count only questions that result in an<br />

eligible end node and, thus, show the number of questions<br />

required for the successful completion of the dialogue. An<br />

increased number of questions indicate more complex services.<br />

3.3.4 Maximum/Minimum/Average Total Cost<br />

These indicators provide the maximum, minimum and average<br />

cost of the service. Obviously, they count only the cost coming<br />

from dialogue paths that result in an eligible end node. The<br />

service provider can use these indicators to measure the range of<br />

the service’s cost for the citizen. As a result, they can also<br />

measure the expected income from the execution of the public<br />

service provided details on the number of citizens that will<br />

consume the service are also known.<br />

3.3.5 Maximum/Minimum/Average Total Subsidy<br />

These indicators provide the maximum, minimum and average<br />

expected citizen’s benefit after the execution of the public service.<br />

It can be used by public authorities to compute the range of the<br />

total subsidy as well as its average provided details on the number<br />

of beneficiaries are known.<br />

3.3.6 Maximum/Minimum/Average Number of Input<br />

Documents<br />

These indicators provide the maximum, minimum, and average<br />

number of documents that different citizens’ categories need to<br />

provide for invoking the service. They also count the number(s) of<br />

documents coming from not eligible dialogues, if applicable.<br />

These indicators could be used to examine the level of<br />

bureaucracy as an increased number of required input documents<br />

usually indicates an increased level of red tape.<br />

3.3.7 Indicators for Set of Services<br />

Apart from the indicators that refer to each specific service<br />

diagram, we also propose a number of indicators that apply to a<br />

set of services diagrams. These indicators are helpful to public<br />

administrations responsible for the design and management of<br />

many public services. The indicators include:<br />

o Involvement of Other Public Authorities. This dictates the<br />

number of other public authorities that are involved in<br />

providing a particular public service. It is measured through<br />

the required input documents of each service and the public<br />

authorities that are issuing them.<br />

o Number of Services per public Authority. This dictates the<br />

number of services provided by each public authority. This<br />

information can be useful for planning, including human<br />

resources management.<br />

o Document’s Importance. A large number of input<br />

documents are actually produced by public authorities. This<br />

indicator depicts the number of services using a particular<br />

document. This is useful in planning e.g. to estimate how<br />

many services will be affected if an input document is<br />

abolished or replaced.<br />

137<br />

It should be noted that as all service descriptions can be stored in<br />

a database, additional information may be extracted depending on<br />

specific needs.<br />

4. PSP IP PLATFORM<br />

In order to demonstrate the use of the proposed notation we<br />

developed a prototype platform presented in this section.<br />

4.1 Architecture and Functionality<br />

The architecture of the developed prototype platform is shown in<br />

fig. 7 using UML deployment diagram while its main<br />

functionality is shown in fig. 8 using UML use case diagram.<br />

Figure 7. Platform architecture<br />

As presented in the use case diagram there are three main actors:<br />

domain expert, content manager and citizen/business (visitor or<br />

end-user). It is worth explaining the content manager. This role is<br />

responsible for central activities including managing all public<br />

documents, describing public services, deciding which PSP IP<br />

diagrams to launch in the Dialogue website etc.<br />

Figure 8. Platform main functionality<br />

4.2 Main Usage Scenario<br />

There are many different usage scenarios for this platform. Here<br />

we present one such usage scenario.<br />

Step 1. Input Documents are Described<br />

The Content manager is using the Service Admin Tool in order to<br />

create descriptions of input documents that will be needed when<br />

modeling PSP IP (fig. 9). Ideally, there should be one such

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

Saved successfully!

Ooh no, something went wrong!