Terminology Reference System Vision

Linda Spencer OEI/OIC Data Standards Branch

Denzel CarricoLockheed Martin Inc

Registry of EPA Applications and

Databases (READ)

Data Element Concepts,

Value Meanings

Environmental Data

Registry(EDR)

Data Dictionaries

Thesauri

Classification Schemes

(Taxonomies)

TerminologyReference

System (TRS)

SystemOntologies

Data Models

PermissibleValueLists Business

AreaOntologies

Data ElementNames and Definitions

ControlledVocabularies

Data Standards

Terms

System Inventory

White– Current CapabilityRed – Future Capability

andRelationships

System of Registries Semantic VisionSystem of Registries Semantic Vision

Joint Requirements Planning (JRP)Joint Applications Development (JAD)

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

Prior to the JRP WorkshopPrior 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

JRP GoalsJRP 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

Examples of TRS II RequirementsMay 2005

Examples of TRS II RequirementsMay 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

Examples of TRS II RequirementsMay 2005

Examples of TRS II RequirementsMay 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

Examples of other TRS II IssuesExamples 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?

ContactsContacts

Linda SpencerEPA OEI/OICData Standards BranchSpencer.linda@epa.gov(202) 566-1651

Denzel CarricoLockheed Martin, Inc.Denzel.c.carrico@lmco.com(703) 647 5790