SIA

Enterprise Architecture

General Characteristics

Distributed systems - It should be possible to add servers, and sites without any major changes to the basic design of the architecture or applications. It should accommodate diverse computing platforms with proper use of interoperability standards and middleware.

Scalability: it should be possible to accommodate an increased number of users, increased number of transactions, or expand the scope of functionality.

Component-based applications - Components are sharable, replaceable building blocks. This is essential to be able to adapt quickly to the changing business needs and technology opportunities.

EJB - Enterprise Java Beans

CCM - CORBA Component Model

Microsoft’s COM+

Event-driven process - When a problem requiring management attention occurs in production, the appropriate manager should be notified immediately. This requires a change in the design of systems and the way they interoperate. Businesses are driven by events: an order is placed, a shipment is received, a machine fails, a person is hired.

Loose coupling - Allows for independently developed applications to interact without concern about time, internal information format, and technology. Highly coherent focused solutions linked through the transfer of transactions in an asynchronous mode of communication. Messages queues are used for comm.

Decision Support Systems

Enterprise integration architecture must support decision makers with:

Current status

Exceptions

Historical records

Relevant knowledge

Business Exceptions - Events requiring human intervention, shifts in key business indicators, violations of policies, or deviations in variables that exceed defined limits should be treated as business exceptions. Automated business processes and rules should determine immediately who should take action and with what priority.

Business Process Automation - Workflow management posts a “work list” to a person or application. Delays can be monitored, action item can be brought to attention based on a priority

Integration Infrastructure Model

Enterprise COTS Application

Distributed Component Based Systems

Decision Support System

Main Control/ Trans Application

Workflow Process Model - Business processes drive the operation of a business.

Workflow: process definition, process system, activity, requester, personal work list, resource assignment facility, process manager, process interoperability.

Reference Architecture Model - represents the collective set of knowledge relating to the e-Government architecture, technology standards, interoperability framework, and governance, and performance management.

Central architecture: Describes the e-Government central platform architecture and specifications for the individual building blocks

Business Model - describes the core and support activities an organization performs.

Process Model - describes processes within and between organizations.

Workflow model - describes process and workflow on a detailed level.

Service catalogue - provides a high level overview of business services and e-services.

Application architecture - describes application components that support business services and e-services.

Application design - describes implementation of applications.

Information model - describes the core concepts related to a specific area or organizational unit.

Logical data model - provides a description of information elements and their relations

Physical data model - provides a detailed and technology-specific definition of data elements and their relations.

Technology platform model - gives a high-level view of the technology platform, including all platform components.

Technical architecture model - describes the components and interactions between the components in the technology platform.

Infrastructure model - details the technical components of the solution.

Boundaryless Information Flow - achieved through global interoperability in a secure, reliable and timely manner.

Infrastructural - Organization of the interconnecting and underlying facilities

Structural - System growth is limited by the “strength” or scalability of its structure

Architectural - Differently architected technologies often don’t “fit” with each other

Semantic - Different ways of representing the same thing