Monday, 23 June 2008

Government architectures

Lots of effort is put in establishing government architectures. Interoperability frameworks are listing various technical standards and ICT governance is also put in place. People transform existing documents into different parts, like strategy, interoperability, and so on. Any good guidelines for IT architecture, including government architecture, should consider generic aspects like abstraction and decomposition, paradigms like SOA, and so on. Existing principles like 'multi-channeling' and 'no wrong door' are widely accepted by most governments. New technology to support these principles should be explored. Is it possible to create one virtual government (per country, for the EU, and global?)?

Besides changes in technology, other aspects need to be considered, since the environment is constantly changing. How to deal with Web x.* for instance. What does it mean for government behaviour? How to cope and integrate standards from the gaming environment for disclosing graphical information and interacting with citizens and companies? In this context, governments still consider graphical information as geographical information.

To be brief, we should set general principles for a government architecture and try to implement them in existing and new projects. Furthermore, we should consider new developments and integrate them in our approach. We have to keep an open mind. As IT architects, we should provide the means to government and business to do an possibly change their work with new means.

No comments: