1 / 12

Service Component Registry and Repository (SCRR)

Service Component Registry and Repository (SCRR). April 26, 2007. Lico Galindo. 2007 Exchange Network National Meeting. Service Oriented Architecture. It’s about services and components It’s about re-use. To use and re-use Know the services and components exist

adonis
Download Presentation

Service Component Registry and Repository (SCRR)

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. Service Component Registry and Repository (SCRR) April 26, 2007 Lico Galindo 2007 Exchange Network National Meeting

  2. Service Oriented Architecture • It’s about services and components • It’s about re-use To use and re-use • Know the services and components exist • Be able to find services and components

  3. Stakeholders • EPA Developers • Developers in States and Tribes • Architects supporting Architectural Review process • Architects monitoring for life cycle conformance to architecture

  4. Types of Services and Components • Web Services • Reusable software designs and Templates • Metadata and Data Services • XML Data Flows • Style Sheets • Data Models (conceptual, logical and physical) • Reusable pieces of code, in various languages • Development Models and guidance, like the Core Reference Model (CRM) • Other types

  5. Existing Solutions • UDDI Registries (web services) • ENDS (metadata registry and data services) • XML Registry (XML Schema and XML shared Components) • Core.gov

  6. Challenges Problems building a Solution • Finding components of different types • Components and Services are heterogeneous – single solution is hard • Few tools available Problems finding services and components • In Registries and Repositories • In Registry, no Repository • No Registry, no Repository

  7. SCRR Scope New Development S C R R Existing Component Registry New Registry New Registry Existing Repository Existing Repository New Repository Existing

  8. Vision for Final Product • Links and Interfaces to currently existing registries and repositories • Links to new registries and their repositories • Links to new registries and their new repositories • Built in modules according to EPA and Exchange Network Stakeholder’s priorities

  9. SCRR Suite S C R R Geodata Tool link EPA/EN UDDI Data Models Repository Reusable Programming code Repository Style Sheets Registry + Repository Metadata And data Services (ENDS) Other UDDI XMLSchema And schema Component repository Reusable Software Design Repository Development Models And CRM Existing New

  10. Proposed SCRR Activities Vision and Scope Requirements Implementation Options • Identify Stakeholders • Define vision, business objectives and desired outcome • Identify constraints and possible barriers • Define scope • Draft Vision and Scope document • Final Vision and Scope document • Identify and prioritize sub-components • Identify and integrate Agency regulations and standards • Define requirements • Prioritize requirements • Tool evaluation • Iterative development of requirements • Draft Requirements document • Final Requirements document • Outline implementation options using defined requirements, constraints, etc. (e.g., use of a COTS tool, enhancement of an existing tool) • Draft Implementation Options • Final Implementation Options Facilitated JAD Sessions, Targeted Interviews & Research Continual Communication with ENLC and NOB and EPA EA Team Project Management and Outreach • Prepare project plan and schedule (iterative) • Define and Execute Stakeholder Outreach Strategy • Issue and Risk Management

  11. Tentative Schedule Finalize contract With Requirements Engineer Define Vision And scope Requirements gathering And analysis Tool Evaluation April 30 May 31 June 30 July 31 Aug 31 Sept 30

  12. Vision of Success • Ease of Discovery and Re-use of Components and Services • Efficiency and Lower Cost of Applications • Timeliness in System Development • Quality

More Related