The Challenges of E-Government Architecture
The Challenges of E-Government Architecture
E-Government is about the government not wasting citizens' time. Architecting for e-government means dealing with distributed systems, complex interactions between departments, and legal and organizational challenges.
Join the DZone community and get the full member experience.
Join For FreeYour feedback matters—tell Capital One DevExchange what you would do with their Money Movement API.
After working for a year on the matter, I did a presentation at a small conference about the options for an architecture of e-government solutions. A 40-minute talk could not cover everything, and it is presented in the context of Bulgaria (hence 2 graphs with Cyrillic script in the slides), so I hope it’s useful anyway.
It follows a previous post of mine that proposes an architecture, which I’ve expanded here.
The main points are:
- all data registers must be integrated somehow;
- the integration should preferably not rely on a centralized ESB-like system;
- privacy must be addressed by strict access control and audit logs, including access for citizens to data about who read their data and why, including notifications;
- the technical challenge is only 20%, the rest is legal and organizational.
Despite being government-related, it’s actually an interesting technical task that not many have solved properly.
Here’s your opportunity to influence experimental APIs. Tell Capital One DevExchange what you think of their new Money Movement API.
Like This Article? Read More From DZone
Published at DZone with permission of Bozhidar Bozhanov , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}