1. Terminology Reference System Vision Linda Spencer OEI/OIC Data Standards Branch Denzel Carrico Lockheed Martin Inc

2. Registry of EPA Applications and Databases (READ) Data Element Concepts, Value Meanings Environmental Data Registry (EDR) Data Dictionaries Thesauri Classification Schemes (Taxonomies) Terminology Reference System (TRS) System Ontologies Data Models Permissible Value Lists Business Area Ontologies Data Element Names and Definitions Controlled Vocabularies Data Standards Terms System Inventory White– Current Capability Red – Future Capability and Relationships System of Registries Semantic Vision

3. Joint Requirements Planning (JRP) Joint Applications Development (JAD)  JRP/JAD is a structured methodology for requirements gathering/negotiations and user interface design and development – during formal interactive workshop sessions  JRP, when used CORRECTLY, will dramatically shorten the front-end analysis of new or re-engineered computer systems – by bringing “together” managers/policy makers in one workshop, and key end users, in a separate workshop – Participants in these workshops are referred to as ACTORS  JRP workshops allow actors to share, debate, collaborate goals and identify functional/system requirements  JRP workshops normally last one to five days, depending on the size, complexity and scope of the project

4. Prior to the JRP Workshop  The JRP Facilitator will complete the following steps prior to holding the first JRP workshop:  Identify who will participate, i.e. “key” managers/policy makers, and end users  Meet individually with each of the participants (Actors) to assess their high level requirements/goals for the new/re-engineered system  Schedule the workshop “off-site”, i.e. hotel, conference center

5. JRP Goals  To specify the systems detail from the business perspective - NOT the Technical perspective (The What NOT the How)  To shorten the requirements gathering effort through an organized rational process  To produce quick logical documentation that will MORE likely be accepted following the JRP workshops

6. Examples of TRS II Requirements May 2005  Should be designated as the Agency’s “Authoritative Terminology”  Terminology should use or be used by DOCUMENTUM  TRS should be developed in XML  Current terminology resources (code sets, taxonomies, thesauri) must be integrated into the new structure  Develop an ability to access, select and compare data from across all sources and legislation  Need an Ontology Tool to manage and access  Should incorporate the content of the “Terms of Environment” glossary  Must utilize data dictionaries, e.g., STORET  Terms must be in both English and Spanish

7. Examples of TRS II Requirements May 2005  Must get rid of duplicate input  Need to have a “Quick” Help System and a user friendly interface  Should contain a shopping cart to chose and download “like” terminologies that can be manipulated on the desktop  Capable of downloading terminologies to construct XML tags

8. Examples of other TRS II Issues  How will TRS play with the Portal?  How can we manage meaning in Taxonomies without definitions?  Can registries access TRS in order to link out to other sources?  Can the multilingual capabilities of the European GEMET be used?  How would the TRS relate to emergency response terminologies in DHS or DOD?  How should this terminology relate to other the terminology at the federal level?  How can the TRS be kept current and maintained?

9. Contacts Linda Spencer EPA OEI/OIC Data Standards Branch Spencer.linda@epa.gov (202) 566-1651 Denzel Carrico Lockheed Martin, Inc. Denzel.c.carrico@lmco.com (703) 647 5790