Embed Size (px)
Citation preview
Enterprise Enterprise ArchitectureArchitecture
Information Policy CouncilApr 19, 2001
Why Enterprise Architecture?
Electronic government is fundamentally changing the way citizens interact with the government, both as consumers of government services and stakeholders in the affairs of state
Design Goals
Facilitate change– The primary design goal for information
systems must be to enable rapid change in business processes and the applications and technical infrastructure that enable them.
Provide better interoperability of agency systems
Deploy advanced electronic government services
Enterprise Technical Architecture
A logically consistent set of principles, standards, and models that:– Are derived from business requirements– Guide the engineering of an organization’s
information systems and technical infrastructure across various domains
Components of Technical Architecture
Conceptual Architecture - the top-level set of principles and standards that guide the domain architectures
Domain Architectures - Logical groupings of related technologies– e.g. application, network, data, middleware,
groupware, security, accessibility
Business Drivers I
Appropriate government information and services will be accessible regardless of location, time, method of access and group (e.g. language, culture, age and ability)
Access to information and services will be authenticated to the degree required by specific information and services. Information will be protected to the level required both internally and externally.
Provide coherent and navigable access across multiple points of interaction for government information and services (I.e., “no wrong door”) spanning departments and other levels of government.
Business Drivers II
Government information and services will quickly respond to the client’s changing expectations
Government will reduce the total cost of ownership of IT investments though the elimination of duplicate infrastructures, support services, and leveraging economies of scale.
The government will increase attractiveness for business investment to build stronger local economies.
Minnesota Version
Start with existing Architecture Advisory Group and Architecture Working Group
Use shortcut process to display tangible progress
Use an existing template to develop a draft with small team from the Working Group
Get go-ahead from Advisory Group Develop the conceptual and domain
architectures with parallel teams.
Document Structure
Topic ChapterConceptual Architecture Chapter 1
Group I: Functional Domains
Data
Information
Document Management
Chapter 2
Middleware Chapter 3
Application Chapter 4
Presentation
Accessibility
Chapter 5
Group II: Infrastructure Domains
Platform Chapter 6
Network Chapter 7
Groupware
Directory Services
Chapter 8
Domain Structure
Category Obsolete Current Emerging
Purpose Scope Principles Best Practices Implementation Guidelines
Standards
Cover Design
ENTERPRISE
ARCHITECTURE
FOR
DUMMIESCIOEDITION
A Reference forThe Rest of Us!
21Hundred
Sold
Other Considerations
Operational focus of agency IT efforts Impact on smaller agencies Existing efforts, e.g.:
– Common security infrastructure (PKI)– Northstar portal upgrades– Electronic Government Services
collaborative– Recordkeeping Metadata study
Adoption and Implementation
Willingness of agencies to adhere to the architecture in future development:– Compelling perceived advantage– Substantial natural consequence– OT leadership– IPC sponsorship
Schedule
Drafting Committee - mid March Working Group approval - Mid April Advisory Group approval - late May Domain architecture definitions - June-
September Architectural Reference, version 1 - October
