E-Government: services, needs and user satisfaction

Document type: Miscellaneous
Full text:
Author(s): Kristian Gustafsson, Markus Fiedler
Title: E-Government: services, needs and user satisfaction
Translated title: E-förvaltning: tjänster, behoven och användarens
Type of publication: Technical report
Year: 2004
Organization: Blekinge Institute of Technology
Department: School of Engineering - Dept. of Telecommunication Systems (Sektionen för teknik – avd. för telekommunikationssystem)
School of Engineering S- 372 25 Ronneby
+46 455 38 50 00
http://www.tek.bth.se/
Authors e-mail: markus.fiedler@bth.se
Language: English
Abstract: Within the e-government process, needs are identified and people try to come up with ideas for the public sector that will increase the effectiveness as well as lead to cost savings. Consequently, many new electronic services are being developed. As a result, Quality of Service (QoS) becomes an even more critical issue in the domain of electronic services. This paper starts by a general discussion of e-government and its services in general. Thereafter it explains different QoS factors that have been identified within the field of electronic services. The identification has been carried out by studying several researchers’ work and by experience from e-government projects. The result shows that service design, security aspects, network performance issues, as well as the users’ perspective, such as user requirements, are all factors of the QoS model. A new electronic service that does not take these factors into consideration might fail and therefore be rejected by its intended users.
Summary in Swedish: Rapporten diskuterar tjänstekvaliténs betydelse för tjänster tillhörande e-förvaltning/24-timmars myndighet etc. e-förvaltning, 24-timmars myndighet, tjänstekvalitet, tjänstedesign, säkerhet, nätverksprestanda, användareperspektiv, krav
Subject: Telecommunications\General
Keywords: e-government, needs, electronic services, Quality of Service, service design, security, network performance, user’s perspective, user requirements
Edit