100% found this document useful (1 vote)
316 views27 pages

Enterprise Information Architecture Component Model - Chapter 5

This document describes various components that make up an enterprise IT architecture. It outlines components for delivery channels, infrastructure security, presentation services, service registry/repository, collaboration, connectivity, directory/security services, operational applications, mashups, metadata management, master data management, data management, content management, analytics applications, and enterprise information integration. Each component is described in terms of its purpose and key capabilities.

Uploaded by

Nat Utomo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
316 views27 pages

Enterprise Information Architecture Component Model - Chapter 5

This document describes various components that make up an enterprise IT architecture. It outlines components for delivery channels, infrastructure security, presentation services, service registry/repository, collaboration, connectivity, directory/security services, operational applications, mashups, metadata management, master data management, data management, content management, analytics applications, and enterprise information integration. Each component is described in terms of its purpose and key capabilities.

Uploaded by

Nat Utomo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 27

Chapter 5

 Component Description :
A component represents a logically grouped set of specific
capabilities to deliver particular software functionality.
The roles, responsibilities, relationships and interactions to
other components, required collaboration that enables the
implementation of specified deployment and customer use case
scenarios
 Delivery channel and external data provider
 Infrastructure Security Component
 Presentation Services
 Service Registry and Repository
 Collaboration services
 Connectivity and Interoperability Services
 Directory and Security Services
 Operational Applications
 Mashup hub
 Metadata Management Component
 Master Data Management Component
 Data Management Component
 Enterprise Content Management Component
 Analytical Application Component
 Enterprise Information Integration Component
 IT Service & Compliance Management Services.
 Delivery Channel and External Data Provider
Differentiate between two different categories

 Internal – Access to internal user or system.


◦ Mobile apps
◦ Enterprise Portal
◦ Client UI
◦ Productivity/Collaboration UI
◦ Enterprise search UI
◦ Mashup

 External – Access to external user or system


◦ External data provider
◦ Web
◦ Cross-enterprise Application
 Infrastructure Security Component
The Infrastructure Security Component represents a De-
Militarized Zone (DMZ). A DMZ provides secure and authorized
access to trusted and controlled network areas.
 Presentation Security
 Business Performance Presentation Services
◦ Business Performance Presentation Services are the underlying set
of presentation services that enables and visualizes the
comprehensive corporate business insight
◦ Monitoring and managing the attainment of business performance
and achievement of business goal.

 Search and Query Presentation Services


◦ Focusing on the intranet search, limited to the information
resource within the enterprise.
◦ files on network file systems and in content management systems,
relational and XML data in databases, emails in email archives,
and information contained in blogs and wikis
◦ SQL enables the retrieval, insertion, updating, and deletion of data
 Presentation Security

 Embedded Analytics
◦ The capability to provide analytical insight for a specific step in a
business process to improve day to day decision.
◦ Embedded Analytics Component has the capability to detect the
context of the step performed by the operational application and
apply appropriate enrichments for analytical data
◦ Eg : Application processing a customer complaint must decide
which action to take.
 Service Registry and Repository (SRR)
 IT Gov  SOA (Service Oriented Arch) Gov  SRR
 SRR enable business process vitality and agility, service reuse,
connectivity and the alignment of business and IT.
◦ What services are available?
◦ Where are these services located?
◦ How are the services used and how do they interact?
◦ Who is using these services and why?
 Business Process Service

 Provide the key capabilities for the modelling, deployment,


orchestration and execution of business process.
 The core of this component is a workflow engine that drives
the business processes.
 The Business Process Execution Language (BPEL) is a standard
that is often supported by an implementation of this
component.
 Collaboration Service

 Enable employee of an enterprise or across enterprises to


efficiently collaborate with each other
◦ Email
◦ Portal
◦ E-meeting
◦ E-learning
◦ Shared Docs Portal
 Connectivity and Interoperability Service

 Represents the backbone used by all IT System in the


enterprise to communicate with each other.
◦ The ESB (Enterprise Service Bus) is a communication
backbone between applications and transport requests
represented by messages (typically, with XML-based
formats today) between service consumers and service
providers
◦ Message and Web Services Gateway, This component uses
key capabilities such as mediation and security of the
Interoperability and interconnectivity Component to
implement tasks such as routing and management services
 Directory and Security Services
 Maintains authentication credential for user and security
