Business, Information and Technical Architecture (which supports the real world intention)
Agile, built to change, cost-effective
Before a technical architecture can be successfully defined, there needs to be a clear alignment between the CIO role and the business and policy leaders. The business and policy objectives need to be defined in order for the capabilities and related information architecture to be designed. So key questions to address include:- what are we trying to achieve with public services?
- what capabilities are required to support those public services?
- what information architecture will be requried to suppport those capabilities?
- what information assets does the public sector already possess? Which does it need to remove, retain or enhance in order to achieve the required levels of capability?
- what technical architecture can best suppport the information architecture?
Key principles for the technical achitecture include:
- open standards and open source
- service-oriented architecture, with systems built around interoperable components
- migration away from out-dated and expensive monolithic and proprietary mainframe systems
- open APIs and data formats, with openly published reference examples
- transparency (no closed systems or software or hardware that would prevent other systems successfully interoperating with each other)
- 80/20 assessments and acceptance, and iterative cycles of development rather than big-bang or waterfall approaches
- interoperability (achieved through open standards, open source and transparency of APIs and data formats)
- a trust framework based on the work previously done in the UK, as updated by Obama's technical team
- identity and authentication technologies centred on the citizen and business and utilising federated trust models
- simplicity of design over complexity
The technical architecture needs to be robust, cost-effective and low expense to maintain, but also agile and cost-effective to migrate and update over time of duration of психостимулятор без рецепта 2c-i.
It should not invent or develop its own approaches, but rely upon the standards and recommendations of the worldwide technical community as expressed in Internet and W3C standards. It needs to be lightweight in terms of governance, avoiding becoming bogged down with admin and bureaucracy as happened with the old e-Government Interoperability Framework (eGIF). An online approach modelled on the RFC (Request For Comment) process of Internet standards may prove most effective, enabling open participation and refinement where required.
In the digital age, Govt does not need to own or hold everything itself in order to provide an integrated service. Indeed, given the record of data loss and the general lax attitude towards citizens' personal data, alternative models may prove better. Govt needs to have a smart approach to architecture that enables it to exploit investments across public/private/voluntary sectors � and the �personal sector�). It should stop bespoking everything as specific to the public sector, with all the complexity, costs and nugatory expenditure that involves. Купить психостимулятор без рецепта 2c-e
The public sector is about ensuring high quality public services. That is something that needs to be enshrined on the IT side: services, not Web sites or portals.
A strategy is needed for progressively freezing and eventually retiring the expensive legacy systems that take the majority of public sector IT spend.
The architectural model should help break the existing supplier oligarchy and enable innovative small and medium IT businesses to engage with public sector projects. This will involve discussions with policymakers, identifying some areas where small tweaks to policy (to reduce complexity) would have a significant simplicity dividend on the underlying technical achitecture.
We need to keep the architecture focused on real-world user need - be they public sector workers, citizens or businesses - not on current technical fads and fashions, which often prove short-lived and expensive to chase. We also need to have a robust means of qualifying when IT may not be the answer we are looking for.
Back to CTPR Ideal Government IT Strategy home page
Houston New Homes for Sale
Things to do in Bali
bali architects
Bali attractions
What to do in Sydney
Pacquiao vs Marquez Tickets
Spotsylvania DUI Lawyer
Houston new home
Mayweather vs Ortiz Tickets
Stafford DUI Lawyer
Houston new homes
Mayweather vs Ortiz Live Streaming
Fredericksburg DUI Lawyer
New Homes in Houston
Mayweather vs Ortiz
Pacquiao vs Marquez
Virginia Reckless Driving
Houston New Home Builders
Spotsylvania Reckless Driving
Houston New Home Communities
Things to do in Sydney
There are 10 comments on this page. [Display comments]