ASSESSING THE TECHNOLOGY LANDSCAPE

LEGACY SYSTEMS▪ Considering with lagacy system

▪ Current enterprise landscape

▪ Specific high priority problem/specific productivity improvement

▪ Paths to connect systems

▪ Fragmentation of system

▪ New system, latest technology

LEGACY SYSTEMS▪ As time goes on, system become out of date

1. Changes in technology

2. Changes in business operation.

▪ In large corporation, local units develop business solutions.

▪ Business data(different form, names and ways).

▪ Client server system.

▪ Information system.

▪ Internet and electronic commerce.

DATA WAREHOUSE▪ Why datawarehouse?

▪ Consistent information is more difficult to access

▪ Seldom retain the data for longer periods of time

▪ Tools to provide analysis on ad hoc basis

▪ ODS

▪ Data cleansing and transformation

▪ Reconciliation of data

▪ Accumulate data for years(historical)

▪ Storage requirements extremely large

DATA WAREHOUSE▪ Addition and retrieval, no updates

▪ Datamart (specific data, specific purpose)

▪ ODS will phased out

▪ Batch processing

▪ Key challenge

INTRODUCTION▪ EAI was an approach to integration of applications first developed in the

late 1990s.

▪ Pre-dated widespread use of JEE, XML and Web Services.

▪ EAI currently has become subsumed into Service Oriented Architecture software stacks

▪ However, the need for the underlying capabilities have not changed.

MIDDLEWARE▪ Interaction between applications across

heterogeneous platforms

▪ Solution to integrating set of servers and applications under a common service interface

▪ Basic infrastucture behind distributed information system

ENTERPRISE APPLICATION INTEGRATION▪ Extends middleware capabilities to cope with

application integration

▪ Uses application logic layers of different middleware systems as building blocks

InterBankNetworks

ClearingHouse

CentralBank

InformationProvider

CardProcessor

BankNetwork

Consumer

Commercial

CorporateOtherBank

Mu

lti-

Ch

ann

el

CustomerRelationshipManagement

Pay

men

t S

yste

ms Accounts

DepositsLoansMortgagesPaymentsCustomer .... Call

Centre

SelfService

Branch

MobileSalesforce

Direct Banking

Internet

ExternalSystems

CoreSystems

InformationWarehouse

DeliverySystems

Customers

Internet

DIVERSE SYSTEMS AND CHANNELS

Example of a banking environment

Purchased Application Package(s) – ERP etc.

New Web-based application(s)

Legacy Application System(s)

ProgramProgram

Program

ProgramProgram

Program

ProgramProgram

Program

IT REALITY – ISLANDS OF COMPUTING

Enterprise IT reflects the structure and history of each enterprise not the business processes required today Departments have their own IT systems Legacy systems are left in place and new systems built

separately.

TACTICAL APPROACH TO INTEGRATING THE BUSINESS

Each requirement is addressed with a point to point solution Typically consisting of a data transfer mechanism and a format

converter. Increasing levels of supplier/client integration points further

complicates the situation.

Enterprise integration requirement

Unrestricted sharing of data and business processes throughout the networked applications or data sources in an organization Extend to customers, suppliers and regulators

The Linking of Data, Business Processes, Applications to automate business processes While ensuring that there are consistent qualities of

service (security, reliability etc)

Reduce the on-going cost of maintenance and reduce the cost of rolling out new systems.

Enterprise integration requirement

Unrestricted sharing of data and business processes throughout the networked applications or data sources in an organization Extend to customers, suppliers and regulators

The Linking of Data, Business Processes, Applications to automate business processes While ensuring that there are consistent qualities of

service (security, reliability etc)

Reduce the on-going cost of maintenance and reduce the cost of rolling out new systems.

DIFFICULTIES▪ Different operating system

▪ Support for different interfaces and functionality

▪ Different data format

▪ Different security requirements

▪ Different infrastructure and interaction protocols

ELECTRONIC COMMERCE▪ Direct communication with end costomers

▪ Data exchange with business partners

▪ New business relations

▪ New marketplace, global

ELECTRONIC COMMERCE

▪ Promote product and services

▪ B2C

▪ Promotes sales and customer loyalty

▪ B2C, web server and supporting applications

▪ Direct communication makes the business more responsive

▪ B2B

▪ EDI

▪ Auction and Bid

WEB ENABLED APPLICATIONS▪ Web Access to applications

▪ Web browsers

▪ Access anywhere in the world

▪ PC(not a practical user device)

WEB ENABLED APPLICATIONS

EXTENSIBLE MARKUP LANGUAGE▪ free-form expression of data structures in a

universal character set

▪ refinement of the basic syntax of HTML

▪ Preferred medium for the exchange of data

▪ tagged data format

▪ elements(a descriptive tag and an associated value)

▪ described by a DTD or XML Schema document

EXTENSIBLE MARKUP LANGUAGEkey strengths of XML

1.It carries with it descriptive tags that provide meaning to the content

2.It facilitates transformation

3.XML is replacing Electronic Document Interchange (EDI).

EXTENSIBLE MARKUP LANGUAGE

▪ XML parser

▪ XML Stylesheet Language (XSL)

▪ Document Object Model (DOM)

▪ Compatible with HTTP

▪ preferred syntax in EAI environment

▪ Open Application Group (OAG), Documents standards

▪ preferred syntax for B2B exchanges

▪ incorporated in the Simple Object Access Protocol (SOAP)

WORKFLOW MANAGEMENT

▪ Workflow management systems/business process management systems

WORKFLOW MANAGEMENT

▪ Manages the execution of activities

▪ Activities

1. perform operations directly

2. invoke applications

3. delegate tasks to humans

▪ From batch processing to eventbased processing

▪ Formalize processes

▪ Enforce compliance

WORKFLOW MANAGEMENT

▪ Monitor performance

▪ Process improvements

▪ Coordinate distributed and concurrent activities.

▪ Interoperation of different workflow systems

▪ Object Management Group (OMG)

▪ Convergence of Workflow management and EAI technologies

▪ Affects the design and scope of applications

DISTRIBUTED OBJECTS▪ Development of systems with distributed components

▪ Objects: shared services or objects of a business application.

DISTRIBUTED OBJECTS

▪ Primary distributed object technologies:

• (CORBA) from the OMG

• (COM+) from Microsoft

• (EJB) from Sun Microsystems

DISTRIBUTED OBJECTS

CORBA offers three particular benefits:

1. It enables a robust, scalable solution.

2. It supports messaging between objects implemented in different languages.

3. It is the product of an industry consortium and enables interoperability between products from different vendors.

DISTRIBUTED OBJECTS

▪ COM+:

1. Its products and operating systems

2. de facto reference

▪ EJB:

1. Specifications aligned to CORBA

2. Multiple vendors

COMPONENTS▪ Object technology; reusable components.

▪ Reuse: individual applications or development teams

▪ A Short Historical Perspective

▪ Component Interface and Connections

▪ Performing Services Transparently

A SHORT HISTORICAL PERSPECTIVE

▪ Programming languages, can be seen from either

▪ The run-time point of view or,

▪ The design and reuse perspective

COMPONENT INTERFACE AND CONNECTIONS

▪ ADLs primarily address the issues related to the early phases of software engineering:

▪ Design

▪ Analysis

▪ They identify a number of concepts, such as:

▪ Architecture, configurations, connectors, bindings, properties, hierarchical models, style, static analysis and behavior.

COMPONENT INTERACTIONS

Iteractions withtraditional software entities

Interactions withother

components

Interactions withother

components

Interactions withcomponent infrastructure

Components

Traditional software entities

Component Infrastructure

MAJORS STEPS IN CBD LIFECYCLE Aspect Phase Actor

Interface Definition Designer

Assembly Assembly Architect

Implementation Implementation Developer

