For example, in his article entitled "The Promise of Digital Government", Garson looks at the very nature of e-government and concludes that:. The second section looks at the virtual face of government. Two of the papers in this section look at web portals, which are portrayed as the interface between citizen and government within the context of e-government.
One of the papers, by Franzel and Coursey, argues that attention with respect to government web portals to date has focused on design issues such as usability. In this paper, they focus on management issues such as commercialization and centralization. After defining a management-oriented perspective to the study of government web portals, the authors use a case study approach and examine the experiences of five states to advance this perspective.
Their review of these government web portals goes beyond a descriptive analysis and examines them from the perspective of six key issues that they feel deserve attention: client definition, political use, centralization, commercialism, outsourcing and performance measurement. The authors do an effective job of identifying and evaluating these sites against these very pertinent principles.
The third section of the book, entitled "Issues in Digital Governance", contains very concrete information on e-government and will be of particular interest to public servants and others who are tasked with implementing e-government and all that it entails.
This section contains papers that look at privacy issues, e-procurement, and e-commerce, among other topics. The paper on e-procurement by Krysiak, Tucker, Spitzer and Holland, concludes with a series of steps that the authors recommend to e-government practitioners:. They then go on to offer six mistakes to avoid in any e-procurement endeavour. Although theoretically sound—the authors obviously have an excellent grasp of project management principles as they apply to information technology projects—the real strength of these principles lies in the fact that they are the product of experience.
Having given us a glimpse of the current state of e-government, the fourth section of the book forces the reader to take a step back and looks at preparation for digital government. This section looks at very pertinent areas such as how to produce useable data sources out of disparate information and how the bureaucracy and academics who study bureaucracy must prepare in order to be able to function in an e-government environment.
Finally, the book looks at the future of digital government by examining issues such as the digital divide and citizen participation. This book does an excellent job of identifying and investigating a variety of phenomena that surround e-government. It will be useful to both academics and practitioners.
The latter will find the case studies and concrete examples of particular interest, which is a particular strength of this book. A notable absence in this volume is a section on security and e-government. Several papers do address this issue in one form or another, but this is an area that certainly deserves its own section. One cannot work in government informatics without being cognizant of security issues.
PLAY 9 Deploy in a flexible hosting environment Our services should be deployed on flexible infrastructure, where resources can be provisioned in real-time to meet spikes in traffic and user demand. Checklist Resources are provisioned on demand Resources scale based on real-time user demand Resources are provisioned through an API Resources are available in multiple regions We only pay for resources we use Static assets are served through a content delivery network Application is hosted on commodity hardware Key Questions Where is your service hosted?
What hardware does your service use to run?
What is the demand or usage pattern for your service? What happens to your service when it experiences a surge in traffic or load? How much capacity is available in your hosting environment? How long does it take you to provision a new resource, like an application server?
How have you designed your service to scale based on demand? How are you paying for your hosting infrastructure e. Is your service hosted in multiple regions, availability zones, or data centers?
For citizens and service users, this means less time filling out government forms and fewer delays in accessing service. Building on the existing solution and maintaining an enterprise approach, TBS and SSC are developing a renewed cyber-authentication service. Consideration should be given to agile development, regardless of contracting vehicle or approach. And yet, there are major concerns. This includes determining how to scale private cloud services, as demand may rise and fall over time. It is an iterative process that must be repeated regularly. This includes ensuring that the digital government vision is incorporated from conception and throughout project and product development.
In the event of a catastrophic disaster to a datacenter, how long will it take to have the service operational? What would be the impact of a prolonged downtime window? What data redundancy do you have built into the system, and what would be the impact of a catastrophic data loss? How often do you need to contact a person from your hosting provider to get resources or to fix an issue? PLAY 10 Automate testing and deployments Today, developers write automated scripts that can verify thousands of scenarios in minutes and then deploy updated code into production environments multiple times a day.
Checklist Create automated tests that verify all user-facing functionality Create unit and integration tests to verify modules and components Run tests automatically as part of the build process Perform deployments automatically with deployment scripts, continuous delivery services, or similar techniques Conduct load and performance tests at regular intervals, including before public launch Key Questions What percentage of the code base is covered by automated tests?
How long does it take to build, test, and deploy a typical bug fix? How long does it take to build, test, and deploy a new feature into production? How frequently are builds created? What test tools are used?
Which deployment automation or continuous integration tools are used? What is the estimated maximum number of concurrent users who will want to use the system? How many simultaneous users could the system handle, according to the most recent capacity test? How does the service perform when you exceed the expected target usage volume?
Does it degrade gracefully or catastrophically? What is your scaling strategy when demand increases suddenly? PLAY 11 Manage security and privacy through reusable processes Our digital services have to protect sensitive information and keep systems secure. How is the user notified of this collection?
Does it collect more information than necessary? How does a user access, correct, delete, or remove personal information? Will any of the personal information stored in the system be shared with other services, people, or partners? How and how often is the service tested for security vulnerabilities? How can someone from the public report a security issue? PLAY 12 Use data to drive decisions At every stage of a project, we should measure how well our service is working for our users.
Digital Government: Principles and Best Practices. Alexei Pavlichev (North Carolina State University, USA) and G. David Garson (North Carolina State University. Digital Government: Principles and Best Practices [Alexei Pavlichev, G. David Garson] on sorkeypokostnorth.gq *FREE* shipping on qualifying offers. E-government has.
Checklist Monitor system-level resource utilization in real time Monitor system performance in real-time e. How have these metrics performed over the life of the service? Which system monitoring tools are in place? What is the targeted average response time for your service? What percent of requests take more than 1 second, 2 seconds, 4 seconds, and 8 seconds? What is the average response time and percentile breakdown percent of requests taking more than 1s, 2s, 4s, and 8s for the top 10 transactions?
What is the percentage of transactions started vs. Excluding scheduled maintenance? How does your team receive automated alerts when incidents occur? How does your team respond to incidents? What is your post-mortem process? Which tools are in place to measure user behavior?
How do you measure customer satisfaction? Everything we build should be as inclusive, legible and readable as possible.
it.uteguxek.tk When a new digital service is ready to be launched, GDS works with the department or agency behind it to create a starting point for the service. This is the point where a user moves from finding out information on …. As a performance analyst on GOV.
UK, my job is to assess how well the site is performing, and track the effects of changes we put in place. Sometimes people think this mostly involves monitoring trends.
That's important, but the interesting ….