This document provides an overview of service-based architectures and defines some of the key issues for data developers. It discusses the business needs driving service-based architectures, including providing access to data, services, and processes anytime from anywhere. It also outlines some of the IT implications, such as the need for multiple levels of integration and security. The document defines what constitutes a service and lists some key characteristics of service-oriented architectures, such as services representing published contracts between providers and consumers.

1. 1
Services Based ArchitecturesServices Based Architectures
Defining The Issues For Data DevelopersDefining The Issues For Data Developers
Robert AbateRobert Abate Ruben TuRuben Tuññgolgol
Managing Partner/Principal Consultant Senior Architect
Intellisys, Inc.Intellisys, Inc. Novell, Inc.Novell, Inc.
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.

2. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
2
Table Of Contents
ServiceService--Based Architecture (SBA) OverviewBased Architecture (SBA) Overview
SBA Case StudiesSBA Case Studies –– Foundations andFoundations and
PracticesPractices
Polo Ralph Lauren & NPD GroupPolo Ralph Lauren & NPD Group
Global Bank, Leasing Company, ConglomerateGlobal Bank, Leasing Company, Conglomerate
SBA and Web ServicesSBA and Web Services
Questions & AnswersQuestions & Answers

3. 3
Service-Based Architecture
Overview
The Business Dilemma,The Business Dilemma,
IT Implications,IT Implications,
And Key Characteristics Of SBA.And Key Characteristics Of SBA.

4. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
4
The Business Dilemma
Provide access toProvide access to
DataData
ServicesServices
ProcessesProcesses
Anytime, anywhere, onAnytime, anywhere, on
any deviceany device
Without forgettingWithout forgetting
security and privacysecurity and privacy
Existing Systems
Transactions PackagesUtilitiesCollaboration Docs/ContentNetwork
Business Requirements
Employees BusinessesPartners Customers
Services Based Architecture Overview

5. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
5
Solution Requirements
Leverage existing systems
Protect systems
Build new applications
Security & Identity Management
Simplified sign-on
Identity management
Security
Multiple Levels of Integration
Process management
Integration Services
Web Services Foundation
Device support
Personalization
Presentation
Resources,
Existing Systems Transactions PackagesUtilitiesCollaboration Docs/ContentNetwork
Business Requirements
Employees B2BPartners Customers
Services Based Architecture Overview

6. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
6
Business Drivers For SBA / SOA
Services Based Architecture Overview
Interconnection Of Enterprise ApplicationsInterconnection Of Enterprise Applications
Replacement Of Legacy SystemsReplacement Of Legacy Systems
Removal Of Hard To Support, Complex InterfacesRemoval Of Hard To Support, Complex Interfaces
Foundation For Web ServicesFoundation For Web Services
Increased Value from Information Technology:Increased Value from Information Technology:
Lower Total Cost to ChangeLower Total Cost to Change (Shared Integration Infrastructure)(Shared Integration Infrastructure)
Lower Total Cost of OwnershipLower Total Cost of Ownership (Shared App., Network & Semantic Infrastructure)(Shared App., Network & Semantic Infrastructure)
FutureFuture--Proof Information FacilitiesProof Information Facilities (Flexibility & Utilization of Assets)(Flexibility & Utilization of Assets)
Improved Business Productivity:Improved Business Productivity:
Higher Throughput Per Managed ProcessHigher Throughput Per Managed Process (Strait Thru Processing)(Strait Thru Processing)
The RealThe Real--Time, Dynamic EnterpriseTime, Dynamic Enterprise (Zero(Zero--Latency and Highly Agile)Latency and Highly Agile)
Enterprise Data Quality, Architecture & IntegrationEnterprise Data Quality, Architecture & Integration
Standardization Of Corporate MetadataStandardization Of Corporate Metadata

7. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
7
IT Implications Of An SOA
Business processes need to span organizationBusiness processes need to span organization
boundaries.boundaries. Businesses produce and consume services.Businesses produce and consume services.
They need to exchange data,They need to exchange data, ““plugplug--inin”” to each otherto each other’’ss
processes without compromising security and privacy andprocesses without compromising security and privacy and
confidentiality.confidentiality.
Businesses need to measure the relative value ofBusinesses need to measure the relative value of
the services they offer or consume.the services they offer or consume. Services thatServices that
become discrete elements of business processes provide anbecome discrete elements of business processes provide an
opportunity to factor them into KPIopportunity to factor them into KPI’’s.s.
Risk mitigation.Risk mitigation. Incremental implementations provideIncremental implementations provide
measurement (and exit) points minimizing risks.measurement (and exit) points minimizing risks.
Service-Based Architecture Overview
TheThe ““realreal--timetime”” enterprise requires services that canenterprise requires services that can
be recomposed, repurposed and delivered to anybe recomposed, repurposed and delivered to any
device, anytime from anywhere.device, anytime from anywhere.

8. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
8
IT Implications Of An SBA / SOA
Adaptability.Adaptability. IT solutions need to be more adaptable to aIT solutions need to be more adaptable to a
changing landscape of standards, technologies, products andchanging landscape of standards, technologies, products and
service producers and consumers.service producers and consumers.
Past, current & future technology investments needPast, current & future technology investments need
to leveraged.to leveraged. Rewrites or replacement of legacy systemsRewrites or replacement of legacy systems
(i.e., anything in production) is deemed as too expensive.(i.e., anything in production) is deemed as too expensive.
Multiple levels of Integration.Multiple levels of Integration. Integration points must beIntegration points must be
at the data, application logic and business process levels.at the data, application logic and business process levels.
Security.Security. Ensure that theEnsure that the rightright people are participating in thepeople are participating in the
rightright process and accessingprocess and accessing rightright data.data.
Service-Based Architecture Overview

9. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
9
What Is A Service …
Service-Based Architecture Overview
A Service Is An Application And / Or Function That:A Service Is An Application And / Or Function That:
Is Designed To Receive Requests From Any SourceIs Designed To Receive Requests From Any Source –– Making NoMaking No
Assumptions As To The Functional Correctness (Syntactic OrAssumptions As To The Functional Correctness (Syntactic Or
Semantic) Of An Incoming RequestSemantic) Of An Incoming Request
Within Each Request, Encompasses A Complete & IndependentWithin Each Request, Encompasses A Complete & Independent
Unit Of Work (Business Or Technical)Unit Of Work (Business Or Technical)
May Stand On ItMay Stand On It’’s Own Or Be Part Of A Larger Set Of Functionss Own Or Be Part Of A Larger Set Of Functions
That Constitute A Larger Service; But ItThat Constitute A Larger Service; But It’’s Scope Is Such Thats Scope Is Such That
Each Request Leaves The System In A Long Term Steady StateEach Request Leaves The System In A Long Term Steady State
Is Designed For And Provides For A NetworkIs Designed For And Provides For A Network--Accessible InterfaceAccessible Interface
Keep Units Of Work Together That Change Together (HighKeep Units Of Work Together That Change Together (High
Cohesion) & Build Separation Between Units That ChangeCohesion) & Build Separation Between Units That Change
Independently (Low Coupling).Independently (Low Coupling).

10. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
10
Key SOA Characteristics #1
Services as published contracts between service providers /Services as published contracts between service providers /
consumers. This impliesconsumers. This implies
WellWell--defined, computerdefined, computer ““understandableunderstandable”” producer/consumer responsibilitiesproducer/consumer responsibilities
and interfacesand interfaces
Services descriptions that permit automated discovery and invocaServices descriptions that permit automated discovery and invocationtion
Loose coupling and high cohesion. Services do one thing and oneLoose coupling and high cohesion. Services do one thing and one thing wellthing well
and should have minimal interdependencies. Hard to produceand should have minimal interdependencies. Hard to produce --> Hard to> Hard to
consume!consume!
A service, like a contract, once published and consumed is veryA service, like a contract, once published and consumed is very difficult todifficult to
amendamend –– a challenge that architects need to address.a challenge that architects need to address.
Standards based. ConsiderStandards based. Consider
Implementation technologies (.NET, J2EE, Web Services, XML)Implementation technologies (.NET, J2EE, Web Services, XML)
Business facing standards (OASIS, Rosetta,Business facing standards (OASIS, Rosetta, ebXMLebXML, etc), etc)
ProcessProcess--oriented, potentially longoriented, potentially long--runningrunning
Many services are actually front ends to discrete business proceMany services are actually front ends to discrete business processes.sses.
Services, specially, those in the B2Bi space may take hours or dServices, specially, those in the B2Bi space may take hours or days toays to
complete.complete.
Secure, trustworthySecure, trustworthy
Services should be calibrated to the consumerServices should be calibrated to the consumer’’s identity and authorizations.s identity and authorizations.
Services should provide guarantees certain guarantees (guaranteeServices should provide guarantees certain guarantees (guaranteed delivery,d delivery,
guaranteed action, nonguaranteed action, non--repudiation, etc)repudiation, etc)
Service-Based Architecture Overview

11. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
11
Key SOA Characteristics #2
Service-Based Architecture Overview
A SBA Consists Of:A SBA Consists Of:
Data CleansedData Cleansed
FoundationFoundation
Integrated MetadataIntegrated Metadata
Defined Units OfDefined Units Of
WorkWork
Standards BasedStandards Based
Shared ServicesShared Services
Units Of WorkUnits Of Work
Loosely CoupledLoosely Coupled
Federated ControlFederated Control

12. 12
SBA Best Practices (Learned)
““Best practices are those strategies, activities, orBest practices are those strategies, activities, or
approaches which have been shown throughapproaches which have been shown through
implementation / evaluation or industry usage to beimplementation / evaluation or industry usage to be
effective at managing issues thru use of theseeffective at managing issues thru use of these
practices, or proactively limiting their effect"practices, or proactively limiting their effect"

13. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
13
Organizational Challenge
CEO
CFO CIO COO
Business Line
Presidents
Finance Legal
Business
Line #1
Business
Line #n
IT Marketing
Competitor
Information
Contracts
StoresSales
Claims Customers
LogisticsInventory Inventory
Vendors
BusinessBusiness
Issues:Issues:
Multiple,Multiple,
Views &Views &
DefinitionsDefinitions
Of DataOf Data
InconsistentInconsistent
SemanticsSemantics
No SingleNo Single
Dictionary /Dictionary /
MetadataMetadata
BusinessesBusinesses
Are StoveAre Stove--
Piped In ThePiped In The
Organization,Organization,
Why ShouldWhy Should
The Data BeThe Data Be
Different?Different?
““I Own ThatI Own That
DataData””
SBA Best Practices (Learned)

14. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
14
Organizational Data Solution
Sales Data
External Data
Vendor Data
Product Data
Customer Data
CEO
CFO CIO COO
Business Line
Presidents
Finance Legal
Business
Line #1
Business
Line #n
IT Marketing
Operational Data Store Corporate
Data
Warehouse
Corporate
Metadata
Exisiting TDS
System
Exisiting TDS
System
Exisiting TDS
System
Exisiting TDS
System
Exisiting TDS
System
Web Solutions
Supply Chain /
CRM / Add-Ons
"Single Version Of The Truth"
BusinessBusiness
Solutions:Solutions:
Single View &Single View &
Definition OfDefinition Of
MetadataMetadata
(Single Version(Single Version
Of Truth)Of Truth)
SemanticsSemantics
From SingleFrom Single
DictionaryDictionary
DataData
WarehousingWarehousing
And OtherAnd Other
ApplicationApplication
Additions AreAdditions Are
Easily Added /Easily Added /
ConnectedConnected
Since MetadataSince Metadata
DefinedDefined
SBA Best Practices (Learned)

15. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
15
Metadata As A Glue
MetadataMetadata promotes agreement on nature / content of datapromotes agreement on nature / content of data
Comprehensive metadata capabilitiesComprehensive metadata capabilities for all tools in thefor all tools in the
integration environment is required (modeling, IDE, etc.)integration environment is required (modeling, IDE, etc.)
A Single dictionaryA Single dictionary fosters common understanding and clearfosters common understanding and clear
communications;communications; two or more breed confusiontwo or more breed confusion
A centralized metadata management architecture,A centralized metadata management architecture, allows usersallows users
to assess the downstream impact of change, before theto assess the downstream impact of change, before the
changes are made (Crosschanges are made (Cross--Impact Analysis)Impact Analysis)
This importance is best conveyed though example:This importance is best conveyed though example:
responsibilities for taking data from acquisition, thoughresponsibilities for taking data from acquisition, though
integration, to analysis and to delivery to business users mayintegration, to analysis and to delivery to business users may
rest with multiple, and sometimes disconnected groups.rest with multiple, and sometimes disconnected groups. TheThe
data however is not disconnected.data however is not disconnected. If one group makes aIf one group makes a
change to a data model / process, that change will have achange to a data model / process, that change will have a
ripple effect throughout the entire data lifecycleripple effect throughout the entire data lifecycle
SBA Best Practices (Learned)

16. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
16
Data Integration Issues
Integration Of Enterprise Into An SBA / SOAIntegration Of Enterprise Into An SBA / SOA
Requires That Foundation Supply Data:Requires That Foundation Supply Data:
Consistency (Semantic, etc.)Consistency (Semantic, etc.)
Quality (Element, Groupings, etc.)Quality (Element, Groupings, etc.)
Cleanliness (Nulls, Bad Records)Cleanliness (Nulls, Bad Records)
Integrity (Referential Integrity, etc.)Integrity (Referential Integrity, etc.)
Standards Based (XML, SOAP, J2EE, etc.)Standards Based (XML, SOAP, J2EE, etc.)
Lowest Level Of Granularity (Elements, Rows, ...)Lowest Level Of Granularity (Elements, Rows, ...)
Timely Delivery At A Reasonable Cost !Timely Delivery At A Reasonable Cost !
SBA Best Practices (Learned)

17. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
17
Semantic Consistency
Semantic ConsistencySemantic Consistency
Applies To MostApplies To Most
Artifacts:Artifacts:
MetadataMetadata
Domain ObjectsDomain Objects
Promotes BusinessPromotes Business
Understanding ThatUnderstanding That
The Underlying DataThe Underlying Data
Is The Same, View IsIs The Same, View Is
DifferentDifferent
Promotes A CommonPromotes A Common
Language ForLanguage For
Developers WhenDevelopers When
Combined With ACombined With A
Common DictionaryCommon Dictionary
Semantic Consistency
Business
Domain
Domain
Objects
Metadata
yields
Executables
Database
Tables
Messages,
Transactions
Implemented
as
XML Schemas,
DTDs
Service
Descriptions
Dictionaries
Taxonomies
Takes the form
of
SBA Best Practices (Learned)

18. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
18
Promoting Common Understanding
Integration Of Enterprise Into An SBA / SOAIntegration Of Enterprise Into An SBA / SOA
Requires That Foundation Provide Data In ARequires That Foundation Provide Data In A
Common Form / Model:Common Form / Model:
High Level UML ModelHigh Level UML Model
Business Process With Data Integration PointsBusiness Process With Data Integration Points
Mid Level Data ModelMid Level Data Model
Logical Problem Space With Connectors, KeysLogical Problem Space With Connectors, Keys
Low Level Data ModelLow Level Data Model
Physical Characteristics (Block Size, Rows,Physical Characteristics (Block Size, Rows, ……))
SBA Best Practices (Learned)

19. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
19
Iterative Development
Iterative Development Requires:Iterative Development Requires:
Business Process Model ProvidesBusiness Process Model Provides
Stability To IterationsStability To Iterations
Defines Subject Area And InterconnectionsDefines Subject Area And Interconnections
Logical Data Model ProvidesLogical Data Model Provides
Hooks And InterHooks And Inter--System CommonalitySystem Commonality
Allows For Patterns And ReAllows For Patterns And Re--UseUse
SBA Best Practices (Learned)

20. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
20
Best Practices Observed #1
Phased Development Approach:Phased Development Approach:
Phase IPhase I –– Centralize, Document & Cleanse DataCentralize, Document & Cleanse Data -- ODSODS
Phase IIPhase II –– Data Layer IntegrationData Layer Integration
Phase IIIPhase III –– Integrated Data PresentationIntegrated Data Presentation
Phase IVPhase IV –– Component IntegrationComponent Integration
Publish & SubscribePublish & Subscribe –– Centralized DBCentralized DB’’s (Customer)s (Customer)
Real Time MessagingReal Time Messaging
Phase VPhase V –– Enterprise Applications IntegrationEnterprise Applications Integration
SBA Best Practices (Learned)

21. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
21
Best Practices Observed #2
1.1. Define the longDefine the long--term vision in the form of an enterpriseterm vision in the form of an enterprise
integration architecture that utilizes standardsintegration architecture that utilizes standards--based toolsbased tools
that are proven to work togetherthat are proven to work together
2.2. Always start with a Common Data Model [CDM] that integratesAlways start with a Common Data Model [CDM] that integrates
the data between systems (ODS, CDW, etc.)the data between systems (ODS, CDW, etc.)
3.3. Create a hubCreate a hub--andand--spoke architecture using a data integrationspoke architecture using a data integration
platform (ETL or Integration Broker) to access data sourcesplatform (ETL or Integration Broker) to access data sources
and then populate the ODS and the CDW. Buy, not buildand then populate the ODS and the CDW. Buy, not build
components. Todaycomponents. Today’’s tools integrate at the metadata levels tools integrate at the metadata level
with powerful connectors and parallel interwith powerful connectors and parallel inter--operabilityoperability
4.4. Build bottomBuild bottom--up and not topup and not top--down for minimization of riskdown for minimization of risk
5.5. Services must be designed with a business process context.Services must be designed with a business process context.
Therefore, start with business document context to define.Therefore, start with business document context to define.
SBA Best Practices (Learned)

22. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
22
Best Practices Observed #3
6.6. Avoid building or buying any solution that does not integrateAvoid building or buying any solution that does not integrate
at the metadata level with a central metadata repository. Theat the metadata level with a central metadata repository. The
metadata can be generated, maintained and reported on bymetadata can be generated, maintained and reported on by
the data integration platform (either ETL or Integrationthe data integration platform (either ETL or Integration
BrokerBroker’’s provide this functionality).s provide this functionality).
7.7. Use a second generation data integration platform or one thatUse a second generation data integration platform or one that
supports both native interfaces into the source and targetsupports both native interfaces into the source and target
databases (not ODBC) and one that support both batch anddatabases (not ODBC) and one that support both batch and
messaging based transfers using todaymessaging based transfers using today’’s industry accepteds industry accepted
standards (J2EE, SOAP, etc.).standards (J2EE, SOAP, etc.).
8.8. When selecting XML standards, try to stay within yourWhen selecting XML standards, try to stay within your
corporations trade area (i.e.: Mortgage companies usecorporations trade area (i.e.: Mortgage companies use
MISMO, Retailers use EDIFACT, etc.)MISMO, Retailers use EDIFACT, etc.)
SBA Best Practices (Learned)

23. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
23
Best Practices Observed #4
9.9. Integrate ALL components of the architecture using theIntegrate ALL components of the architecture using the
metadata including:metadata including:
* Modeling, Application Development, Reporting, OLAP,
etc. should all connect to the repository
* Use the data integration platform to both generate and
maintain central metadata / change control records
* Generate extensible, XML-compliant metadata and
LDAP-compliant directories (as a minimum)
* Derive ALL of the local metadata using the central
metadata as the source of record.
10.10. Integrate different or multiple, networked, data integrationIntegrate different or multiple, networked, data integration
platform engines with a common global metadata. BEWAREplatform engines with a common global metadata. BEWARE
OF MULTIPLE VERSIONS OF THE TRUTH!OF MULTIPLE VERSIONS OF THE TRUTH!
SBA Best Practices (Learned)

24. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
24
Best Practices Observed #5
11.11. Use the realUse the real--time features of the data integration platform totime features of the data integration platform to
populate realpopulate real--time data into the ODStime data into the ODS
12.12. Do not load dirty source data into the ODS. Use the dataDo not load dirty source data into the ODS. Use the data
integration platformintegration platform’’s cleansing function to resolve logicals cleansing function to resolve logical
inconsistencies and provide for referential data integrity.inconsistencies and provide for referential data integrity.
13.13. Limit sources with access to the ODS, this will eliminateLimit sources with access to the ODS, this will eliminate
contention issues in the foundation.contention issues in the foundation.
** Deliver the information from the metadata tools using the
existing portal to the user community
* Use a business intelligence oriented corporate portal as the
gateway to both structured and unstructured information
* It is also easy to add data warehousing functionality through
this interface
SBA Best Practices (Learned)

25. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
25
Best Practices Observed #6
14.14. Anticipate scalability and performance issues by ensuringAnticipate scalability and performance issues by ensuring
that bottlethat bottle--necks are avoidednecks are avoided
** Parallel queries
* Distributed Tables
* Indices On Key Fields
* ODS Optimized For Speed Of Write (Third Normal Form)
* DW Optimized For Speed Of Read (Star Schema, …)
~ Pre-built Aggregates For Common Queries
~ In-Line Aggregation During Loading Process
15. Use a staging area, it will help in debugging loading issues,
and will provide a starting point from the same machine
removing network issues.
SBA Best Practices (Learned)

26. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
26
Data Cleansing And Integration
What Is Cleansed Data And Why Is ItWhat Is Cleansed Data And Why Is It ““DirtyDirty””??
Cleansed data refers to the transformation of data so that eachCleansed data refers to the transformation of data so that each
disparate system inputs itdisparate system inputs it’’s information into the ODS with thes information into the ODS with the
appropriate values & correct formatappropriate values & correct format (PC: data is integrity challenged).(PC: data is integrity challenged).
““DirtyDirty”” refers to data where relationships and/or business rules arerefers to data where relationships and/or business rules are
lacking or are inconsistently applied.lacking or are inconsistently applied.
What Does This Mean To I.S. Developers?What Does This Mean To I.S. Developers?
Part of the cleansing process to understand the way the data isPart of the cleansing process to understand the way the data is
currently captured in itscurrently captured in its ““nativenative”” or legacy system.or legacy system.
Second, is to understand the format of theSecond, is to understand the format of the ““newnew”” model and transformmodel and transform
the data appropriately (data vs. transaction).the data appropriately (data vs. transaction).
Next, business rules are used to govern data behavior.Next, business rules are used to govern data behavior.
Finally, the data must be validated in itFinally, the data must be validated in it’’s new form against thes new form against the
operational, legacy system for accuracy and business rules (someoperational, legacy system for accuracy and business rules (some
business rules may not exist in legacy systems).business rules may not exist in legacy systems).
SBA Best Practices (Learned)

27. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
27
Data Modeling Best Practices
Definition Of CDM?Definition Of CDM?
A Common Data Model [CDM] is a set of standard field names,A Common Data Model [CDM] is a set of standard field names,
descriptions and usage across the different divisions & systemsdescriptions and usage across the different divisions & systems
organized around business processes.organized around business processes.
A resultant output of the CDM is that it allows for the integratA resultant output of the CDM is that it allows for the integrateded
business processes.business processes.
Implementation Considerations?Implementation Considerations?
First, a model must be built to represent the business process mFirst, a model must be built to represent the business process modelodel
including theincluding the ““actorsactors””, data and activities., data and activities.
Second, identify the core entities, their relationships and theSecond, identify the core entities, their relationships and the unifyingunifying
fibers and repeating patterns across the whole model.fibers and repeating patterns across the whole model.
Third, the representations used by business areas must be validaThird, the representations used by business areas must be validatedted
to ensure accuracy (checks with CFO, divisions, departments, etcto ensure accuracy (checks with CFO, divisions, departments, etc).).
Fourth, the CDM must be logically modeled and normalized.Fourth, the CDM must be logically modeled and normalized.
Fifth, the CDM must be physically modeled & implemented.Fifth, the CDM must be physically modeled & implemented.
SBA Best Practices (Learned)

