# Presentation: 660517

## 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 Office
- May 17, 2006
- Sol Safran, PRIME Enterprise Data Management

## 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 formats

- 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 formats

- Adapted 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

**Notes:**
The IRS is building a framework where XML will be the standard for data exchange.

## 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

- 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

## Target

- Applications

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

- Messages

- Components
- (aggregated
-  terms)

- Terms

- This 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.

## 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

- 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

## Reviewed IRS efforts
Alternatives Analysis
Metadata Repository
MeF, CADE, E-Services
Reviewed Federal Agencies
Federal Registry
DOE/FSA
DOD
DHS/Global Justice

- 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

## 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

- 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

## ebXML Registry Architecture

- ebXML Registry Architecture

## Registry Java UI

## ObjectType ClassificationScheme

-  Defines type of information stored in the registry
-  Allows registry customization for IRS-specific assets
-  We defined IRS XML components

## AssociationType ClassificationScheme

-  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

## SubjectRole ClassificationScheme

-  Defines registry user roles
-  Enables governance and fine-grained access control policy and authorization
-  We defined IRS-specific roles

## StatusType ClassificationScheme

-  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

## Find ComplexType By Name

## Browse ComplexType

-  Enables focused, encapsulated view of artifacts
-  Enables exploration of relationships and dependencies between artifacts
-  Reduces research and analysis time

## Export ComplexType to ZIP File

## Export ComplexType to ZIP File

**Message**

**Aggregate**
**Component**

**Basic**
**Component**

**Specialized**
**Datatype**

**Requires**

**Assembly of**

**Assembly of**

**\Messages.xsd**

**\AggregateComponents.xsd**

**\BasicComponents.xsd**

**\SpecialzedDataTypes.xsd**

_**Components**_

_**Where Stored**_

- Organized within a folder structure by ‘namespace’

_**Implemented as**_

## Content of Exported ZIP File

## Impact Analysis: Changing Type

## 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

- 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

## Contact

- 		 _[John.A.Triplett@IRS.Gov](mailto:John.A.Triplett@IRS.Gov)_
- 		 202.283.3380
- Sol Safran	 Prime Enterprise Data Management (EDM)
- 		 _[Sol.Safran@IRS.Gov](mailto:Sol.Safran@IRS.Gov)_
- 		 301.731.7543