Lifecycle Packaging, Deployment

Administrator

Framework, run-time support

Execution End User

ARCHITECTURAL DESCRIPTION LANGUAGE

▪ Components and Ports

▪ Connectors and Roles

▪ Systems and Attachments

▪ Representations and Bindings

▪ Properties, Constraints, Types and Styles

COMPONENTS AND PORTS

▪ Components

▪ Represent the computational elements and data stores of a system.

▪ Ports

▪ Are the points of interaction between a component and its environment.

ComponentPort

CONNECTORS AND ROLES

▪ Connectors

▪ Represent interactions between components such as method calls or an SQL connection between a client and a database server.

▪ The interface of a connector is defined as a set of roles

Connector

Role

SYSTEMS AND ATTACHMENTS

▪ The structure of a system is specified by a set of components, a set of connectors, and a set of attachments.

▪ Attachment

▪ Links a component port to a connector role.

Attachement

REPRESENTATIONS AND BINDINGS

Connector

Component

PortRole

AttachementBinding

JAVA BEAN COMPONENT MODEL

▪ Key Features

▪ Interface of a Component

▪ Implementation of a Component

▪ Components Assembly

▪ Packaging and Deployment

KEY FEATURES▪ Bean Box

▪ "A Java Bean is a reusable software component that can be manipulated visually in a builder tool”.

▪ The Java Bean was designed for the construction of graphical user interface (GUI).

▪ Explicitly tailored to interact in two different contexts:

▪ At composition time, within the builder tool.

▪ At execution time, with the runtime environment.

INTERFACE OF A COMPONENT

▪ This model defines four types of port:

▪ methods,

▪ properties,

▪ event sources and

▪ event sinks called listeners.

Read-only property

Write-only property

Property

Method

Event source

Event sink (listener)

Bounded property

v Vetoable property

ro

wo

1 Unicast event source

Ports

IMPLEMENTATION OF A COMPONENT

▪ Most bean components are implemented by a simple Java object, the object being encapsulated in the component, but there are more sophisticated implementations possible.

▪ Wrapping a legacy object.

▪ Multiple-objects implementation.

▪ Dependency on traditional entities.

IMPLEMENTATIONS OF BEAN COMPONENTS

Object

Method

Method call

Binding

A simple implementation A more complex implementation

COMPONENTS ASSEMBLY

▪ Assembly is one of the key features of Java Bean though no not specific solution is provided.

▪ Different ways of assembling components are supplied.

Component-based assembly Heterogeneous assembly

PACKAGING AND DEPLOYMENT

▪ Java Beans define a model for packaging components into archives.

▪ Includes the definition of dependency relationships between the package items.

▪ The customization code can be more complex than the component itself!

▪ Each package item can be marked "Design Only", so that they can be removed in a final application.

JAVA▪ Portability via JVM

▪ Complemented the JVM with the JDK

▪ encapsulate platform differences

▪ Java applets

▪ Memory management

▪ Remote Message Invocation

▪ Java Transaction API

▪ Java Messaging Service

▪ Java Naming and Directory Interface

▪ Java Database Connectivity

▪ Java 2 Enterprise Edition

▪ Which technology provides adequate tools for analysis on ad hoc basis

▪ Which type of computing and technology will be required for B2C

▪ How XML is replacing EDI

▪ Which technology enforce compliance and improvements in business process

▪ What are 3 genuine technologies for creating distributed objects and compare contrast those 3

UNIFIED MODELING LANGUAGE▪ Unified Modeling Language (UML) by OMG.

▪ Based on a specification developed by Rational Software

▪ OMG specification experts represent efforts of 21 tool vendors and industry experts

▪ Wide acceptance in the industry

▪ Efforts to expand its scope.

▪ Visualizations and diagramming techniques

▪ commonly is the class diagram

▪ Common Warehouse Metamodel (CWM)

▪ Enterprise Distributed Object Computing (EDOC), EAI, and action semantics(under development)

▪ Workflow process(anticipated)

