E-Business Architecture

E-Business Architecture
E-business Architectures leverage web technologies to
implement mission critical E-Business applications.
These architectures use clients that have small footprints
to access services provided by resource managers and
accessed across a strong and reliable network. These
clients can be browsers running on PCs or network
devices, PDAs, Cell Phones and other Pervasive
Computing devices.
 E-Business Architecture
Thin Client E-Business architectures that support these solutions are based upon web
technologies across a network
Application Service
Client Resource Manager
Application Service
Resource Manager
Application Service

Characteristics Characteristics Characteristics

Thin - Small Control Logical Unit of Work Reuse Legacy Code
Footprint Reusable Components Platform Specific Code
Portable Protocol Independent Protocol Independent
OS Independent
Protocol Responsibilities Responsibilities
Independent
Responsibilities  Perform Business Logic (Calculations,  Store and Retrieve data from
 Present data to users Edits, Business Rules) data sources.
 Validate Input data  Access data from Resource Managers  Perform sorting, filtering and
 Verify data types (valid dates,  Perform Distributed Transactions selective data retrieval
valid numeric and alpha data etc.)  Encapsulate Business constructs  Eliminate any platform
 Use appropriate Application dependent issues such as data
Services to access and update types, field misuse etc.
data
Presentation Application Services Resource Managers
E-Business Architecture
Definition

The E-Business architecture is more

than just a collection of technologies
and products. It consists of several
architectural models and is much
like a city plan in that it defines
blueprint that will meet current and
future needs of a diverse user
population and will adapt to
changing business and technology
requirements.
E-Business Architecture
Key Influencers

The key elements that help influence an

E-Business architecture include:
 The overall E-Business Strategy of the
organization
 Business Drivers such as Time to Market,
One-to-one customer service etc.
 The Current IT Environment
 IT Vision, Objectives and Strategies
 Organizational Constraints – Staff,
Budgets, Risk Tolerance etc.
 New and Emerging Technologies
 E-Business Architecture Models
What is the
Developing a new Business
brand or extending a
functionality that
strong brand to the needs to be
online environment Functional provided by the
Architecture solution?
Creating the look
and feel of the e- What types of content,
Digital how is it maintained,

Content Management
business
Branding published and

Data Architecture
Solution Information
& distributed
Architecture
UI
What information Where is the
Design
needs to be made information stored,
available, to how is it accessed and
whom, and how? how is data integrity
maintained?
What are the
How do you
security
manage Security Architecture and privacy
and administer the
Requirements for the
infrastructure Operational/Systems Mgt. Architecture infrastructure
and the application
and application
 Digital Branding
The key components of the Digital Branding effort include:

 Developing an online Brand

 Extending a strong brand across multiple channels –

paper, print, media and the Internet

 Developing guidelines for representing the brand

across the web
 User Interface & Usability
• The key components of the
Usability:
 Site navigation
 Experience with screen
interaction
 Impact of personalization
 Human interface factors (color,
size, font, etc.)
 Use case modeling impact
 Information Architecture
 The key questions that are addressed by an information
architecture are:
 What data are made available to users?
 Who are the users who can accesses the information?
 What roles do these users play when they access the
information?
 What do they need the information for? – Understand the
context
 How do they access the information? – Browser, PDA, GUI,
VRU etc.
 The Information Architecture drives how data and information
are stored and accessed within the e-business solution
 Content Management
The key questions that need to be addressed
by the content management architecture are:
Content
Management  Identify types of content

 Who owns and manages the content?

Content Content
Creation Publishing  Expiration date for the content

 The process and the workflows needed to manage

the content
Content
Distribution  How is the content developed and published

 How is the content distributed

 Functional Architecture
The Functional Architecture should focus on describing the
function of the IT system and is primarily concerned with:
the structure and modularity of the software components
(both application and technical)
interactions between components, including protocols
the interfaces provided by components, and their usage
dynamic behavior, expressed as collaborations between
components
 Data Architecture
The Data Architecture includes a thorough analysis of:

 what data needs will be accessed ?

 why is the data accessed ?
 where is the data located ?
 what is the currency of the data ?
 how will we maintain data integrity ?
 what is the data relationship between data
displayed & stored?
 how can we provide round the clock availability
when the backend systems and databases are not
available on a 24x7 basis?
 Security Architecture
Virus detection Firewalls,
and protection, Intrusion Boundary proxies and
spam filters Immunity Server other services
etc. to protect the
application

Encryption
Services needed
to ensure the
Policy Information integrity of the
PKI
Manager Integrity information

Public Key Services required

Infrastructure to allow the
Services information to
Non
Authentication hold up in a court
repudiation
of law

Services to validate Privacy Establish adequate privacy

you are who you requirements and guidelines
say you are for the application
Systems Management Architecture
The Systems Management Aspect should cover:

 all the nodes within the architecture

 manageable from local and remote locations
 based on standards and extensible to support new
technologies
 include support for systems administration, systems
management, and software configuration management
 Systems Management Architecture

The Operational Aspect’s focus is on describing the operation

of the IT system and is primarily concerned with:
representing network organization (hardware platforms,
locations, topology, etc.)
what runs where - where software and data are ‘placed’
on this network
satisfying the Non-Functional requirements of the
system (performance, availability, security, etc.)
the management and operation of the IT system
(capacity planning, software distribution, backup and
recovery)