28. 28
SBA Case Studies
Polo Ralph LaurenPolo Ralph Lauren
AndAnd
The NPD GroupThe NPD Group

29. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
29
Data Integration Challenge
Wholesale
OLTP
System
WEB /
eCommerce
System
Licensing
OLTP
System Financial
System
[AP/AR/GL]
Business
Planning
System
Warehouse
System
Shipping
System
Data
Warehouse
Starting PointStarting Point
Issues:Issues:
For EveryFor Every
AddedAdded
System, MustSystem, Must
Code ( NCode ( N -- 1 )1 )
InterfacesInterfaces
Multiple,Multiple,
DisparateDisparate
Copies OfCopies Of
DataData
InconsistentInconsistent
SemanticsSemantics
No SingleNo Single
Dictionary /Dictionary /
MetadataMetadata
MultipleMultiple
SecuritySecurity
MechanismsMechanisms
SBA Case Studies – Polo & NPD Group

30. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
30
Data Layer Integration Solution
WholesaleWholesale
OLTPOLTP
SystemSystem
Web /Web /
eCommerceeCommerce
SystemSystem
LicensingLicensing
OLTPOLTP
SystemSystem
FinancialFinancial
SystemSystem
[AP/AR/GL][AP/AR/GL]
BusinessBusiness
PlanningPlanning
SystemSystem
WarehouseWarehouse
SystemSystem
ShippingShipping
SystemSystem
DataData
WarehouseWarehouse
Centralized ODSCentralized ODS
Common Data Model
= Wrapper-Facade
AsynchronousAsynchronous
communicationscommunications
TransactionalTransactional
System IntegrationSystem Integration
Async. comm.Async. comm.
via a messagevia a message--
orientedoriented
middlewaremiddleware
[MOM] added[MOM] added
the followingthe following
capabilities:capabilities:
Just in timeJust in time
propagationpropagation
of businessof business
eventsevents
Trickle inTrickle in
datadata
integrationintegration
SBA Case Studies – Polo & NPD Group

31. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
31
Polo Ralph Lauren and NPD Group
SBA Case Studies – Polo & NPD Group
Security and Identity Management
Employee Partner Business Customer
Services
Users and Devices
Resources,
Existing Systems
Java ClientPortlets .NETServletsJSP
Transactions PackagesUtilitiesCollaboration Docs/ContentNetwork

32. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
32
Polo Ralph Lauren Corporation
Administration &
Runtime
Monitoring
Environment
Development
Environment
Runtime Environment
Testing Environment
Security Environment
Polo Realities
and
Business Requirements
Constrain
Constrain
MultiMulti--FacetedFaceted
ArchitectureArchitecture
Development &Development &
RunRun--TimeTime
EnvironmentEnvironment
TestingTesting
EnvironmentEnvironment
Scalable FeaturesScalable Features
(Rapid Growth)(Rapid Growth)
Administration &Administration &
Monitoring OfMonitoring Of
EventsEvents
SBA Case Studies – Polo & NPD Group

33. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
33
Polo Ralph Lauren Corporation
Stylized Data Flow DiagramStylized Data Flow Diagram
(DFD) Denotes Informatica(DFD) Denotes Informatica’’ss
Power Center As The Hub.Power Center As The Hub.
Power Center Pumps Data ToPower Center Pumps Data To
And From Spokes (PoloAnd From Spokes (Polo
Legacy Systems, DataLegacy Systems, Data
Warehouses, Etc.)Warehouses, Etc.)
It Automatically GeneratesIt Automatically Generates
The Metadata And StoresThe Metadata And Stores
Consistent With The SterlingConsistent With The Sterling
KnowledgeBase.KnowledgeBase.
It Has BiIt Has Bi--Directional Links ToDirectional Links To
Erwin, PoloErwin, Polo’’s Physical Datas Physical Data
Modeling ToolModeling Tool
Power Center was entirelyPower Center was entirely
confined to the Data Layerconfined to the Data Layer
IA/IQ's Reporting Tools
Data Integration Layer
Informatica's Power Center
Extraction, Transformation and Load Tool
Polo Legacy Applications
PCIS is Men's
Wholesale's home
grown "ERP"
application
PCIS to ODS
PCISRetail
Island Pacific is
Retail's off-the-shelf
grown "ERP"
application
IP to ODS
Retail Sales
(DB2/400 Files)
Wholesale Sales
(DB2/400 Files)
Polo ODS
i2's Active Data
Warehouse feeds
i2's SCM package
ODS to i2 ADW
i2 ADW
Informatica's
Dynamic Data
Store (DDS)
Metadata Services
? ? ?
ODS to Polo DW
Polo Data
Warehouse
?
IQ KnowledgeBase
IQ Objects My Eureka
SBA Stylized Data Layer Flow
SBA Case Studies – Polo & NPD Group

34. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
34
Integrated Environments
CAPABILITIES:CAPABILITIES:
DevelopmentDevelopment
EnvironmentEnvironment
RuntimeRuntime
EnvironmentEnvironment
AdministrateAdministrate
EnvironmentEnvironment
BestBest
PracticesPractices
PurchasePurchase
Before BuildBefore Build
(Where(Where
Possible)Possible)
Development Run Time Administration Best PracticesDevelopmentDevelopment Run TimeRun Time AdministrationAdministration Best PracticesBest Practices
Code:
Jbuilder, SynerJ
RPG CL
Dreamweaver
Code:Code:
Jbuilder, SynerJJbuilder, SynerJ
RPG CLRPG CL
DreamweaverDreamweaver
Design:
Rational Rose
Visio Professional
Design:Design:
Rational RoseRational Rose
Visio ProfessionalVisio Professional
Data Model:
ERwin
Data Model:Data Model:
ERwinERwin
Requirements:
Rational Rose
Visio Professional
MS Word
Requirements:Requirements:
Rational RoseRational Rose
Visio ProfessionalVisio Professional
MS WordMS Word
LEGACY
DEVELOPMENT
LEGACYLEGACY
DEVELOPMENTDEVELOPMENT
Common Bus.
Components:
EJB’s
Common Bus.Common Bus.
Components:Components:
EJBEJB’’ss
Wrappers:
Native Compiler
Wrappers:Wrappers:
Native CompilerNative Compiler
Application
Servers:
Forte’ iPlanet
BEA Weblogics
ApplicationApplication
Servers:Servers:
ForteForte’’ iPlanetiPlanet
BEA WeblogicsBEA Weblogics
Messaging:
CORBA
BEA Tuxedo
Messaging:Messaging:
CORBACORBA
BEA TuxedoBEA Tuxedo
Databases:
ORACLE
DB2/400
Databases:Databases:
ORACLEORACLE
DB2/400DB2/400
Development
Methodology:
Rational Unified
Process
DevelopmentDevelopment
Methodology:Methodology:
Rational UnifiedRational Unified
ProcessProcess
QA
User Signoff
QAQA
User SignoffUser Signoff
Testing:
Winrunner
Alpha & Beta
Testing:Testing:
WinrunnerWinrunner
Alpha & BetaAlpha & Beta
Documentation:
Component
Oriented Design,
Implementation
Guide
Documentation:Documentation:
ComponentComponent
Oriented Design,Oriented Design,
ImplementationImplementation
GuideGuide
Standards:
Transactions, DB
Standards:Standards:
Transactions, DBTransactions, DB
SBA Case Studies – Polo & NPD Group
Consoles:
iPlanet Console
WebLogics Console
BEA Manager
Consoles:Consoles:
iPlanet ConsoleiPlanet Console
WebLogics ConsoleWebLogics Console
BEA ManagerBEA Manager
Operations:
HP OpenView
Operations:Operations:
HP OpenViewHP OpenView
Data Movement:
Informatica
PowerCenter
Data Movement:Data Movement:
InformaticaInformatica
PowerCenterPowerCenter

35. 35
SBA Case Studies
RetailRetail –– Executive DashboardExecutive Dashboard
Global BankGlobal Bank –– Corporate BankingCorporate Banking
Leasing CompanyLeasing Company –– Lease SyndicationLease Syndication
ConglomerateConglomerate –– ProvisioningProvisioning

36. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
36
Security and Identity Management
Services
ForecastsOrdersCustomerDocs/ContentInventoryProducts
Retail - Executive Dashboard
Inventory
Status
Products Forecasts
Order
Management
Planning
Engines
Customer
Management
Warehouse
Management
Docs/Content
Product Design
& Development
Resources,
Existing Systems
Executive
Customer
Data
Orders
SBA Case Studies – Retail, Bank, Leasing & Provisioning

37. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
37
Security and Identity Management
Global Bank - Service and Content Aggregation
Services
Users and Devices
Java ClientPortlets .NETServletsJSP
Employee Partner Business
Customer
Employee
Resources,
Existing Systems
Transactions PackagesUtilitiesCollaboration Docs/ContentNetwork
SBA Case Studies – Retail, Bank, Leasing & Provisioning

38. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
38
Leasing Company - Business Process Integration
Services
Users and Devices
Java ClientPortlets .NETServletsJSP
Lease
Applicant
Employee Investor Vendor /
Supplier
Resources,
Existing Systems
Transactions PackagesUtilitiesCollaboration Docs/ContentNetwork
Security and Identity Management
SBA Case Studies – Retail, Bank, Leasing & Provisioning

39. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
39
J2EE Application Server
Identity
Network
eDirectory
Active Directory
Transactions
Oracle, MySQL
exteNd
Packages
PeopleSoft, Baan
Portal
exteNd
Collaboration
GroupWise, Notes
Workflow / BPM
exteNd
ID Synchronization
Sync. Sync. Sync.Sync.
Sync.
Sync.
Firewall
Metadirectory
Web Simplified
Sign-on
Resource/Services
Simplified Sign-on
Identity
Web ApplicationsWeb Applications
Content Management
Workflow Search
Portal
Rules
Personalization
Web
ID Synchronization
Identity
Business Process
Integration
Web Services
Identity
Web Services IntegrationWeb Services Integration
Forecast Track HistoryPurchasingInventory
Conglomerate - Provisioning and Identity Management
SBA Case Studies – Retail, Bank, Leasing & Provisioning

40. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
40
Runtime Environment
Red Hat Linux ASRed Hat Linux AS
2.1 on Intel2.1 on Intel
AIX on IBM HW,AIX on IBM HW,
Windows 2000 onWindows 2000 on
Intel, MainframeIntel, Mainframe
Windows 2000 onWindows 2000 on
IntelIntel
Solaris 2.6 on SunSolaris 2.6 on Sun
HWHW
Hardware / OSHardware / OS
PeopleSoft, Baan,PeopleSoft, Baan,
AD, eDirectoryAD, eDirectory
Mainframe Apps,Mainframe Apps,
C++ AppsC++ Apps
AS400 Apps, VBAS400 Apps, VB
AppsApps
AS400 Apps, I2AS400 Apps, I2
Planning EnginesPlanning Engines
Backend SystemsBackend Systems
Oracle 9i,Oracle 9i, MySQLMySQLOracle 9iOracle 9iSQL Server 2000SQL Server 2000Oracle 8iOracle 8iDatabaseDatabase
exteNdexteNd JBrokerJBrokerMQ SeriesMQ SeriesMSMQ, MQMSMQ, MQ
SeriesSeries
Sun (Forte) Fusion,Sun (Forte) Fusion,
PowerMartPowerMart
MiddlewareMiddleware
exteNdexteNd App ServerApp ServerOracle 9i AppOracle 9i App
ServerServer
COM+COM+Sun (Forte) AppSun (Forte) App
ServerServer
Application ServerApplication Server
exteNdexteNd ComposerComposer
BPMBPM
NoneNoneBizTalkBizTalkSun (Forte) FusionSun (Forte) FusionProcessProcess
IntegrationIntegration
exteNdexteNd DirectorDirectorexteNdexteNd DirectorDirectorIISIISEureka PortalEureka PortalPresentationPresentation
ConglomerateConglomerate
(Identity Mgmt &(Identity Mgmt &
ProvisioningProvisioning
Global BankGlobal Bank
(Corporate(Corporate
Banking)Banking)
LeasingLeasing
Company (LeaseCompany (Lease
Syndication)Syndication)
Polo (ExecutivePolo (Executive
Dashboard)Dashboard)
SBA Case Studies – Retail, Bank, Leasing & Provisioning

41. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
41
Design & Development Environment
Custom developedCustom developedCustom developedCustom developedCustom developedCustom developedCustom developedCustom developedUnit TestingUnit Testing
ToolTool
Windows 2000 onWindows 2000 on
IntelIntel
Windows 2000 onWindows 2000 on
IntelIntel
Windows 2000 on IntelWindows 2000 on IntelWindows 2000 onWindows 2000 on
IntelIntel
DeveloperDeveloper
PlatformPlatform
CVSCVSPVCSPVCSMS Visual SourceSafeMS Visual SourceSafePVCSPVCSVersionVersion
ControlControl
JEditJEdit, XML Spy,, XML Spy,
exteNdexteNd Workbench,Workbench,
ComposerComposer
DesignerDesigner
JDeveloperJDeveloper,, InteliJInteliJ
IDEA,IDEA, SunONESunONE
(Forte for Java)(Forte for Java)
MS Visual Studio, XMLMS Visual Studio, XML
SpySpy
JBuilderJBuilder, Visual, Visual
SlickEditSlickEdit
IDEIDE
EnterpriseEnterprise
Architect,Architect, exteNdexteNd
Composer BPMComposer BPM
DesignerDesigner
TogetherTogether
ControlCenterControlCenter,,
ErwinErwin
Rational Rose, Erwin,Rational Rose, Erwin,
XML Spy, BizTalkXML Spy, BizTalk
Orchestration DesignerOrchestration Designer
Rational Rose, Erwin,Rational Rose, Erwin,
Sun (Forte) FusionSun (Forte) Fusion
Process DesignerProcess Designer
Design ToolDesign Tool
ConglomerateConglomerate
(Identity Mgmt &(Identity Mgmt &
Provisioning)Provisioning)
Global BankGlobal Bank
(Corporate(Corporate
Banking)Banking)
Leasing CompanyLeasing Company
(Lease Syndication)(Lease Syndication)
Polo (ExecutivePolo (Executive
Dashboard)Dashboard)
SBA Case Studies – Retail, Bank, Leasing & Provisioning

42. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
42
Key Patterns Used
Layers, Service LayerLayers, Service Layer
HalfHalf--Sync, HalfSync, Half--AsyncAsync
Domain ObjectsDomain Objects
Wrapper FaWrapper Faççadeade
ObserverObserver
MediatorMediator
Abstract FactoryAbstract Factory
Composite, CompositionComposite, Composition
SBA Case Studies – Retail, Bank, Leasing & Provisioning

43. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
43
Layers, Service Layers
Business ProcessBusiness Process
ApplicationApplication
DataData
DataLayer
(sampleComponents)
Business Process Layer (sample activities)
ApplicationLayer
(sample
Components)
Get Request
Data
approval not required
Perform Unit of
Work #2
Perform Unit of
Work #1
Get Approval Apply Ruleapproval
required
Approver
invoke
output
input
Rule
Processor
Database
(ODS, Data Warehouse)
XML
Document
DataService
Layer
Request Data
Transfer Object
Approval
Request Entry
invoke
invoke
Data Set Rule
delegate
some work
Domain Object
Data Transfer
Object
Domain
Object
Data
Mart
Data
Mart
XML
Document
Identity
invoke invoke
SBA Case Studies – Retail, Bank, Leasing & Provisioning

44. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
44
Half-Sync, Half-Async
DataLayer
(sampleComponents)
Business Process Layer (sample activities)
ApplicationLayer
(sample
Components)
Get Request
Data
approval not
required
Perform Unit of
Work #2
Perform Unit of
Work #1
Get Approval Apply Rule
async
Approver
sync
output
input
Rule
Processor
Database
(ODS, Data
Warehouse)
XML
Document
DataService
Layer
Request Data
Transfer Object
Approval
Request Entry
synch
sync
Data Set Rule
Domain Object
Data Transfer
Object
Domain
Object
Data
Mart
Data
Mart
XML
Document
sync async
sync sync
Mix of synchronousMix of synchronous
(blocking calls) and(blocking calls) and
asynchronous (nonasynchronous (non
blocking call)blocking call)
Sync andSync and asyncasync mixmix
is usually required inis usually required in
long runninglong running
interactions.interactions.
Examples:Examples:
Lease applicationLease application
processingprocessing
Wire transferWire transfer
ProvisioningProvisioning
ApprovalApproval
processingprocessing
Identity
SBA Case Studies – Retail, Bank, Leasing & Provisioning

45. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
45
Domain Objects
Leasing Company (LeaseLeasing Company (Lease
Syndication)Syndication)
Lease Application, Equipment,Lease Application, Equipment,
Offer, Investor, Customer,Offer, Investor, Customer,
Salability RuleSalability Rule
Global Bank (Corporate Banking)Global Bank (Corporate Banking)
Account, Account Portfolio, BankAccount, Account Portfolio, Bank
Statement, Transaction HistoryStatement, Transaction History
Conglomerate (IdentityConglomerate (Identity
Management & Provisioning)Management & Provisioning)
Identity, Provision, ProvisioningIdentity, Provision, Provisioning
Task, EventTask, Event
Multiple implementations: Classes,Multiple implementations: Classes,
XML Schemas/documents, DataXML Schemas/documents, Data
Transfer Objects, TablesTransfer Objects, Tables
SBA Case Studies – Retail, Bank, Leasing & Provisioning

46. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
46
Adapter, Wrapper Facade
Resources,
Existing Systems
Databases PackagesCustom AppsProcesses Docs/ContentDirectories
Services““WrapWrap””,,
repurpose,repurpose,
integrateintegrate
existing systemsexisting systems
ExposeExpose
backendbackend
functionality asfunctionality as
Web ServicesWeb Services
Services
SBA Case Studies – Retail, Bank, Leasing & Provisioning

47. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
47
Wrapper Façade – Global Bank
AccountPortfolioAccountPortfolio andand
AccountPortfolioServiceAccountPortfolioService areare
part of a Wrapper Fapart of a Wrapper Faççadeade
that aggregates bankingthat aggregates banking
services to a customerservices to a customer
portalportal
Some FaSome Faççades evolved intoades evolved into
Domain ObjectsDomain Objects
Backend Wrappers andBackend Wrappers and
Object AdaptersObject Adapters
homogenize access tohomogenize access to
various backvarious back--end systemsend systems
Enabled incremental roll outEnabled incremental roll out
of servicesof services
SBA Case Studies – Retail, Bank, Leasing & Provisioning

48. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
48
Observer, Mediator, Abstract Factory
Initiate processingInitiate processing
based on businessbased on business
eventsevents
Abstract Factory andAbstract Factory and
Mediator simplify theMediator simplify the
ObserverObserver’’ss
responsibility to that ofresponsibility to that of
a reporter of eventsa reporter of events
SBA Case Studies – Retail, Bank, Leasing & Provisioning

49. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
49
Observer, Mediator, Abstract Factory
Leasing Company, Conglomerate Observers and MediatorsLeasing Company, Conglomerate Observers and Mediators
Observer (Polo, Leasing Company, Global Bank, Conglomerate)Observer (Polo, Leasing Company, Global Bank, Conglomerate)
Implemented as message queue listeners (receivers)Implemented as message queue listeners (receivers)
Messages in queue contain events or work requestsMessages in queue contain events or work requests
Initiated business processes directlyInitiated business processes directly
Mediator (Global Bank)Mediator (Global Bank)
Invoked by ObserverInvoked by Observer
Orchestrated delegated tasks in the absence of a process managerOrchestrated delegated tasks in the absence of a process manager
(e.g., wire transfer)(e.g., wire transfer)
Abstract Factory (Leasing Company, Conglomerate)Abstract Factory (Leasing Company, Conglomerate)
Invoked by observerInvoked by observer
Apply rules before instantiating a process, e.g.,Apply rules before instantiating a process, e.g.,
Determine suitability of Lease Application for syndicationDetermine suitability of Lease Application for syndication
Determine availability of Provision for a given IdentityDetermine availability of Provision for a given Identity
SBA Case Studies – Retail, Bank, Leasing & Provisioning

50. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
50
Composite, Composition
NOTE: Composition is not a design patternNOTE: Composition is not a design pattern
More of a design approach: favorMore of a design approach: favor
composition over inheritancecomposition over inheritance
Differences (at the risk of oversimplifying):Differences (at the risk of oversimplifying):
Composite aggregates entities with aComposite aggregates entities with a
common interface or supercommon interface or super--classclass
Composition aggregates dissimilarComposition aggregates dissimilar
entitiesentities
Common usageCommon usage
PartPart--whole situationswhole situations
XML SchemaXML Schema –– simpleTypes,simpleTypes,
complexTypes as building blockscomplexTypes as building blocks
Data Transfer Object and Domain ObjectData Transfer Object and Domain Object
build upon finer grained objects.build upon finer grained objects.
ExamplesExamples
Transactions, Balances, StatementTransactions, Balances, Statement
Lease Application, Lessor, Lessee, LeaseLease Application, Lessor, Lessee, Lease
ObjectObject
Provision, Provisioning Task, Provisioner,Provision, Provisioning Task, Provisioner,
IdentityIdentity
Shirt, collar, sleeve, trim, trim setShirt, collar, sleeve, trim, trim set
SBA Case Studies – Retail, Bank, Leasing & Provisioning

51. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
51
Composite, Composition
Provisioning and Lease Syndication: XML elements and complexTypeProvisioning and Lease Syndication: XML elements and complexTypess
consistent with Domain Objects, Data Transfer Objects and databaconsistent with Domain Objects, Data Transfer Objects and database tablesse tables
SBA Case Studies – Retail, Bank, Leasing & Provisioning

52. Robert Abate
Ruben Tuñgol
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.
52
Questions & Answers
Open Discussion …
Robert AbateRobert Abate Ruben TuRuben Tuññgolgol
Managing Partner/Principal Consultant Senior Architect
Intellisys, Inc.Intellisys, Inc. Novell, Inc.Novell, Inc.
Intellisys@att.netIntellisys@att.net ruben.tungol@novell.comruben.tungol@novell.com
(201) 745(201) 745--76807680
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.

53. 53
Services Based ArchitecturesServices Based Architectures
Defining The Issues For Data DevelopersDefining The Issues For Data Developers
Robert AbateRobert Abate Ruben TuRuben Tuññgolgol
Managing Partner/Principal Consultant Senior Architect
Intellisys, Inc.Intellisys, Inc. Novell, Inc.Novell, Inc.
Intellisys@att.netIntellisys@att.net ruben.tungol@novell.comruben.tungol@novell.com
(201) 745(201) 745--76807680
INTELLIgent
SYStems
CorporatIoN
INTELLISYS, Inc.