irs component asset registry (xml registry/repository) prototype

1

IRS Component Asset Registry(XML Registry/Repository)

Prototype

Senior leaders must champion reuse by expecting that assets be reused, recognizing projects and individuals that successfully reuse assets or publish them, and by making reuse a priority.

- FEA Services and Components Based Architectures Version 3.5

Enterprise Data Management OfficeMay 17, 2006

Sol Safran, PRIME Enterprise Data Management

2

• Objective:– Identify the target state of XML technology implementation for the IRS– Assess and adopt appropriate standards, practices, and tools for the IRS and its trading

partners– Strategically transition current systems and legacy formats to modernized XML data exchange

formatsAdapted from a Department of Education, Federal Student Aid briefing. “XML: A Beginners Guide”Presented at the 2003 Electronic Access Conference in San Diego, CA.

IRS XML Framework

3

• MeF/CADE/E-Services– Common data requirements & all use XML– No common data components between them

• Triples the size of the IRS vocabulary

• Require custom interfaces

– XML (XSD, XSL, etc.) managed within each project release

• Vocabularies are project dependent– Cross project visibility does not exist

• Difficult to discover and reuse external project components

• Interfaces require significant transformation

Where We Are

4

Applications

Interfaces

(Services, API, GUI, batch, etc.)

Messages

Components

(aggregated

terms)

TermsThis is the controlled vocabulary. We aim to minimize, but not eliminate, terms outside of this universe.

These are the exchange messages as deployed by projects

These are the interfaces where the messages are deployed.

Each layer builds from shared components at the lower levels

These are common message fragments, such as address.

Target

5

• EDMO is tasked to build a common vocabulary for data exchange– Common data exchange components– XML service descriptions (WSDL)– ICD Process

• So that we can:– Do a good job at managing data exchange– Identify reusable interfaces/minimize redundancy– Compose interfaces from messages/components– Enhance interoperability/minimize transformations– Provide enterprise exposure to available

components– Assist projects using assets from previous projects– Reduce lifecycle costs for XML

development/maintenance

EDMO Goals

6

• Reviewed IRS efforts– Alternatives Analysis– Metadata Repository– MeF, CADE, E-Services

• Reviewed Federal Agencies– Federal Registry– DOE/FSA– DOD– DHS/Global Justice

• Reviewed Standards– ebXML RIM– UDDI

• Developed Concept– ConOps– Build vs. Buy

• Sun

• Other ebXML RIM

• Others

– End2End (EEP) Prototype

IRS Registry History

7

• Prototype Use Cases– UC 1 Initialization

• Populate with initial set of data• Complete

– UC 2 Development• Developer-based use case• Complete

– UC 3 Operations• Service-based use case • Finalizing

– UC 4 Reporting• BusinessObjects Integration use case• Finalizing

Registry Prototype Use Cases

8

ebXML Registry Architecture

9

Registry Java UI

10

• Defines type of information stored in the registry

• Allows registry customization for IRS-specific assets

• We defined IRS XML components

ObjectType ClassificationScheme

11

• Defines types of possible relationships between objects stored in the registry

• Allows registry customization for IRS-specific relationships

• We defined relationships between IRS XML components

AssociationType ClassificationScheme

12

• Defines registry user roles

• Enables governance and fine-grained access control policy and authorization

• We defined IRS-specific roles

SubjectRole ClassificationScheme

13

• Defines the types of registry artifact status

• Allows registry to be customized for IRS specific status and enables governance, notification and workflow

• We defined IRS-specific status

StatusType ClassificationScheme

14

Find ComplexType By Name

15

• Enables focused, encapsulated view of artifacts

• Enables exploration of relationships and dependencies between artifacts

• Reduces research and analysis time

Browse ComplexType

16

Export ComplexType to ZIP File

17

Message

AggregateComponent

BasicComponent

SpecializedDatatype

Requires

Assembly of

Assembly of

\Messages.xsd

\AggregateComponents.xsd

\BasicComponents.xsd

\SpecialzedDataTypes.xsd

Components Where Stored

Organized within a folder structure by ‘namespace’

Export ComplexType to ZIP File

Implemented as

18

Content of Exported ZIP File

19

Impact Analysis: Changing Type

20

• Prototype - 30 May Completion• Decision Point for Extended Prototype

– Not acquisition– In IRS infrastructure; up to 1 Year– Add IRS requirements incrementally

• Governance– Initiated contract support– Implement with extended prototype– Integrate QOD

Next Steps

21

John Triplett Enterprise Data Management Office (EDMO) John.A.Triplett@IRS.Gov 202.283.3380

Sol Safran Prime Enterprise Data Management (EDM) Sol.Safran@IRS.Gov 301.731.7543

Contact