enterprise architecture models
DESCRIPTION
TRANSCRIPT
![Page 1: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/1.jpg)
04/09/23 Ch.3 1
Defining Enterprise Architecture
Bina Ramamurthy
![Page 2: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/2.jpg)
04/09/23 Ch.3 2
Introduction
We will describe a general framework for an enterprise architecture.Goals are not specific to a particular application but to the enterprise as a whole.Automation, streamlining, flexibility, workflow driven applications are some of the features we will focus on.
![Page 3: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/3.jpg)
04/09/23 Ch.3 3
Topics for discussion
General characteristicsBusiness system hierarchyIntegration infrastructure modelNetwork modelWorkflow modelAn enterprise integration scenarioSummary
![Page 4: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/4.jpg)
04/09/23 Ch.3 4
General Characteristics
Distributed computingComponent-based applicationsEvent-driven systemsLoose coupling of business functionsDecision support systemsWorkflow managementInternet access and personalization of interfaces
![Page 5: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/5.jpg)
04/09/23 Ch.3 5
Distributed systems
Scalability: it should be possible to accommodate increased number of user, increased number of transactions, or expand the scope of functionality.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 middelware.
![Page 6: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/6.jpg)
04/09/23 Ch.3 6
Component-based applications
Should support 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.Sun’s Enterprise Java Beans (EJB), CORBA component model (CCM) and Microsoft’s COM+.
![Page 7: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/7.jpg)
04/09/23 Ch.3 7
Event-driven process
Businesses are driven by events: an order is placed, a shipment is received, a machine fails, a person is hired.Processes must be streamlined.When a problem requiring management attention occurs in production, appropriate manager should be notified immediately. This requires a change in the design of systems and the way they interoperate. (Project 1: IncidentWeb)
![Page 8: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/8.jpg)
04/09/23 Ch.3 8
Loose coupling
Traditional: large, monolithic solutions.Desired: highly coherent focused solutions linked through the transfer of transactions in an asynchronous mode of communication.Messages queues are used for comm.Loose coupling allows for independently developed applications to interact without concern about time, internal information format, and technology.
![Page 9: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/9.jpg)
04/09/23 Ch.3 9
Decision Support Systems(p.48,49)
Enterprise integration architecture must support decision makers with these information: Current status Exceptions (system and business-based) Historical records Relevant knowledge
Currently business exceptions (what we call incidents in project1) are not recognized by systems, but rather by humans.
![Page 10: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/10.jpg)
04/09/23 Ch.3 10
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.
![Page 11: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/11.jpg)
04/09/23 Ch.3 11
Project1 1. Define at least four business exceptions
(incidents).2. Define limits or exceptional conditions that
will trigger these exceptions.3. Decide who and which applications should be
“notified” about the exceptions. You may use email (mail api), messaging (message queues) or simple method invocation to implement this.
4. Define what remedial actions should be taken.5. For the cheapbooks.coms: possible
exceptions can be “out of stock”, and “denial of service”.
![Page 12: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/12.jpg)
04/09/23 Ch.3 12
Business Process Automation
Traditionally: documents were source of input and reports were produced as outputs.Current business involve interactions between humans as well as humans and computers.Business process automation: workflow management post a “work list” to a person or application. Delays can be monitored, action item can be brought to attention based on a priority.Controls can be applied to make to sure exceptions are given proper attention and actions receive proper authorization.
![Page 13: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/13.jpg)
04/09/23 Ch.3 13
Integration Infrastructure Model (fig.3.2)
LegacySystem
Adapter
Message Queue
EnterpriseCOTSApplication
DistributedComponentBased systems
Decision SupportSystem
MainControl/TransApplication
Enterprise Infrastructure
![Page 14: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/14.jpg)
04/09/23 Ch.3 14
Workflow Process Model
Business processes drive the operation of a business.Examples: (enterprise level) fill customer order, get (trivial) approval on a form.Workflow: process definition, process system, activity, requester, personal work list, resource assignment facility, process manager, process interoperability.
![Page 15: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/15.jpg)
04/09/23 Ch.3 15
Figure 3.4 Workflow Process Model
Process A instance
Process B instance
Requester
Process manager
Resource AssignmentFacilities
Personal Worklist
Process A Definition
![Page 16: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/16.jpg)
04/09/23 Ch.3 16
Component-based model
We will look at it in the context of J2EE and EJB next week.
![Page 17: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/17.jpg)
04/09/23 Ch.3 17
Enterprise Scenerio
Figure 3.8Customer, sales portal, customer representative, billing service, order processing, customer relationship manager, accounting, archives, management information, exceptions, purchasing, warehouse, supplier, carrier, shipping, carrier.. Back to customer.
![Page 18: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/18.jpg)
04/09/23 Ch.3 18
Summary
Enterprise systems: processes, applications, application components, messaging, exceptions and notification.We looked workflow model.We will look into component model later.
![Page 19: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/19.jpg)
04/09/23 Ch.3 19
Topics of Discussion
State the main ideas you’ll be talking about
![Page 20: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/20.jpg)
04/09/23 Ch.3 20
Topic One
Details about this topicSupporting information and examplesHow it relates to your audience
![Page 21: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/21.jpg)
04/09/23 Ch.3 21
Topic Two
Details about this topicSupporting information and examplesHow it relates to your audience
![Page 22: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/22.jpg)
04/09/23 Ch.3 22
Topic Three
Details about this topicSupporting information and examplesHow it relates to your audience
![Page 23: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/23.jpg)
04/09/23 Ch.3 23
Real Life
Give an example or real life anecdoteSympathize with the audience’s situation if appropriate
![Page 24: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/24.jpg)
04/09/23 Ch.3 24
What This Means
Add a strong statement that summarizes how you feel or think about this topicSummarize key points you want your audience to remember
![Page 25: Enterprise Architecture Models](https://reader036.vdocuments.mx/reader036/viewer/2022081413/54795890b4af9f9b158b47f9/html5/thumbnails/25.jpg)
04/09/23 Ch.3 25
Next Steps
Summarize any actions required of your audienceSummarize any follow up action items required of you