1 / 16

January 10, 2008

Reusable Component Services (RCS) (formerly Service Component Registry and Repository/SCRR ) Presentation to the Enterprise Architecture Work Group (EAWG). January 10, 2008. Lico Galindo, Data Standards Branch, OIC. Purpose of this presentation. Raise awareness of RCS in the EA community

tilly
Download Presentation

January 10, 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Reusable Component Services (RCS)(formerly Service Component Registry and Repository/SCRR)Presentation to the Enterprise Architecture Work Group (EAWG) January 10, 2008 Lico Galindo, Data Standards Branch, OIC

  2. Purpose of this presentation • Raise awareness of RCS in the EA community • Give a status update on the RCS project • Request your continuous help, collaboration and support

  3. Motivation and Rationale for RCS • Customer Requests • Requests from the NOB • Replacement of the XML Registry • Web Services Catalog • Exchange Network Discovery Services (ENDS) in search of data registries

  4. Sponsorship • Data Standards Branch • Exchange Network (NOB, ECOS) • Central Data Exchange (CDX) • Part of OEI’s SOA Initiative • Looking for broader participation from the EA community • Looking for participation from the EPA program offices

  5. What we have done • Presentations to the NOB and Exchange Network National Conference • Presentations to the CDX and the Web Services Work Group • Vision workshop • Interviews • Preliminary requirements and priorities

  6. Purpose(as defined in July 24-25 workshop) The purpose of the SCRR is to provide a clearinghouse of information about components, services, technologies, and solutions in a collaborative workspace so that application and database development, and architecture are performed in an effective and efficient manner capitalizing on lessons learned from others and reuse of previous work

  7. What RCS is • Critical component of Service Oriented Architecture • Information about • Components • Services • Technologies • Solutions • Collaborative Catalog or Index of existing Registries • Vehicle for Sharing, Reuse • To maximize Effectiveness, Efficiency, Quality • To minimize Redundancy, Cost

  8. What SCRR is not • Replacement for existing registries or repositories • Not only for web services or XML schema

  9. Customers • Developers, Architects and Managers for • EPA Program Offices • EPA Regions • State Agencies • Tribes and Territories • Local Municipalities • Colleges and Universities • Other Federal Agencies • Contractors that support customers above

  10. Proposed Entries • Web Services • XML data flows and schema • Metadata/data services • Data Models • Best Practices • Templates • Geospatial components • Code sets • Other architectural components

  11. Functionality • Search and Discover • Subscribe • Catalog • Register and Publish • Govern and Administer • Secure • Collaborate • Help

  12. Priorities • Web Services Catalog – OEI SOA initiative • New XML Registry and Schema Workbench • Integration with Exchange Network Discovery Services (ENDS) • Data Models

  13. RCS in Support of Enterprise Architecture and Service Oriented Architecture • Registries and repositories for standard artifacts • Registries for web services and reusable components • Functionality that supports discovery, documentation and reuse

  14. RCS in Support of Application and Database Development • Registries and repositories templates, schema, code blocks, web services, best practices, etc. • Registries and repositories for data dictionaries, data models, data sets, code sets, etc. • Functionality that supports discovery, documentation and reuse

  15. Next Steps • Update for Vision Group (January 2008) • Requirements workshop for Web Services Catalog (February 2008) • Requirement workshops and interviews with EPA program offices and other key EPA stakeholders (starting January 2008) • Formal requirements for RCS and Web Services Catalog (April 2008) • Tool evaluation and selection for Web Services Catalog (May 2008) • Build and integration for Web Services Catalog (July 2008) • Requirement workshops and interviews with Exchange Network and EPA stakeholders, for new XML Registry and Schema Workbench • Formal requirements for new XML Registry (September 2008) • Tool Evaluation and selection for new XML Registry • Build and integration for new XML Registry • Work on other RCS priorities • Establishment of Governance Structure • Continued Outreach for Sponsorship, Funding and Support

More Related