policies, including rules and access control lists.
 Operational Applications
Multiple design point addressed by operational application.
designed to make the processing of the daily transactional
workload efficient and to guarantee the required integrity of the
transactional data

◦ High Level Description


 An operational system is used to process the daily
transactional load of an organization and is frequently
called a transactional system.
 Concurrency in terms of addressing a high number of
users who are concurrently using the system.
 Performance regarding transaction response time or end-
user response time.
 Operational Applications
Multiple design point addressed by operational application.
designed to make the processing of the daily transactional
workload efficient and to guarantee the required integrity of the
transactional data

◦ High Level Description


 Throughput regarding the transaction rate, meaning the
number of transactions per time interval.
 Scalability to enable growth to be addressed in terms of
allowing more users to interface with the operational
system, for example.
 Continuous availability by implementing high availability
and continuous operations to address unplanned and
planned outages.
 Security, delivering data protection, authentication, and
authorization either with built in capabilities or by
interfacing with external providers.
 Operational Applications
Multiple design point addressed by operational application.
designed to make the processing of the daily transactional
workload efficient and to guarantee the required integrity of the
transactional data

◦ Interfaces
 Using the Connectivity and Interoperability Services (such
as the ESB), Operational Systems do interface with other
systems
 Mashup Hub
A mashup is considered a lightweight web application created by
combining information from a set of heterogeneous sources or
other capabilities from various existing sources to deliver new
insight
◦ High Level Description
Responsible for delivering the info 2.0 promise using
mashup and web syndication function.
◦ Service Description
 Mashup Builder services
 Mashup Catalog services
 Mashup Server runtime
 Virtual member services
 Feed Services
 Proxy Services
 Information Interface Services
 Metadata Management Component and Metadata
Service
Provide a common set of functionalities and core services for
enabling open communication, exchange and consumption of
metadata between system that use different data format,
including storage and optimization models, data models,
directories, EII functions— and core data management
functions.
 Master Data Management Component
Single, authoritative, enterprise wide source of trusted master
data, and maintains it at the high level of quality.
• Collaborative authoring
• Author by different people, different roles, but still a master data
• Operational
◦ This method is characterized by stateless services for many concurrent
applications and users in a high-performance environment
• Analytical
• Provide clean and consistent master data to BI systems
• Analytics on the master data itself  a report of how many new customers
were created in a week or month with this component
• Identity Analitcs
 Data Management Component and Data Services
Provide a common set of functionality and core services to
access and manage data stored in a heterogeneous set of
repositories

Enable an open communication and exchange of information


between system that use different data formats, data access
methods and programming models
 Data Management Component and Data Services
 Enterprise Content Management Component and
Content Service
Delivers all the relevant capabilities for the management of
unstructured data.

• MAM
• DMS
• CRM
 Enterprise Content Management Component and
Content Service
 Analytical Applications Component and Analytical
Services
Comprised of BI (business intelligence) and PM (performance
management) Services, enable department, organization and
large enterprise to leverage information to acquire a better
understanding of their commercial context and to better
understand and optimize business performance.
 Analytical Applications Component and Analytical
Services
 Enterprise Information Integration Component
and Ell Services
EII services are delivered through a set of tools and products
that help enterprises derive more value from the complex,
heterogeneous information spread across their systems. These
services enable users to quickly understand, transform, and
integrate large amounts of information stored within their
enterprises
Help to ensure high-quality information over time, delivering it
on demand to any requesting person or application, other
system components, or in the context of a defined business
process.
 Enterprise Information Integration Component
and Ell Services
 IT Services & Compliance Management Services
Delivering the non-functional requirements for the EIA
Reference Architecture
• Compliance Management Services – SLA

• Availability Management Services – MTBF, MTTR, MTTF

• Retention Management Services – Autodelete

• Security Management Services – NetSec

• Capacity Management Services – Capacity Planning

• Quality of Services Management – QoS : Functionality,


maintainability, security, operational

You might also like