▪ Complemented by XML Model Interchange (XMI)

▪ Generating skeleton, class code from specifications

▪ Complete large-scale applications from UML sre expected

▪ Reducing the effort of programming applications with interoperability

MODEL DRIVEN ARCHITECTURE (MDA) ▪ using UML to define

technology-independent models to map them for specific technologies.

▪ standard specifications for services, applications, and components with operability

PUBLIC KEY INFRASTRUCTURE (PKI)

▪ Used with digital certificates

▪ Digital certificates are issued by a trusted certification authority

▪ encrypted with the authority's private key

▪ The systems and services for issuing and using certificates are called the PKI.

▪ Mechanism to obtain certified identification from a trusted authority

▪ Without previously being identified

▪ Used by Secure Sockets Layer (SSL)

▪ Sender and receiver can authenticate each other with their digital certificates

▪ authenticate a message received from a specified source

▪ the export of public key encryption technology from the United States was restricted as a threat to national security

DIGITAL SIGNATURES▪ Employ public key technology

▪ Signature authenticates the document

▪ Prevents the signer from repudiating the document

▪ To attach a digital signature

1. the document is first processed by a digest function

2. The digest value is then encrypted with the signer's private key and attached to the digital document

3. The recipient can execute the same digest function decrypt the signature with the originator's public key

DIGITAL SIGNATURES▪ If the two digest values are equal, the signature

verifies

▪ Federal legislation was adopted recently giving digital signatures the same legal effect as signatures on paper documents

▪ This opens the door to widespread replacement of paper legal documents

▪ The consequence is that the scope of business transactions conducted over the Internet will be expanded greatly.

WIRELESS INTERFACE DEVICES▪ Cellular phones have become commonplace

▪ Enables new forms of Internet purchases

▪ Frees employees to conduct business anywhere and at any time

▪ The Web pages accessed by these devices cannot be formatted the same as Web pages for conventional Web browser displays

▪ Web sites accessed by these devices must recognize device limitations

KNOWLEDGE MANAGEMENT capture, cataloging, retrieval, and application of

enterprise knowledge,

KNOWLEDGE MANAGEMENT▪ Technical support for knowledge management is still

in the early stages

▪ Knowledge management is a second-order business function

▪ It is difficult to implement and sustain such systems when mainstream systems involve inconsistent data, diverse technologies, and constant change.

▪ As enterprises implement consistent architectures, we can expect to see a growth in knowledge management facilities linked to business processes and applications.

AGENT TECHNOLOGY▪ A software agent is an autonomous program that

senses and reacts to its environment

▪ Its environment may include information about the actions of other agents.

▪ Agent itself will determine if, when, and how it will perform its function.

▪ A simple agent:to monitor some activity, raise an alarm

▪ More sophisticated agents:to direct the flow of work

AGENT TECHNOLOGY▪ Agents also might be employed for knowledge

management

▪ Agent technology is still in its infancy

▪ Consistent enterprise architecture will be a key enabler for such technology.

INTERACTIVE VOICE▪ Few applications make use of voice input or output

▪ Voice input and output require additional functionality and increase the risk of errors

▪ Voice input and output also enable hands- and eyes-free operation in activities and environments that are not conducive to conventional terminal interaction.

▪ Interactive voice communication will require yet another form of message formatting. Enterprise applications will need to anticipate these requirements when they prepare and accept message content.

MODEL DRIVEN ARCHITECTURE▪ The Model Driven Architecture strategy of the OMG

provides the ability to specify applications and standards as Platform Independent Models (PIM) that can be mapped to evolving technical platforms.

▪ Tools provide the ability to transform a PIM specification to executable code

▪ Standard mappings will enable independently developed applications and components to be interoperable

▪ The UML Profile for Enterprise Distributed Object Computing(EDOC ) provides the modeling elements for the platform-independent specification of component-based, large-scale systems

▪ The technology to implement MDA exists, the standards and tools for composing large-scale applications are under development.