approaches for modeling soas within existing architecture tools and reference models second...
TRANSCRIPT
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models
Second Service-Oriented Architectures for E-Government Conference
October 31, 2006
Michael Alford: [email protected]
Kevin Brett: [email protected]
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 2
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
What this training session is about
Service Oriented Architectures are the mandated standard for federal agencies
But…
“SOA” is ambiguous and poorly understood, particularly by business managers
To gain the benefits of SOA, Enterprise Architecture modeling can help: Clarify ambiguities Create a common language between IT and management Encourage constructive adoption of SOA ideas
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 3
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Background on this training session
The approaches presented here are a work in progress, based mainly on SRA’s modeling of SOA architectures at the Environmental Protection Agency (EPA)– We make assumptions to resolve ambiguities in existing
guidance– We sometimes go against OMB terminology and usage in
order to produce a more internally consistent metamodel
We invite audience participation and discussion throughout
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 4
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
BACKGROUND
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 5
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business Evolution of Reuse in Software Development
1970s 1980s 1990s Early 2000s TODAY
Reuse through function-oriented
programming(sub-routine and function reuse
Reuse through object-oriented programming(class reuse)
Reuse through distributed object technologies and component based
architectures(CORBA/DCOM/
DCE and component reuse
Reuse through early service orientation
(reuse of web services)
Service-Oriented Architectures
(SOA)
▼ ▼ ▼ ▼ ▼
“The future of software development will likely consist of complete assembly of applications from services and components – often referred to as “true software manufacturing.”
Services and Component-Based Architectures, CIO Council, January 2006
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 6
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
OMB’s Vision for SOA Application
Reusability and repurposing of effort is the core concept
OMB is, in effect, applying the IT principle of increasing abstraction in systems development to the business itself
Bottom line: It’s not always about IT anymore– Practitioners need to expand their thinking about
services to encompass business processes
A Component is defined as “a self-contained business process or service with predetermined functionality that may be exposed through a business or technology interface.”
FEA Service Component Reference Model
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 7
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business Applying SOA Abstraction to Business Processes
Performance Reference Model (PRM)
Business Reference Model (BRM)
Service Component Reference Model (SRM)
Data Component Reference Model (DRM)
Technical Reference Model (TRM)
Co
mp
on
en
t ba
sed
Arc
hite
ctu
res
Perfo
rma
nce
an
d B
us
iness
Drive
rs
Inputs, Outputs, and Outcomes Uniquely Tailored Performance Indicators
Lines of Business Agencies, Customers, Partners
Service Domains, Service Types Business and Service Components
Service Component Infrastructures, Interoperability Technologies, Recommendations
Business-focused Data Standardization Cross-Agency Information Exchanges
For EA modeling, we use the SRM as a bridge between the business aspects on the top half and technical features of the bottom half of the FEA.
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 8
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
ELEMENTS OF AN APPROACH FOR MODELING
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 9
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Goals of our Approach to Modeling SOA
1. Depict both IT and business service components, and the relationships and dependencies between them
2. Resolve ambiguities of SOA terminology to accommodate both the CPIC-level (investment/architecture) view of SOA, and the developer’s IT view (e.g., J2EE)
3. Make choices of how deep to go in developing SOA models– Find the right breakpoint between EA modeling and SLC-
level IT development– Make modeling choices based on the expect use of the
model
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 10
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business Problems to be Solved#1. SOA Spans Layers of Architecture
Technology
Applications/Services
Data
SOAModeling
InformationTechnology
Business
Goals
Business
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 11
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business Problems to be Solved#1. SOA Spans Layers of Architecture (cont’d)
JSP, Java, XML
Web Feature Services
ArcXML
Client SideClient Side
Data StorageData Storage
Server SideServer Side
LegendMAP Report/
GTSTools
Oracle AS
ArcIMS Java Connector
ArcIMS Server
Geospatial Portlet
EPA Portal
OracleOracleSDE Layers
Spatial Data Objects (SDO)
WME-User, SPCEIWI
Other Schemash
ttp
/tc
ph
ttp
Metacarta(GeoText
Search)Server
http
SOAP
Map Services
EPA Web ServicesFramework
Web Map Services
Feature Servers(Terra, FEMA,
Geography Network,NWIS.. etc.,)
Feature Servers(Terra, FEMA,
Geography Network,NWIS.. etc.,)
http/tcp
SOAP
SOAP
SOAP
ArcIMS Java Connector
Web Map Services
ArcIMS Java Connector
Web Map Services
Metacarta(GeoText
Search)Server
Metacarta(GeoText
Search)Server
SDE Layers
Spatial Data Objects (SDO)
WME-User, SPCEIWI
Other Schemas
SDE Layers
Spatial Data Objects (SDO)
WME-User, SPCEIWI
Other Schemas
Tec
hn
olo
gy
Ap
plic
atio
ns
Dat
aB
usi
nes
s
Components in a developer’s logical presentation include components that FEA maps to different layers of the architecture
In a modeling tool such as Metis™, this implies the need for a wide range of different service component objects, each particular to an architecture level
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 12
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business Problems to be Solved#2. CPIC and Developer SOA Views Differ
3. Service Reference Model (SRM) Table:
I dentify the service components funded by this major I T investment (e.g., knowledge management, content management, customer relationship management, etc.). Provide this
information in the format of the following table. For detailed guidance regarding components, please refer to http:/ / www.whitehouse.gov/ omb/ egov/ .
Agency Component
Name
Agency Component Description
Service Domain
FEA SRM Service Type
FEA SRM Component
FEA Service Component
Reused Name
FEA Service Component Reused UPI
I nternal or
External Reuse?
BY Funding Percentage
Enterprise Geospatial Services
Consumable and/or reusable geospatial services: vector and raster data; geoprocessing, geocoding, spatial tag and query, analytical services.
Back Office Services
Data Management
Data Exchange
Data Exchange
020-00-01-16-01-6005-00-404-142
Internal 1
Enterprise Geospatial Services
Consumable and/or reusable geospatial services: vector and raster data; geoprocessing, geocoding, spatial tag and query, analytical services.
Business Analytical Services
Visualization Imagery No Reuse 1
JSP, Java, XML
Web Feature Services
ArcXML
Client SideClient Side
Data StorageData Storage
Server SideServer Side
LegendMAP Report/
GTSTools
Oracle AS
ArcIMS Java Connector
ArcIMS Server
Geospatial Portlet
EPA Portal
OracleOracleSDE Layers
Spatial Data Objects (SDO)
WME-User, SPCEIWI
Other Schemas
htt
p/t
cph
ttp
Metacarta(GeoText
Search)Server
http
SOAP
Map Services
EPA Web ServicesFramework
Web Map Services
Feature Servers(Terra, FEMA,
Geography Network,NWIS.. etc.,)
Feature Servers(Terra, FEMA,
Geography Network,NWIS.. etc.,)
http/tcp
SOAP
SOAP
SOAP
Developer’s View of SOA Geospatial Visualization
CPIC View of SOA Geospatial Visualization
CPIC and other investment- or management-level views of services tend to be general and loosely defined
The developer’s view is analytic and logical, usually disaggregated and technical
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 13
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Problems to be Solved#3. Services are Built from Multiple Components
EPA Portal: Component View
Source: Lockheed Martin
Granularity becomes a problem: how can we represent levels of granularity within a single object?
A single object needs to represent the highest level of the service – the service to which all other components are aggregated
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 14
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business SRA’s Approach for EA Modeling Using the SRM
Basic concept: Separate “component-ness” from “service.”
Component Granularity Service Definition
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 15
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business SRA’s Approach for EA Modeling Using the SRM
Basic concept: Separate “component-ness” from “service.”
Component Granularity Service DefinitionPotential IT Exhibit 300s
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 16
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Definitions of “Component-ness”
SRM Definition
– “self-contained with predetermined functionality”
– “exposed through a business or technology interface”
As elaborated in “Service Component-Based Architectures” V 2.0, components are– Encapsulated– Consumable– Extensible– Standards-based– Well-documented– Follow industry best-
practices– Provide a cohesive set of
services– Have well-defined license
or service level agreement
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 17
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business The SRM’s Definition of Components, Annotated for Modeling
Level Definition Our Modeling Perspective
Distributed Component
The lowest level of component granularity. It is a software element that can be called at run-time with a clear interface and a clear separation between interface and implementation. It is autonomously deployable. [Normally not expressed as an IT 300 exhibit. A distributed component provides low ROI for capital planning purposes.]
May be distributed, but doesn’t need to be. In our modeling, DCs are always IT elements, but they don’t need to be software elements. A DC could be a server, or a LAN, or some other low-level component called be a higher-level component or by another DC.
Business Component
Represents the implementation of an autonomous business concept or business process. It consists of all the technology elements (i.e., software, hardware, data) necessary to express, implement, and deploy a given business concept as an autonomous, reusable element of a large information system. It is a unifying concept across the development lifecycle and the distribution tiers.[Normally not expressed as an IT 300 exhibit, but as a sub-component of a larger business component system.]
BCs tend to represent simple IT systems. So far we have not found the need to include business processes as components within BCs. BCs are composed of other elements, but these elements do not necessarily have to be all DCs, or even include DCs.
[addenda to definition from Service Components-Based Architecture Version 2.0]
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 18
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business The SRM’s Definition of Components, Annotated for Modeling
Level Definition Modeling Perspective
Business Component Systems
A set of cooperating business components assembled together to deliver a solution to a business problem.[Can be expressed as an IT 300 exhibit.]
BCS can be complex IT systems, composed of multiple BCs, and in our experience they can often include business processes. Examples of BCSs that include business processes include EPA’s current Geospatial Services Ex. 300 and its previous Program Management Office Ex. 300.
Federated Component
A set of cooperating system-level components federated to resolve the business need of multiple end users often belonging to different organizations.
We have not encountered any FCs at EPA, but examples include USDA’s Payroll System, FEMA Mac,
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 19
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business The SRM’s Definition of Components, Annotated for Modeling (cont’d)
Level Examples Modeling Perspective
Business Component Systems
A set of cooperating business components assembled together to deliver a solution to a business problem.[Can be expressed as an IT 300 exhibit.]
BCS can be complex IT systems, composed of multiple BCs, and in our experience they can often include business processes. Examples of BCSs that include business processes include EPA’s current Geospatial Services Ex. 300 and its previous Program Management Office Ex. 300.
Federated Component
A set of cooperating system-level components federated to resolve the business need of multiple end users often belonging to different organizations.
A federated component includes numerous Business Component Systems exposed as an integrated service across the government to multiple end-users in different organizations. We have not encountered any FCs at EPA, but examples include USDA’s payroll service, FEMA Mapping Analysis Center.
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 20
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Metis™ Modeling Basics
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 21
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Basics of Modeling with Metis
The metamodel provides support for all EA information that could potentially be represented in an agency model to support a wide variety of uses.
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 22
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
The metamodel defines a set of objects, their properties and the allowable relationships between those objects.
All relationships in the metamodel
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 23
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Basics of Metis metamodeling
Each Object represents an element of the
architecture
Ap
plic
-at
ion
CDX
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 24
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Basics of Metis metamodeling
Each Object represents an element of the
architecture
Label provides object type, color indicates level of architecture
Ap
plic
-at
ion
CDX
Title identifies particular element name, such as name of application or system
Object properties can contain any number of attributes for the object type and the specific element represented
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 25
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Basics of Metis metamodeling
Ap
p
Mo
du
leArchive Manager
Each Object represents an element of the
architecture
Label provides object type, color indicates level of architecture
Ap
plic
-at
ion
CDX
Title identifies particular element name, such as name of application or system
Object properties can contain any number of attributes for the object type and the specific element represented
All other objects are modeled similarly
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 26
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Basics of Metis metamodeling
Ap
p
Mo
du
leArchive Manager
Ap
plic
-at
ion
CDX
All objects should be connected by one or
more relationships
Each Object represents an element of the
architecture
Label provides object type, color indicates level of architecture
Title identifies particular element name, such as name of application or system
Object properties can contain any number of attributes for the object type and the specific element represented
All other objects are modeled similarly
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 27
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
Basics of Metis metamodeling
Ap
p
Mo
du
leArchive Manager
Ap
plic
-at
ion
CDX
All objects should be connected by one or
more relationships
Relationships are directional and described by verbs
Aggregates to
Aggregates
Each Object represents an element of the
architecture
Label provides object type, color indicates level of architecture
Title identifies particular element name, such as name of application or system
Object properties can contain any number of attributes for the object type and the specific element represented
All other objects are modeled similarly
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 28
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business Mapping to the Service Component Reference Model
Architecture Elements FEA SRM, Extended
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
ServicesProvided
SR
M SRM Domain
SR
M SRMType
SR
M SRMComponent
SR
M “Agency” Service”
Application Layer Objects
Data Layer Objects
Business Layer Objects
Technology Layer Objects
Bu
sin
ess
Dat
aA
ppl
ica-
tions
Tec
hno-
logy
Any object in the model may be connected to any SRM service
SRM Domains and Service Types areinherited by the lowest service level
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 29
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business Mapping to the Service Component Reference Model
Architecture Elements FEA SRM, Extended
Any object in the model may be connected to any SRM service
SRM Domains and Service Types areinherited by the lowest service level applicable;for BCSs, this may be at the Type level
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
ServicesProvided
SR
M SRM Domain
SR
M SRMType
SR
M SRMComponent
SR
M “Agency” Service
Application Layer Objects
Data Layer Objects
Business Layer Objects
Technology Layer Objects
Bu
sin
ess
Dat
aA
ppl
ica-
tions
Tec
hno-
logy
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 30
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business Mapping to the Service Component Reference Model
Architecture Elements FEA SRM, Extended
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
ServicesProvided
SR
M SRM Domain
SR
M SRMType
SR
M SRMComponent
SR
M “Agency” Service
Application Layer Objects
Data Layer Objects
Business Layer Objects
Technology Layer Objects
Bu
sin
ess
Dat
aA
ppl
ica-
tions
Tec
hno-
logy
Objects in the Business Layermap only to FCs and BCSs.Objects in the Data, Application,and Technology Layers map to BCSs, BCs, and DCs.
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 31
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
EXAMPLES
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 32
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business Portal Proposed Solution – component view
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 33
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
EPA Records Management System(Enterprise Content Management System ECMS)
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Ap
plic
-at
ion
ECMS
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 34
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
EPA Records Management System(Enterprise Content Management System ECMS)
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Ap
plic
-at
ion
ECMS
Service “Components”
SR
M Digital Asset Services
SR
M Records Management
SR
M SRM Component
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 35
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
EPA Records Management System(Enterprise Content Management System ECMS)
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Ap
plic
-at
ion
ECMS
Ap
p
Mo
du
le
Indexing Services
Ap
p
Mo
du
le User Access Management A
pp
M
od
ule User Identity
ManagementAp
p
Mo
du
le
Metadata Services
Ap
p
Mo
du
le
Content Services
Service “Components”
SR
M Digital Asset Services
SR
M Records Management
SR
M SRM Component
SR
M EPA Component
Service “Components”
SR
M Support Services
SR
M Security Management
SR
M Identification Authorization
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 36
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
EPA Records Management System(Enterprise Content Management System ECMS)
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Ap
pli
c-a
tio
n
ECMS
Ap
p
Mo
du
le
Indexing Services
Ap
p
Mo
du
le User Access Management A
pp
M
od
ule User Identity
ManagementAp
p
Mo
du
le
Metadata Services
Ap
p
Mo
du
le
Content Services
Ap
p
Mo
du
le Full-text Indexing ServicesA
pp
M
od
ule
Web Services
Ap
p
Mo
du
le Service-based Objects
Ap
p
Mo
du
le Documentum Docapps
Ap
p
Mo
du
le Content Transfer Component A
pp
M
od
ule
Workflow Services
Ap
p
Mo
du
le
Lifecycle Services
Ap
p
Mo
du
le Authentication Services
Ap
p
Mo
du
le Authorization Services
Ap
p
Mo
du
le User Password Management
Services
Ap
p
Mo
du
le User, Group, and Organization Management
Ap
p
Mo
du
le
Scanning Services
Ap
p
Mo
du
le Records Management
Services
Ap
p
Mo
du
le
Auditing Services
Ap
p
Mo
du
le
Single Sign-on
Ap
p
Mo
du
le LDAP Synchronization
Service “Components”
SR
M Digital Asset Services
SR
M Records Management
SR
M SRM Component
SR
M EPA Component
Service “Components”
SR
M Support Services
SR
M Security Management
SR
M Identification Authorization
SR
M EPA Component
Service “Components”
SR
M Support Services
SR
M Security Management
SR
M Identification Authorization
SR
M
Password Management
Services
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 37
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
EPA Portal
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Ap
plic
-at
ion
EPA Portal
Service “Components”
SR
M Digital Asset Services
SR
M Knowledge Management
SR
M Information Sharing
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 38
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
EPA Portal
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Ap
plic
-at
ion
EPA Portal
Ap
p
Mo
du
le User Access Management A
pp
M
od
ule
Report Generator
Ap
p
Mo
du
le Multi-Lingual Support A
pp
M
od
ule Interoperability
& Integration Support
Ap
p
Mo
du
le
Collaboration Ap
p
Mo
du
le
Omni Portlet Ap
p
Mo
du
le Security Management/
Protection
Ap
p
Mo
du
le User Identity Management A
pp
M
od
ule
Self Service
Service “Components”
SR
M Digital Asset Services
SR
M Knowledge Management
SR
M Information Sharing
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 39
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
EPA Portal
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Portal Communities
Ap
plic
-a
tio
n
EPA Portal
Ap
p
Mo
du
le User Access Management A
pp
M
od
ule
Report Generator
Ap
p
Mo
du
le Multi-Lingual Support A
pp
M
od
ule Interoperability
& Integration Support
Ap
p
Mo
du
le
Collaboration Ap
p
Mo
du
le
Omni Portlet Ap
p
Mo
du
le Security Management/
Protection
Ap
p
Mo
du
le User Identity Management A
pp
M
od
ule
Self Service
Ap
plic
-a
tio
n Environmental Scientist Portal
Ap
plic
-a
tio
n
Geodata Gateway
Ap
plic
-a
tio
n Administrative Services Portal
Ap
plic
-a
tio
n
Air Portal
Ap
plic
-a
tio
n
Water Portal
Ap
plic
-a
tio
n
Community n...
Service “Components”
SR
M Digital Asset Services
SR
M Knowledge Management
SR
M Information Sharing
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 40
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
EPA Portal
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Portal Communities
Ap
pli
c-
ati
on
EPA Portal
Ap
p
Mo
du
le User Access Management A
pp
M
od
ule
Report Generator
Ap
p
Mo
du
le Multi-Lingual Support A
pp
M
od
ule Interoperability
& Integration Support
Ap
p
Mo
du
le
Collaboration Ap
p
Mo
du
le
Omni Portlet Ap
p
Mo
du
le Security Management/
Protection
Ap
p
Mo
du
le User Identity Management A
pp
M
od
ule
Self Service
Ap
pli
c-a
tio
n Environmental Scientist Portal
Ap
pli
c-
ati
on
Geodata Gateway
Ap
pli
c-
ati
on Administrative
Services Portal
Ap
pli
c-a
tio
n
Air Portal
Ap
pli
c-
ati
on
Water Portal
Ap
pli
c-
ati
on
Community n...
Service “Components”
SR
M Digital Asset Services
SR
M Knowledge Management
SR
M Information Sharing
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 41
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
EPA Portal
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Portal Communities
Ap
plic
-at
ion
EPA Portal
Ap
p
Mo
du
le User Access Management A
pp
M
od
ule
Report Generator
Ap
p
Mo
du
le Multi-Lingual Support A
pp
M
od
ule Interoperability
& Integration Support
Ap
p
Mo
du
le
Collaboration Ap
p
Mo
du
le
Omni Portlet Ap
p
Mo
du
le Security Management/
Protection
Ap
p
Mo
du
le User Identity Management A
pp
M
od
ule
Self Service
Ap
plic
-at
ion Environmental
Scientist Portal
Ap
plic
-at
ion
Geodata Gateway
Ap
p
Mo
du
le
ESRI Module A
Ap
p
Mo
du
le
ESRI Module B
Ap
plic
-at
ion Administrative
Services Portal
Ap
plic
-at
ion
Air Portal
Ap
plic
-at
ion
Water Portal
Ap
plic
-at
ion
Community n...
Service “Components”
SR
M Digital Asset Services
SR
M Knowledge Management
SR
M Information Sharing
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 42
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
EPA Portal
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Portal Communities
Ap
pli
c-
ati
on
EPA Portal
Ap
p
Mo
du
le User Access Management A
pp
M
od
ule
Report Generator
Ap
p
Mo
du
le Multi-Lingual Support A
pp
M
od
ule Interoperability
& Integration Support
Ap
p
Mo
du
le
Collaboration Ap
p
Mo
du
le
Omni Portlet Ap
p
Mo
du
le Security Management/
Protection
Ap
p
Mo
du
le User Identity Management A
pp
M
od
ule
Self Service
Ap
p
Mo
du
le Authorization Service
Ap
p
Mo
du
le Access Control Provisioning
Service
Ap
p
Mo
du
le Register for Portal/Community
Access
Ap
p
Mo
du
le Subscribe to a User Community
Ap
p
Mo
du
le Unsubscribe to a User Community
Ap
p
Mo
du
le Personalization Service
Ap
p
Mo
du
le User Provisioning Service
Ap
p
Mo
du
le User Credentials Service
Ap
p
Mo
du
le Single Sign-on Service
Ap
p
Mo
du
le Reduced Sign-on Service
Ap
p
Mo
du
le Charting Omni-Portlet
Ap
p
Mo
du
le Report Omni-Portlet
Ap
p
Mo
du
le
Language Strings
Ap
p
Mo
du
le International-ization Services
Ap
p
Mo
du
le Web Services for Remote Portlets
Ap
p
Mo
du
le
Web Clipping
Ap
p
Mo
du
le
Workspaces
Ap
p
Mo
du
le
Content Services
Ap
p
Mo
du
le Discussion Services
Ap
p
Mo
du
le
Calendar Services
Ap
p
Mo
du
le
Search ServicesA
pp
M
od
ule
XML Viewer
Ap
p
Mo
du
le
Web Service
Ap
p
Mo
du
le
SQL
Ap
p
Mo
du
le Fixed and Delimited Format
Ap
p
Mo
du
le
URL
Ap
p
Mo
du
le Cross Site Scripting
Ap
p
Mo
du
le SQL Injection Services
Ap
p
Mo
du
le
Custom Filters
Ap
pli
c-
ati
on Environmental
Scientist Portal
Ap
pli
c-
ati
on
Geodata Gateway
Ap
p
Mo
du
le
ESRI Module A
Ap
p
Mo
du
le
ESRI Module B
Ap
pli
c-
ati
on Administrative
Services Portal
Ap
pli
c-
ati
on
Air Portal
Ap
pli
c-
ati
on
Water Portal
Ap
pli
c-
ati
on
Community n...
Service “Components”
SR
M Digital Asset Services
SR
M Knowledge Management
SR
M Information Sharing
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 43
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business EPA CDXProblem of Adding Manual Processes
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Ap
plic
-at
ion
CDX
Service “Components”
SR
M Back Office Services
SR
M Data Management
SR
M Data Exchange
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 44
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business EPA CDXProblem of Adding Manual Processes
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Ap
plic
-at
ion
CDX
Ap
p
Mo
du
le Homepage Manager A
pp
M
od
ule
Archive Manager
Ap
p
Mo
du
le Registration/ Authentication A
pp
M
od
ule
E-Mail Service
CORE CDX SERVICES
Dat
abas
e
CDX Archive
Ser
vice
Exchange Network Web
Service Ser
vice CDX Web
Service 2 Ser
vice CDX Web
Service 3 Ser
vice CDX Web
Service 4 Ser
vice CDX Web
Service 5 Ser
vice CDX Web
Service 6 Ser
vice CDX Web
Service 7 Ser
vice CDX Web
Service 8 Ser
vice CDX Web
Service 9
Service “Components”
SR
M Back Office Services
SR
M Data Management
SR
M Data Exchange
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 45
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business EPA CDXProblem of Adding Manual Processes
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Ap
plic
-at
ion
CDX
Ap
p
Mo
du
le Homepage Manager A
pp
M
od
ule
Archive Manager
Ap
p
Mo
du
le TRI Workflow ManagerA
pp
M
od
ule Registration/
Authentication Ap
p
Mo
du
le
E-Mail Service
CORE CDX SERVICES
Partners
Pa
rtn
er
Org TRI Reporting
Organization
Pa
rtn
er
Ap
p
TRI-ME
Pa
rtn
er
Ro
le TRI Certifying Official
Ap
p E
xch
P
kg Form R Flat File
Dat
ab
ase
CDX Archive
Ap
p E
xch
P
kg Paper Form R
Ap
p E
xch
P
kg Form R Paper
Certification
Ap
p E
xch
P
kg Media-Based Form
R
Bu
s P
ro
Ex
ch P
kg
Letter
Pa
rtn
er
Org
.
States
Se
rvic
e Exchange Network Web
Service Se
rvic
e CDX Web Service 2 S
erv
ice CDX Web
Service 3 Se
rvic
e CDX Web Service 4 S
erv
ice CDX Web
Service 5 Se
rvic
e CDX Web Service 6 S
erv
ice CDX Web
Service 7 Se
rvic
e CDX Web Service 8 S
erv
ice CDX Web
Service 9
Flow-Specific CDX Components
Ap
p
Mo
du
le
TRI Registration
Ap
p
Mo
du
le TRI XML Data Transformation
Ap
p
Mo
du
le TRI XML Data Validation
Ap
p
Mo
du
le TRI Data Certification
Service “Components”
SR
M Back Office Services
SR
M Data Management
SR
M Data Exchange
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 46
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business EPA CDXProblem of Adding Manual Processes
Ap
p
Mo
du
le TRI Workflow Manager
Partners
Pa
rtn
er
Org TRI Reporting
Organization
Pa
rtn
er
Ap
p
TRI-ME
Pa
rtn
er
Ro
le TRI Certifying Official
Ap
p E
xch
P
kg Form R Flat File
Ap
p E
xch
P
kg Paper Form R
Ap
p E
xch
P
kg Form R Paper
Certification
Ap
p E
xch
P
kg Media-Based Form
R
Bu
s P
ro
Ex
ch P
kg
Letter
Pa
rtn
er
Org
.
States
Flow-Specific CDX Components
Ap
p
Mo
du
le
TRI Registration
Ap
p
Mo
du
le TRI XML Data Transformation
Ap
p
Mo
du
le TRI XML Data Validation
Ap
p
Mo
du
le TRI Data Certification
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 47
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business EPA CDXProblem of Adding Manual Processes
Ap
p
Mo
du
le TRI Workflow Manager
Partners
Pa
rtn
er
Org TRI Reporting
Organization
Pa
rtn
er
Ap
p
TRI-ME
Pa
rtn
er
Ro
le TRI Certifying Official
Ap
p E
xch
P
kg Form R Flat File
Ap
p E
xch
P
kg Paper Form R
Ap
p E
xch
P
kg Form R Paper
Certification
Ap
p E
xch
P
kg Media-Based Form
R
Bu
s P
ro
Ex
ch P
kg
Letter
Pa
rtn
er
Org
.
States
Flow-Specific CDX Components
Ap
p
Mo
du
le
TRI Registration
Ap
p
Mo
du
le TRI XML Data Transformation
Ap
p
Mo
du
le TRI XML Data Validation
Ap
p
Mo
du
le TRI Data Certification
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 48
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business EPA CDXProblem of Adding Manual Processes
Electronic Facility Data Profile System
TRI Staging Support System
TRI Reporting Center Processes (detail)
Partners
Par
tne
r O
rg TRI Reporting Organization
Par
tne
r A
pp
TRI-ME
Par
tne
r R
ole TRI Certifying
Official
Ap
p E
xch
P
kg Form R Flat File
Dat
abas
e
TRI Staging Database A
pp
M
od
ule Form R Data
Entry
Ap
p
Mo
du
le Compliance Validation
Bu
sin
ess
Pro
ces
s
Catalog
Bu
sin
ess
Pro
ces
s Initial QA(Completeness, Reconciliation)
Bu
sin
ess
Pro
ces
s
System Entry
Bu
sin
ess
Pro
ces
s
Technical QA
Ap
plic
-at
ion
FRS
Dat
abas
e
EFDP Database
Ap
plic
-at
ion
EFDP Manager
Ap
plic
-at
ion
EFDP Web Site
Ap
p E
xch
P
kg Paper Form R
Ap
p E
xch
P
kg
Form R Paper Certification
Ap
p E
xch
P
kg
Media-Based Form R
Ap
p E
xch
P
kg
Notice of Significant Error
(NOSE)
Bu
s P
ro
Exc
h P
kg
Letter
Ap
p E
xch
P
kg
Notice of Noncompliance
(NON)
Ap
plic
-at
ion
TRIS
Par
tne
r O
rg.
States
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 49
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business EPA CDXProblem of Adding Manual Processes
TRI Staging Support System
TRI Reporting Center Processes (detail)
Da
tab
as
e
TRI Staging Database A
pp
M
od
ule Form R Data
Entry
Ap
p
Mo
du
le Compliance Validation
Bu
sin
es
s
Pro
ce
ss
Catalog
Bu
sin
es
s
Pro
ce
ss Initial QA
(Completeness, Reconciliation)
Bu
sin
es
s
Pro
ce
ss
System Entry
Bu
sin
es
s
Pro
ce
ss
Technical QA
Ap
pli
c-
ati
on
FRS
Ap
pli
c-
ati
on
TRIS
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Service “Components”
SR
M Back Office Services
SR
M Data Management
SR
M Data Warehouse
SR
M EPA Component
Service “Components”
SR
M Back Office Services
SR
M Data Management
SR
M Data Cleansing
SR
M EPA Component
Service “Components”
SR
M Digital Asset Services
SR
M Document Management
SR
M indexing
SR
M EPA Component
Service “Components”
SR
M Back Office Services
SR
M Data Management
SR
M Loading & Archiving
SR
M EPA Component
Approaches for Modeling SOAs within Existing Architecture Tools and Reference Models 50
Technology
Applications/Services
Data
Business
Goals
InformationTechnology
Business
CDX Flow-Specific ElementsShared Elements
EPA CDXProblem of Adding Manual Processes
Electronic Facility Data Profile System
TRI Staging Support System
TRI Reporting Center Processes (detail)
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Ap
pli
c-
ati
on
CDX
Ap
p
Mo
du
le Homepage Manager A
pp
M
od
ule
Archive Manager
Ap
p
Mo
du
le TRI Workflow ManagerA
pp
M
od
ule Registration/
Authentication Ap
p
Mo
du
le
E-Mail Service
CORE CDX SERVICES
Partners
Pa
rtn
er
Org TRI Reporting
Organization
Pa
rtn
er
Ap
p
TRI-ME
Pa
rtn
er
Ro
le TRI Certifying Official
Ap
p E
xc
h
Pk
g Form R Flat File
Da
tab
as
e
TRI Staging Database A
pp
M
od
ule Form R Data
Entry
Ap
p
Mo
du
le Compliance Validation
Bu
sin
es
s
Pro
ce
ss
Catalog
Bu
sin
es
s
Pro
ce
ss Initial QA
(Completeness, Reconciliation)
Bu
sin
es
s
Pro
ce
ss
System Entry
Bu
sin
es
s
Pro
ce
ss
Technical QA
Ap
pli
c-
ati
on
FRS
Ap
pli
c-
ati
on
TRIS
Da
tab
as
e
CDX Archive
Da
tab
as
e
EFDP Database
Ap
pli
c-a
tio
n
EFDP Manager
Ap
pli
c-a
tio
n
EFDP Web Site
Ap
p E
xc
h
Pk
g Paper Form R
Ap
p E
xc
h
Pk
g Form R Paper Certification
Ap
p E
xc
h
Pk
g Media-Based Form R
Ap
p E
xc
h
Pk
g
Notice of Significant Error
(NOSE)
Bu
s P
ro
Ex
ch
Pk
g
Letter
Ap
p E
xc
h
Pk
g
Notice of Noncompliance
(NON)
Ap
pli
c-a
tio
n
TRIS
Pa
rtn
er
Org
.
States
Se
rvic
e Exchange Network Web
Service Se
rvic
e
CDX Web Service 2 S
erv
ice
CDX Web Service 3 S
erv
ice
CDX Web Service 4 S
erv
ice
CDX Web Service 5 S
erv
ice
CDX Web Service 6 S
erv
ice
CDX Web Service 7 S
erv
ice
CDX Web Service 8 S
erv
ice
CDX Web Service 9
Flow-Specific CDX Components
Ap
p
Mo
du
le
TRI Registration
Ap
p
Mo
du
le TRI XML Data Transformation
Ap
p
Mo
du
le TRI XML Data Validation
Ap
p
Mo
du
le TRI Data Certification
FEA Service Component Reference Model
Component Granularity
SR
M Federated Component
SR
M Bus. Comp. System
SR
M Business Component
SR
M Distributed Component
Service “Components”
SR
M SRM Domain
SR
M SRM Type
SR
M SRM Component
SR
M EPA Component
Service “Components”
SR
M Back Office Services
SR
M Data Management
SR
M Data Exchange
SR
M EPA Component
We will have to model 22 separate flows in use now, with an additional 15 or so scheduled for FY 2007