Document ID: EPA-HQ-OEI-2005-0015-0003
Agency: epa
Document Type: Supporting & Related Material
Title: 
Posted Date: 2005-11-09T05:00Z

Doc.
No.:
28­
TRS­
SRS­
0089
­
1
Systems
Requirements
Document
for
Environmental
Terminology
Services
Developed
for
Request
for
Comment/
Request
for
Information
November
3,
2005
Revised
November
8,
2005
U.
S.
Environmental
Protection
Agency
Office
of
Environmental
Information
Office
of
Information
Collection
Collection
Strategies
Division
Data
Standards
Branch
Doc.
No.:
28­
TRS­
SRS­
0089
­
2
Doc.
No.:
28­
TRS­
SRS­
0089
­
3
TABLE
OF
CONTENTS
1.0
INTRODUCTION
..................................................................................................
4
1.1
Project
Background...........................................................................................
4
2.0
SYSTEM
DESCRIPTION......................................................................................
4
2.1
Business
Objectives..........................................................................................
4
2.2
Anticipated
Users/
Stakeholders
........................................................................
5
2.3
Concept
of
Operations
......................................................................................
5
3.0
SYSTEM
ARCHITECTURE..................................................................................
6
3.1
Business
Process
Model
...................................................................................
6
3.2
Use
Scenarios...................................................................................................
7
3.2.1
Create
A
Terminology
Resource
for
a
New
Project....................................
7
3.2.2
Map
Terminology
for
Interoperability..........................................................
7
3.2.3
Supply
Terminology
for
Content
Management
System..............................
8
3.2.4
Conduct
a
Broad­
Based
Search
in
Support
of
a
Regulatory
Investigation
.9
3.2.5
Develop
an
XML
Schema
or
DTD
for
a
Dataset.........................................
9
3.2.6
Check
a
Document
with
an
Environmental
Spell
Checker
.......................
10
3.2.7
Select
a
Definition
from
an
Environmental
Dictionary
..............................
10
3.2.8
Create
an
Environmental
Glossary
..........................................................
10
4.0
Conceptual
Data
Model
......................................................................................
10
4.1
Technical
Environment....................................................................................
13
5.0
SYSTEM
REQUIREMENTS
...............................................................................
14
5.1
Content............................................................................................................
15
5.2
Relationships...................................................................................................
16
5.3
Metadata
for
terms
..........................................................................................
16
5.4
Metadata
for
term
sets
....................................................................................
17
5.5
Development
and
Maintenance.......................................................................
17
5.6
Searching
the
Repository
................................................................................
17
5.7
Comparing
Terms
in
the
Repository................................................................
18
5.8
Display
and
Print
.............................................................................................
18
5.9
Data
Exchange................................................................................................
19
5.10
User
Interface..................................................................................................
19
5.11
Validation
and
Error
Prevention.......................................................................
19
5.12
Workflow
.........................................................................................................
19
5.13
System
Interfaces............................................................................................
21
5.14
Non­
Functional
Requirements.........................................................................
22
5.14.1
Usability....................................................................................................
22
5.14.2
Performance.............................................................................................
22
5.14.3
Availability
................................................................................................
22
5.14.4
Standards.................................................................................................
22
5.14.5
Security
....................................................................................................
24
5.15
Support
Requirements
....................................................................................
24
5.15.1
Training
....................................................................................................
24
5.15.2
Documentation.........................................................................................
24
5.15.3
System
Acceptance/
Testing.....................................................................
24
5.15.4
Change
Control
........................................................................................
24
Doc.
No.:
28­
TRS­
SRS­
0089
­
4
1.0
INTRODUCTION
1.1
Project
Background
The
Terminology
Reference
System
(
TRS)
(
http://
www.
epa.
gov/
trs)
is
a
part
of
the
Environmental
Protection
Agency's
System
of
Registries
(
http://
www.
epa.
gov/
sor).
The
TRS
was
developed
in
1997
and
has
not
been
updated
or
revised
since.
The
TRS
is
a
compilation
of
collections
of
terms
from
the
Agency
program
offices
and
the
states.
These
take
all
sorts
of
forms
including
dictionaries,
glossaries,
key
word
lists,
taxonomies,
data
dictionaries,
and
thesauri.
There
is
no
consistency
or
common
format.
The
entries
have
been
captured
in
their
original
formats.
Some
of
the
TRS
collections
have
definitions
and
relationships
but
many
of
the
collections
are
simple
lists
of
terms.
The
TRS
also
contains
the
General
European
Multilingual
Environmental
Thesaurus
(
GEMET).
GEMET
contains
6,000
terms
and
definitions
in
26
languages.
GEMET
is
utilized
as
the
terminology
search
tool
for
EIONET,
the
European
Environment
Agency's
web
site
(
http://
www.
eionet.
eu.
int).
US
EPA
translated
the
GEMET
terminology
into
American
English
with
the
intention
of
using
some
of
its
multilingual
capability
in
retrieval
of
US
EPA
web
documents.
However,
the
multilingual
retrieval
capability
has
never
been
developed.
The
current
TRS
search
capability
and
user
interface
is
very
basic
permitting
only
alphabetical
and
resource
searches.
Other
than
the
ability
to
search
across
all
resources,
there
are
no
links
between/
among
terms
or
concepts
in
these
resources.
The
TRS
is
not
well
known
and
scarcely
used
in
the
Agency.

Over
the
years
there
has
been
no
modernization
effort.
And
yet,
the
needs
of
the
Agency
for
terminology
are
becoming
more
sophisticated.
We
are
looking
beyond
dictionary
capabilities.
The
Agency
is
moving
in
the
direction
of
extending
and
enhancing
web
services
and
portal
technologies.
Both
web
services
and
portals
are
dependent
on
having
robust
terminology
support
so
that
like
things
called
by
different
names
can
be
integrated
through
meaning.
Web
services
will
enable
programs
providing
simple
services
to
interact
with
each
other
and
deliver
added­
value
services.
The
portal
will
synchronize
information
around
a
role,
process
or
project
to
improve
decision­
making.
Web
services
and
portals
are
just
the
beginning
of
semantic
management
of
content.
The
Agency
must
begin
to
put
in
place
the
type
of
terminology
system
able
to
feed
these
new
semantic
technologies.
Only
then
can
it
use
these
new
capabilities
to
improve
its
business
processes
and
services.

2.0
SYSTEM
DESCRIPTION
2.1
Business
Objectives
The
Agency
is
seeking
a
commercial
off­
the­
shelf
(
COTS)
and/
or
Government
off­
the­
shelf
(
GOTS)
software
package(
s)
to
match
the
user/
system
requirements.
The
Agency
will
also
consider
customization
of
a
COTS/
GOTS
and
the
integration
of
several
COTS/
GOTS
products.

Part
of
EPA's
vision
is
to
see
the
TRS
evolve
from
being
just
a
terminology
repository,
into
a
suite
of
Environmental
Terminology
Services
(
ETS).
It
will
always
remain
a
repository
for
environmental
terminology
and
terminology
structures
(
taxonomies,
thesauri,
ontologies,
dictionaries,
etc.).
However,
the
environmental
terminology
contained
in
the
repository
will
be
enriched.
Through
use
and
curation,
the
TRS
will
evolve
from
a
term­
based
system
to
a
concept­
based
system.
The
concepts
the
ETS
contains,
along
with
their
terms
and
definitions,
will
have
sufficient
metadata
to
enable
those
concepts
to
be
used
as
the
building
blocks
for
the
creation
of
business­
driven
Agency
terminology
structures
(
taxonomies,
thesauri,
etc.)
The
repository
will
also
contain
an
authoritative
controlled
vocabulary
for
the
Agency
which
can
serve
in
the
creation
of
glossaries
for
web
pages
and
documents,
a
common
vocabulary
for
search
engines,
and
in
the
development
of
rules
and
regulations.

In
addition
to
being
a
repository,
the
ETS
will
offer
services
which
will
include
1)
tools
to
assist
users
in
the
creation
of
business­
driven
terminology
structures,
2)
the
ability
to
serve
up
terminology
machine
to
Doc.
No.:
28­
TRS­
SRS­
0089
­
5
machine,
3)
terminological
dictionary
interfaces
that
can
be
customized
for
a
user's
web
page,
and
4)
the
capability
for
ETS
terminology
stewards
to
input
terminology
and
edit
their
terminology
structures.

Ultimately,
the
ETS
will
support
the
implementation
of
semantic
web
technologies
including
software
agents
using
ontologies
developed
by
extending
and
enhancing
the
terms,
relationships
and
rules
surrounding
the
concepts
relevant
to
a
specific
business
process.

ETS
will
be
much
more
marketable
and
many
times
more
useful,
once
it
is
shaped
to
fit
the
actual
needs
of
users.
After
the
ETS
is
accepted
as
an
enterprise
solution,
Agency
costs
will
be
lowered
by
centrally
maintaining
terminology
and
terminology
metadata.
In
addition,
the
quality
of
the
data
will
be
improved
as
the
currency
of
the
data
will
automatically
be
maintained
in
a
collaborative
fashion
by
terminology
stewards.
The
development
of
a
robust
ETS
will
also
enable
the
Agency
to
take
advantage
of
efficiency
gained
through
semantic
management
technologies.
Ultimately,
the
ETS
will
be
the
source
of
a
standardized
terminology
for
the
Agency
which
will
improve
data
quality
in
data
integration
and
exchange.

2.2
Anticipated
Users/
Stakeholders
EPA
anticipates
a
number
of
users.
These
include:

IT
staff
including
IT
specialists,
managers,
security
specialists,
system
analysts,
system
architects
and
system
planning
specialists
Decisions
makers
including
Program
Managers,
Environmental
Analysts,
Research
Scientist,
Data
Collection
Managers,
Lawyers,
Emergency
Response
Staff,
Policy
Managers
and
Regulators
Information
professionals
including
Librarians,
Terminology
Experts,
Records
Managers,
Data
Standards
Experts,
Web
Content
Managers,
and
Information
Specialists
General
users
including
Tribal
Experts,
State
Environmental
Agency
staff,
and
the
general
public
interested
in
environmental
issues
More
specifically
the
ETS
will
be
used
by
terminology
stewards
who
have
responsibility
for
maintaining
certain
term
sets
and
by
developers
of
taxonomies
for
EPA's
content
management
and
portal
systems.

The
use
scenarios
related
to
these
stakeholder
groups
are
provided
under
Use
Scenarios
(
Section
3.2)
below.

Many
of
the
users
listed
will
use
the
ETS
"
behind
the
scenes",
with
the
output
from
the
ETS
embedded
or
accessed
by
other
systems,
including
EPA's
Content
Management
System,
EPA
portals
and
desktop
portlets,
and
search
engines.
Both
humans
and
systems
will
use
the
content
of
the
ETS.
Therefore
attention
must
be
paid
to
both
types
of
interfaces.

2.3
Concept
of
Operations
The
ETS
will
be
web­
enabled.
It
will
be
accessible
24/
7.
There
will
be
system
administrator(
s)
and
terminology
stewards
available
to
maintain
the
integrity
of
the
content
and
software.
To
ensure
that
ETS
is
well
maintained,
the
stakeholders
will
meet
periodically
to
discuss
new
technology
in
the
marketplace,
advances
in
terminology
practice
and
recommend
changes
to
the
system.

The
modernization
will
include
both
the
acquisition
of
modern
software
and
redesign
of
the
process
for
the
management
of
the
content.
The
software
must
be
able
to
organize,
advertise
and
manage
Doc.
No.:
28­
TRS­
SRS­
0089
­
6
concepts/
information.
It
must
be
able
to
generate
a
controlled
word
list,
glossary,
taxonomy,
thesaurus,
and
ontology.
It
will
have
an
internal
capability
to
check
for
multiple
definitions
of
a
term
depending
on
the
context.
It
will
be
able
to
make
comparisons
of
terms
and
definitions
based
on
meanings.
It
will
become
the
authoritative
source
for
terms,
and
contain
rigid
security
features
for
the
protection
of
the
system.
The
process
for
management
will
include
a
system
of
terminology
stewards
who,
through
a
system
of
controlled
access,
will
input
and
maintain
definitions
and
terms
to
the
database.

The
EPA
envisions
that
the
ETS
will
provide
the
terminology
for
semantic
management
functions
within
the
Agency.
The
design
team
will
also
be
looking
at
the
use
of
advanced
linking
and
hyper­
linking
capabilities
to
increase
referencing
abilities,
multilingual
options,
and
various
methods
of
comparing
terms
and
terms
sets.
This
will
enable
EPA
to
collaborate
more
fully
internally
and
with
the
health
community,
scientific
community,
environmental
industry,
and
the
international
environmental
community.

The
ETS
will
support
the
implementation
of
the
Federal
Enterprise
Architecture
(
FEA)
(
http://
cio.
gov
)
to
enhance
interoperability
across
business
lines
within
the
federal
government,
for
example
with
other
science
and
regulatory
agencies.

3.0
SYSTEM
ARCHITECTURE
3.1
Business
Process
Model
While
there
are
a
number
of
informal
processes
in
place
at
this
time
for
the
development
of
terminologies
and
vocabularies,
EPA
does
not
have
a
formal
business
process
model
for
the
development
and
governance
of
terminology.
Work
is
currently
underway
on
an
EPA­
wide
taxonomy
for
content
management
and
information
architecture
on
the
web,
but
the
process
for
ongoing
maintenance
of
such
a
taxonomy
and
the
integration
of
that
work
with
the
ETS
has
not
yet
been
determined.

Prior
to
implementing
the
ETS
and
in
conjunction
with
stakeholders
and
developers
working
on
the
other
systems,
one
or
more
processes
will
be
put
into
place.
However,
the
business
process
for
the
ETS
will
change
over
time.
The
processes
may
be
real­
time
or
in
batch.
Some
processes
may
require
more
human
intervention
and
review
while
others
will
require
the
ETS
to
respond
machine­
to­
machine.
A
key
requirement
is
for
a
system
that
will
allow
a
number
of
business
process
models
to
be
used
depending
on
the
requirements
and
the
system
and
group
with
which
the
ETS
is
to
be
interfaced.

A
major
part
of
the
development
of
the
ETS
will
be
the
development
of
a
process
and
governance
for
stewardship
and
curation
of
term
sets
and
eventually
concepts
and
ontologies
across
the
enterprise.
The
governance
structure
is
likely
to
involve
a
number
of
layers,
and
therefore,
a
number
of
roles,
which
may
change
over
time
as
the
ETS
functionality
and
content
mature.

Given
the
enterprise­
wide
nature
of
the
ETS,
the
fact
that
it
is
a
redesign
of
an
existing
system,
and
that
it
will
act
as
an
authoritative
repository
for
terminology
that
will
be
used
by
other
systems,
the
following
business
process
models
are
likely.

New
terminology
will
be
suggested
by
a
user
of
any
of
these
systems,
including
the
ETS
itself,
and
perhaps
automatically
by
one
of
the
systems.
This
new
terminology
will
be
staged
for
review
by
the
stewards
of
a
particular
system
or
by
the
coordinators
of
the
ETS.
Once
the
term
or
concept
has
been
approved,
it
will
be
connected
to
one
of
the
term
sets
in
the
ETS
and
a
minimal
record
will
be
created.

New
terminology
may
also
enter
into
the
system
by
virtue
of
updates
to
the
existing
term
sets
from
external
sources.
For
example,
as
the
GEMET
Thesaurus
is
maintained,
new
versions
will
be
ingested
into
the
ETS.
The
GEMET
Thesaurus
will
include
new
terminology
or
changes
to
the
terminology,
definitions,
etc.
that
existed
in
the
previous
version.
Doc.
No.:
28­
TRS­
SRS­
0089
­
7
3.2
Use
Scenarios
The
following
use
scenarios
were
developed
based
on
interviews
or
discussion
with
key
stakeholder
groups.
It
is
EPA's
intent
to
have
vendors
address
these
use
cases
in
the
formal
response
and
in
any
best
and
final
presentations.

3.2.1
Create
A
Terminology
Resource
for
a
New
Project
The
information
manager
for
a
recently
funded
project/
program
within
the
EPA
needs
to
create
a
taxonomy
to
organize
digital
materials
and
paper
files.
She
accesses
the
ETS
to
look
for
existing
terms
that
can
be
used.
Since
the
program
is
related
to
Air
Quality
and
Health,
she
accesses
the
two
topic
trees.
At
first
she
browses
the
individual
resources
that
have
been
categorized
as
applicable
to
Air
Quality
and
Health.
She
selects
these
two
resources
and
then
browses
them
(
using
a
visualization
tool)
to
get
an
overview
of
the
kinds
of
topics
that
are
included.
Based
on
this
she
finds
some
hierarchies
of
terms
(
trees)
and
individual
terms
that
may
be
useful.
She
selects
the
trees
and
terms
and
downloads
them
into
a
tool
that
allows
her
to
create
a
specialized
resource
based
on
this
input.

In
addition
to
selecting
terms
based
on
browsing,
she
accesses
the
ETS
with
a
text
search
on
key
terms.
The
results
provide
exact
and
near
matches
(
including
truncated
and
stemmed
terms).
She
can
review
the
entire
record,
including
the
source
of
the
term,
the
level
of
authority,
and
the
definition.
Individual
terms
may
be
selected
with
or
without
their
hierarchy
(
if
applicable)
or
other
parts
of
the
record
such
as
the
scope
note
(
definition).

The
tool
allows
the
terms
and
hierarchies
to
be
imported,
displayed
and
manipulated.
The
tool
tracks
changes
or
additions
to
relationships
and
scope
notes
(
definitions)
and
other
key
metadata.
She
can
also
add
new
terms.
These
"
new
terms"
may
be
completely
new
or
they
may
have
been
in
the
ETS,
in
some
form,
but
were
not
identified
by
the
information
manager.

Upon
completion
of
the
new
resource,
the
information
manager
submits
the
resource
back
to
the
ETS.
A
series
of
validation
checks
are
performed
to
ensure
the
quality
of
the
information
that
is
submitted
to
the
ETS.
The
information
manager
assigns
a
curator,
which
may
be
the
information
manager
or
someone
else,
who
has
been
trained
to
perform
this
function.
A
report
of
the
upload
is
provided
not
only
to
the
curator
but
to
the
ETS
coordinator.
The
changes
and
new
terms
are
made
available
in
a
candidate
status
within
the
ETS
until
they
have
been
approved
by
the
ETS
coordinator.

3.2.2
Map
Terminology
for
Interoperability
As
part
of
an
international
project
agreement,
the
U.
S.
and
Europe
must
develop
joint
reporting
mechanisms
based
on
environmental
indicators.
However,
the
U.
S.
and
Europe
have
different
definitions
for
key
terms
used
in
the
development
of
the
indicators.
In
addition,
the
Europeans
must
support
the
official
languages
of
the
European
Union.

The
information
managers
collect
their
respective
indicators
and
definitions.
The
ETS
is
populated
with
these
resources.
The
information
managers
work
collaboratively
to
map
the
terms
used
by
the
U.
S.
and
the
various
multilingual
terms
used
in
Europe
in
order
to
support
the
terms
of
reference
documents,
the
agreements
and
the
reporting
mechanism.
The
terminology
mapping
is
then
used
with
the
respective
metadata
registries
in
order
to
identify
the
appropriate
datasets
and
to
determine
transforms
that
can
be
used
to
make
the
data
more
interoperable.

3.2.3
Develop
and
Register
a
Consensus
Glossary
The
EPA
and
State
and
Tribal
partners
are
undertaking
a
new
project.
During
the
discussions
it
becomes
apparent
that
there
is
no
consensus
on
the
terms
and
the
definitions
of
the
terms
in
this
Doc.
No.:
28­
TRS­
SRS­
0089
­
8
particular
area.
While
in
the
meeting,
the
partners
access
the
ETS.
They
search
for
relevant
terms
and
any
definitions
that
are
available.
In
some
cases
they
agree
on
the
terms
and
their
definitions,
while
in
other
cases
new
consensus
definitions
are
needed
in
order
to
develop
appropriate
terms
of
reference
for
this
project.
In
still
other
cases,
the
terms
do
not
exist
in
the
ETS.
In
these
cases,
the
terms
are
registered
as
candidate
terms.
Over
the
course
of
many
meetings,
they
are
able
to
create
a
consensus
glossary
(
with
definitions)
that
allow
the
work
on
the
project
to
move
forward
with
common
terms
of
reference.

3.2.4
Supply
Terminology
for
the
Content
Management
System
The
Content
Management
System
is
intended
to
organize
and
provide
search
support
for
documents,
web
sites
and
other
information
created
by
EPA.
Part
of
the
CMS
is
the
development
of
a
taxonomy
for
presentation
and
navigation
of
such
information.
The
key
to
the
CMS
is
the
assignment
of
metadata
for
each
piece
of
content.

A
web
content
manager
has
recently
authored
content
related
to
EPA's
latest
success
in
brown
fields
cleanup.
She
provides
the
content
to
the
CMS
so
that
it
can
be
used
by
others
in
press
releases,
articles,
on
the
web
site
and
provided
for
records
management.
As
part
of
the
assignment
of
metadata
for
the
CMS,
she
accesses
terms
provided
to
the
CMS
from
the
ETS.
In
addition
she
adds
any
terms
that
are
not
found.
These
new
terms
are
extracted
from
the
CMS
and
provided
to
the
ETS
curator
for
incorporation
into
the
ETS.

3.2.4.1
Add
a
Node
to
the
Enterprise­
wide
Taxonomy
from
within
the
CMS
An
EPA
Web
Content
Manager
needs
to
classify
a
new
document
according
to
an
enterprise
taxonomy
of
topics.
The
content
refers
to
a
topic
that
does
not
yet
exist
in
the
enterprise­
wide
taxonomy.
Through
the
CMS
interface,
she
adds
the
node
in
what
she
believes
is
the
appropriate
place.
However,
she
does
not
have
authorization
to
make
changes
to
an
enterprise­
wide
taxonomy;
therefore,
her
submission
sets
off
a
workflow
for
review
by
an
enterprise
reference
librarian.
The
new
term
appears
in
the
CMS
only
after
it
has
been
approved.
When
it
is
approved,
it
kicks
off
an
e­
mail
to
the
Web
Content
Manager,
who
classifies
the
document
with
the
new
category.

3.2.4.2
Add
a
Node
to
the
CMS­
specific
Taxonomy
from
within
the
CMS
An
EPA
Web
Content
Manager
uses
a
web­
specific
list
of
audience
types
to
tag
content
according
to
target
EPA
audiences.
As
a
Senior
Web
Manager,
she
is
authorized
to
revise
this
list,
which
is
stored
in
the
central
ETS.
Within
the
CMS
she
adds
a
new
audience
type
to
the
list.
It
appears
immediately
within
the
CMS
and
she
and
her
co­
workers
may
use
the
term
when
tagging
content
for
audience
going
forward.

3.2.4.3
Apply
Categories
and
Terms
from
the
ETS
within
the
CMS
An
EPA
Content
Contributor
adds
new
content,
and
(
depending
on
the
content
type
he
selects
and
perhaps
other
implicit
metadata)
is
prompted
within
the
author
flow
to
supply
explicit
metadata.
Values
come
from
the
central
ETS
­­
either
real­
time
or
as
a
nightly
cache
­­
but
are
displayed
differently
according
to
structures
and
rules.
For
example,
topic
values
are
represented
as
navigable
trees,
with
multiple
facets.
The
Content
Contributor
can
apply
multiple
categories
from
within
and
across
trees.
Other
controlled
terms
are
flatter;
for
example,
Audience
is
represented
as
check­
boxes
or
multi­
selects
in
a
select­
box.
To
the
extent
"
Office"
cannot
be
inferred
from
the
Contributor's
log­
in,
he
must
select
Office
from
a
radio­
button
listing.
Doc.
No.:
28­
TRS­
SRS­
0089
­
9
3.2.4.4
Autosuggest
Categories
and
Terms
When
the
content
contributor
goes
to
tag
new
content,
the
CMS
scans
the
text
and
suggests
categories
and
keyword
terms
based
on
its
"
reading"
of
the
text.
All
terminology
is
supplied
to
the
CMS
from
the
ETS.
Assume
that
the
auto­
classification
subsystem
has
been
at
least
minimally
"
trained"
in
advance.
The
Content
Contributor
reviews
these
suggestions
manually
and
revises
them
as
necessary.

3.2.4.5
Revise
or
Add
Metadata
upon
Transition
to
the
Web
CMS
Repository
An
official
EPA
document
is
finalized
within
a
document
management
repository.
It
has
been
fully
tagged
according
to
print
and
retrieval
needs
to
that
point.
Upon
finalization,
the
business
rules
within
the
system
dictate
that
the
document
is
converted
to
HTML
and
PDF
and
those
renditions
inserted
into
the
Web
CMS
repository.
Using
an
ETS­
based
thesaurus,
the
Web
CMS
applies
additional
metadata
­­
such
as
audience
and
additional
access
terms
­­
to
those
renditions,
based
on
existing
metadata
associated
with
the
document.

3.2.4.6
Invoke
Retention
Rules
Based
on
Metadata
A
Content
Manager
adds
a
new
document
to
the
CMS.
Based
on
a
combination
of
implicit
and
explicit
metadata,
the
CMS
auto­
declares
the
document
a
record.
At
that
point,
it
applies
retention­
specific
metadata
from
the
ETS.
As
necessary,
a
"
hold"
is
placed
on
the
Web
version
and
it
is
managed
as
an
official
record
in
situ
or
the
authoritative
document
is
transferred
to
a
records
repository.

3.2.4.7
Generate
Pages
and
Page
Elements
Based
on
Metadata
The
CMS,
either
in
real­
time
or
on
scheduled
intervals,
reads
categories
out
of
the
ETS
or
a
local
cache
to
generate
metadata­
based
navigation
elements,
directory
structures,
and
custom
index
pages.

3.2.5
Conduct
a
Broad­
Based
Search
in
Support
of
a
Regulatory
Investigation
A
member
of
the
EPA
legal
department
must
conduct
a
broad­
based
search
across
federal,
state
and
publicly
available
information
regarding
the
regulation
of
a
particular
industry.
The
terminology
related
to
this
subject
varies
greatly.
The
lawyer
accesses
the
ETS
to
determine
all
the
terms
related
to
the
process
being
researched.

The
ETS
provides
the
term
as
it
appears
in
all
the
ETS
resources.
The
lawyer
can
choose
to
narrower
the
list
by
resource,
language,
approval
status,
source,
etc.
The
lawyer
can
choose
to
display
broader
terms,
narrower
terms,
or
any
related
terms
(
those
that
have
more
specific
RT
relationships
are
automatically
included
in
this
category,
but
more
precise
relationships
are
also
identified
in
the
display
to
provide
more
precision).

The
lawyer
selects
terms.
The
terms
are
presented
with
the
appropriate
Boolean
logic.
The
lawyer
provides
the
query
to
both
internal
and
external
search
engines.

3.2.6
Develop
an
XML
Schema
or
DTD
for
a
Dataset
A
database
administrator
is
developing
a
database
to
house
a
new
dataset
for
monitoring
asthma
and
various
particulates.
The
agency
policy
is
that,
whenever
possible,
data
elements
and
corresponding
XML
tags
should
be
selected
from
the
XML
Registry
and
the
EDR,
in
order
to
promote
interoperability
Doc.
No.:
28­
TRS­
SRS­
0089
­
10
and
integration
of
data.
The
database
administrator
first
searches
these
two
registries
in
the
SOR,
but
finds
no
previously
developed
element.
He
then
searches
the
ETS
for
a
concept
that
can
be
used
to
name
and
define
the
new
data
element.

He
searches
the
ETS
by
term.
The
ETS
responds
with
uses
from
all
sources.
He
then
limits
the
results
to
those
terms
that
are
approved
for
EPA
official
use.
It
turns
out
that
the
term
he
queried
is
not
the
official
term,
but
there
is
an
official
term
which
is
a
synonym
for
it.
The
database
administrator
selects
this
term
for
use
in
his
application.

The
term
usage
is
updated
in
the
ETS
to
reflect
the
fact
that
it
is
proposed
for
use
with
this
system/
dataset.
However,
this
is
only
a
temporary
status.
When
the
system/
dataset
moves
from
development
to
production,
the
element's
status
is
also
changed
to
reflect
its
approved
usage.

3.2.7
Check
a
Document
with
an
Environmental
Spell
Checker
An
EPA
researcher
is
working
on
a
journal
article.
The
authoring
process
is
supported
by
a
spell
checker
for
environmental
protection.
The
content
of
the
ETS
that
meets
certain
criteria
(
authority
status,
source,
approval
status,
audience,
etc.)
is
extracted
and
provided
as
a
spell
checker.
This
spell
checker
can
be
loaded
as
an
add­
in
to
existing
spell
check
dictionaries,
including
those
used
for
word
processing
and
email
applications.
The
extracted
terms
from
the
ETS
are
enhanced
with
special
routines
to
handle
morphological
variants,
such
as
adverbs,
singular
versus
plural,
etc.

3.2.8
Select
a
Definition
from
an
Environmental
Dictionary
A
Congressional
staffer
is
working
on
draft
legislation
for
regulating
a
chemical
that
has
been
determined
to
be
detrimental
to
human
health.
In
order
to
ensure
continuity
between
this
draft
legislation
and
previous
related
legislation,
the
staffer
accesses
the
appropriate
dictionary
while
in
the
word
processing
software.

The
content
of
the
ETS
that
meets
certain
criteria
(
authority
status,
source,
approval
status,
audience,
etc.)
is
extracted
and
provided
in
an
alphabetical
list
with
one
or
more
scope
notes
(
definitions)
as
a
dictionary.
This
dictionary
is
made
available,
in
various
forms,
to
the
public,
decision
makers,
Congressional
staffers,
or
researchers.

He
searches
the
dictionary
for
the
process
that
is
being
regulated.
The
ETS
provides
a
scope
note
(
definition)
that
has
been
used
before.
It
also
provides
a
link
to
the
related
chemicals
in
the
Chemical
Registry
and
to
the
regulation/
legislation
that
previously
defined
or
used
the
process
term.
Having
looked
up
the
process,
the
Congressional
staffer
copies
the
definition
from
the
ETS
into
the
document
that
he
is
creating.

3.2.9
Create
an
Environmental
Glossary
A
publications
manager
wants
to
create
a
specialized
glossary
for
a
report
on
brown
field
technologies.
Based
on
the
audience/
office
metadata
elements
and
the
terms
related
to
the
term
"
brown
field",
he
selects
terms
and
their
definitions.
The
ETS
provides
the
capability
to
display
the
terms
in
alphabetical
order
followed
by
the
appropriate
definition
for
the
context.
He
has
the
option
to
include
all
the
terms
or
to
process
it
against
the
terms
that
actually
appear
in
the
report.

4.0
CONCEPTUAL
DATA
MODEL
Doc.
No.:
28­
TRS­
SRS­
0089
­
11
The
Conceptual
Data
Model
is
based
on
ISO
1087­
1.
A
graphical
representation
of
1087­
1
is
provided
below.
The
terms
used
in
the
model
are
defined
in
the
ISO
standards
listed
in
Section
5.14.4.
Doc.
No.:
28­
TRS­
SRS­
0089
­
12
Object
Property
Concept
Characteristic
Concept
System
Representation
Designation
Definition
Term
Name
Concept
Relation
Hierarchical
Associative
Spatial
Causal
Temporal
Generic
Partitive
Concept
Type
Superordinate
Subordinate
Co­
ordinate
Generic
Comprehensive
[
has]*
/
is
of
is
abstraction
of
/[
maps
with]*
is
of
/
has
represented
by
/
represents
contained
in
/
contains
contains
/
contained
in
types
concepts
in
/
has
type
concepts
of
Specific
Partitive
Subject
Field
Concept
Field
has
/
is
of
has
/
is
of
has
/
is
of
Special
Language
1087­
1
Summary
Type
of
Characteristic
is
categorized
by
/
categorizes
used
as
criterion
to
establish
/
established
using
Doc.
No.:
28­
TRS­
SRS­
0089
­
13
The
initial
content
in
the
ETS
will
be
focused
on
terms
and
term
sets.
However,
over
time,
some
of
the
content
will
be
enhanced
into
a
concept­
based
system
as
reflected
in
the
Conceptual
Data
Model.
The
ETS
must
serve
current
needs
and
also
evolve
into
a
richer
environment;
the
system
must
support
partial
implementation
of
this
conceptual
model.
For
example,
term
sets
that
are
in
the
current
ETS
must
be
migrated
to
the
ETS
without
losing
current
information
or
demanding
the
completion
of
information
that
is
not
available
at
the
time
of
migration.
Some
sets
will
be
sets
of
terms,
without
connections
to
concepts,
definitions
or
relationships.
The
ETS
must
allow
these
simpler
structures
to
be
imported
and
maintained,
while
allowing
additional
information,
such
as
relationships,
designations
and
definitions
to
be
added
over
time.
For
example,
special
projects
or
routine
curation
of
the
ETS
may
over
time
connect
separate
terms
around
a
single
concept,
assign
"
approved
or
preferred"
attributes,
or
specify
relationships
or
more
granular
relationships
than
those
that
exist
upon
original
import
into
the
ETS.

4.1
Technical
Environment
The
EPA
technical
environment
is
changing
as
are
many
of
its
systems.
The
anticipated
environment
is
centered
on
the
use
of
Oracle
for
database
management,
NorthernLights
for
unstructured
search,
Oracle
Portal
for
portal
development,
and
Documentum
for
enterprise­
wide
content
management
of
documents
as
well
as
web
content.
However,
EPA
is
seeking
an
ETS
environment
that
is
open
enough
to
allow
this
technical
environment
to
change
over
time,
allowing
for
the
interchange
of
components
without
major
impacts
on
the
ETS.
As
the
ETS
becomes
an
environmental
tool,
State,
international
and
public
users
of
the
ETS
may
want
to
interface
a
variety
of
their
own
systems
with
the
ETS,
so
an
open
environment
based
on
standards,
XML
and
web
services
is
desirable.

The
Agency,
through
the
work
of
the
Exchange
Network
and
its
Central
Data
Exchange
(
CDX)
(
http://
www.
exchangenetwork.
net/
),
is
moving
in
the
direction
of
extending
and
enhancing
Web
service
capabilities.
These
services
permit
the
aggregation
of
large
quantities
of
information
across
different
software
applications,
running
on
a
variety
of
platforms
and/
or
frameworks.
Web
services
are
dependent
on
having
robust
terminology
support
so
that
like
things
that
are
called
by
different
names
can
be
integrated
through
meaning
and
so
that
programs
providing
simple
services
can
interact
with
each
other
in
order
to
deliver
sophisticated
added­
value
services.

The
Agency
is
piloting
portal
technology
as
a
collaborative
decision
management
solution
within
the
enterprise.
It
is
envisioned
that
the
portal
will
support
a
convergence
of
collaboration,
knowledge
management,
and
business
intelligence.
The
portal
accesses
content
from
disparate
data
sources;
synchronizes
information
around
a
role,
process
or
project;
allows
users
to
collaborate
with
subject
matter
experts
throughout
the
decision
network
for
insight
and
experience.
Key
to
the
success
of
the
Portal
Project
will
be
the
development
and
use
of
terminology
to
bring
information
together
around
meaning.

The
Terminology
Reference
System
is
and
will
continue
to
be
a
part
of
a
suite
of
registries
(
EPA's
System
of
Registries)
based
on
ISO
11179
(
http://
metadata­
standards.
org/
11179/).
The
anticipated
interaction
among
the
registries
is
shown
in
the
following
diagram.
Doc.
No.:
28­
TRS­
SRS­
0089
­
14
20
System
of
Registries
Semantic
Vision
System
of
Registries
Semantic
Vision
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
Black
 
Current
Capability
Red
 
Future
Capability
and
Relationships
5.0
SYSTEM
REQUIREMENTS
The
following
requirements
have
been
gathered
from
a
variety
of
stakeholder
groups.
Priorities
are
provided.
N=
Necessary.
D=
Desirable.
F=
Future.
Doc.
No.:
28­
TRS­
SRS­
0089
­
15
5.1
Content
5.1.1.1
The
system
shall
have
the
capability
to
build
and
maintain
a
variety
of
term
set
structures,
including
simple
term
lists
(
pick
lists),
taxonomies,
thesauri,
glossaries,
gazetteers,
etc.
(
N)

5.1.1.2
The
system
shall
have
the
capability
to
build
and
maintain
ontologies.
(
D)

5.1.1.3
The
system
shall
maintain
concepts,
associated
terms,
relationships
between
concepts,
term
definitions,
meanings,
synonyms,
abbreviations,
acronyms,
context,
and
note
fields.
(
N)

5.1.1.4
The
system
shall
support
the
migration
and
storage
of
terms
from
the
existing
TRS.
The
resources
currently
available
in
the
TRS
are
listed
at
http://
iaspub.
epa.
gov/
trs/
SEARCH$.
STARTUP#
2
(
browse
down
to
Information
Resource
search,
keep
the
keyword
field
blank,
keep
"
All"
in
the
Resource
Type
field,
and
press
Begin
Search).
(
N)

5.1.1.5
The
system
shall
have
the
capability
to
associate
multiple
terms
with
a
concept.
(
N)

5.1.1.6
The
system
shall
have
the
capability
to
maintain
an
approved
(
or
preferred)
term
attribute
by
context,
if
necessary.
(
N)

5.1.1.7
The
system
shall
have
the
capability
to
maintain
an
authoritative
definition
attribute.
(
N)

5.1.1.8
The
system
shall
have
the
capability
to
maintain
an
authoritative
form
or
representation
attribute.
(
N)

5.1.1.9
The
system
shall
have
the
capability
to
store
terms
in
upper,
lower
and
mixed
case.
(
N)
Doc.
No.:
28­
TRS­
SRS­
0089
­
16
5.1.1.10
The
system
shall
support
foreign
language
terms.
(
N)

5.1.1.11
The
system
shall
handle
non­
roman
alphabets
(
Unicode
UTF
8).
(
N)

5.1.1.12
The
system
shall
store
common
misspellings
of
terms
to
support
aliases
from
the
misspellings
to
the
correct
spellings
in
search
systems.
(
D)

5.1.1.13
The
system
shall
associate
terms
with
a
type
of
audience
or
other
context.
(
N)

5.1.1.14
The
system
shall
cite
references
for
key
elements
such
as
term
definitions
and
to
hyperlink
to
reference
materials
in
digital
form.
(
D)

5.1.1.15
The
system
shall
maintain
scientific
notation.
(
D)

5.2
Relationships
5.2.1.1
The
system
shall
have
the
capability
to
assign
and
manage
relationships
between
concepts.
(
N)

5.2.1.2
The
standard
relationships
Broader
Term,
Narrower
Term,
and
Related
(
Associative)
Term
shall
be
available.
(
N)

5.2.1.3
Hierarchical
relationships
shall
be
further
specified
through
standard
relationships
such
as
partitive
and
generic.
(
N)

5.2.1.4
Hierarchical
and
Associative
relationships
shall
be
further
specified
through
user
defined
relationships,
both
uni­
and
bi­
directional.
(
N)

5.2.1.5
The
system
shall
have
the
capability
to
label
terms
as
abbreviations
or
acronyms
and
to
cross­
reference
them
to
the
full
versions
of
terms.
(
N)

5.2.1.6
The
system
shall
have
the
capability
to
relate
taxonomies
created
from
the
ETS
to
their
parent
collections.
(
D)

5.3
Metadata
for
terms
5.3.1.1
The
system
shall
have
the
capability
to
record
the
date
of
entry,
date
of
modification,
language,
encoding
scheme
(
such
as
the
transliteration
scheme
used),
responsible
individual
or
group,
for
terms
and
specific
components
of
the
concept
record,
such
as
definitions.
(
N)

5.3.1.2
The
system
shall
assign
unique
identifiers
to
each
concept
and
term
within
the
system.
Minimally
this
should
be
a
URL,
but
a
URI
or
a
Handle
that
allows
for
global
uniqueness
on
when
the
information
is
put
on
the
web
is
important.
(
N)
Doc.
No.:
28­
TRS­
SRS­
0089
­
17
5.3.1.3
The
system
shall
have
the
capability
to
record
notes
concerning
the
use,
history
and
provenance
of
the
concepts,
terms
and
relationships.
(
N)

5.3.1.4
The
system
shall
be
able
to
record
the
applications
where
a
term
is
used.
(
D)

5.3.1.5
The
system
shall
have
the
capability
to
add
other
metadata
elements
as
needed.
(
D)

5.4
Metadata
for
term
sets
5.4.1.1
The
system
shall
have
the
capability
to
maintain
metadata
for
term
sets.
Minimally,
the
Dublin
Core
element
set
shall
be
available
for
describing
term
sets.
(
N)

5.4.1.2
The
system
shall
have
the
capability
to
associate
terms
and
definitions
with
specific
EPA
program
office
or
system
that
owns
the
terminology.
(
N)

5.4.1.3
The
system
shall
have
the
capability
to
store
contact
information
for
terminology
stewards.
(
N)

5.5
Development
and
Maintenance
5.5.1.1
The
system
shall
have
the
capability
to
add
information
to
a
record
over
time,
including
new
definitions,
new
relationships,
etc.
(
N)

5.5.1.2
The
system
shall
have
a
collaborative
maintenance
facility
to
maintain
content.
(
D)

5.5.1.3
The
system
shall
have
the
capability
to
control
term
and
term
set
versioning.
(
N)

5.6
Searching
the
Repository
5.6.1.1
The
system
shall
have
the
capability
to
search
a
concept
and
retrieve
all
or
part
of
the
record
for
that
concept
including
terms
linked
to
that
concept,
related
concepts
and
their
relationships,
etc.
(
N)

5.6.1.2
The
system
shall
have
the
capability
to
perform
a
Boolean
search
and
phrase
searching.
(
N)

5.6.1.3
The
system
shall
have
the
capability
to
perform
case
sensitive
and
case
insensitive
searches
based
on
user
preference
at
the
time
of
the
search.
(
N)
Doc.
No.:
28­
TRS­
SRS­
0089
­
18
5.6.1.4
The
system
shall
have
the
capability
to
search
for
EPA
approved
terms
and
term
sets
separate
from
other
terms
and
term
sets.
(
N)

5.6.1.5
The
system
shall
maintain
records
of
all
transactions,
including
searching.
(
N)

5.6.1.6
The
system
shall
have
the
capability
to
recover
search
failures
by
offering
partial
or
alternative
word
choices.
(
N)

5.6.1.7
The
system
shall
have
the
capability
to
search
on
partial
or
truncated
terms,
both
left
and
right
truncation
and
masking
of
characters.
(
N)

5.6.1.8
The
system
shall
have
a
memory
capability
to
record
each
user's
past
sessions.
(
F)

5.6.1.9
The
system
shall
have
the
capability
to
provide
prompts
for
new
session
queries
based
on
a
record
of
the
user's
past
sessions.
(
F)

5.6.1.10
The
system
shall
have
the
capability
to
store
browser
navigation
information.
(
D)

5.6.1.11
The
system
shall
have
the
capability
to
restrict
a
search
to
a
single
term
set
selected
by
the
user
or
application.
(
N)

5.6.1.12
The
system
shall
have
the
capability
to
restrict
a
search
to
a
group
of
term
sets
selected
by
the
user
or
application.
(
N)

5.7
Comparing
Terms
in
the
Repository
5.7.1.1
The
system
shall
have
the
capability
to
compare
and
contrast
terms
within
and
across
term
sets.
(
N)

5.7.1.2
The
system
shall
have
the
capability
to
compare
and
contrast
definitions
within
and
across
term
sets.
(
N)

5.7.1.3
The
system
shall
have
the
capability
to
use
meanings
to
compare
terms
and
term
sets.
(
N)

5.8
Display
and
Print
5.8.1.1
The
system
shall
have
default
displays
to
support
the
display
and
printing
of
terms
and
types
of
term
sets.
(
N)

5.8.1.2
The
system
shall
display
terms
from
hierarchies
in
a
variety
of
standard
formats
including
a
flat
alphabetical
list,
a
display
of
the
term
within
the
hierarchy,
etc.
(
N)

5.8.1.3
The
system
shall
display
the
placement
of
a
term
within
an
ontology.
(
D)

5.8.1.4
The
system
shall
provide
printer
friendly
formats.
(
N)

5.8.1.5
The
system
shall
have
the
capability
to
hide
or
expose
archived
terms
and
term
set
versions.
(
N)
Doc.
No.:
28­
TRS­
SRS­
0089
­
19
5.9
Data
Exchange
5.9.1.1
The
system
shall
have
the
capability
to
use
well­
structured
and
documented
XML
for
the
exchange
of
terminology
with
other
systems.
(
N)

5.9.1.2
The
system
shall
have
the
capability
to
export
and
import
terminologies
in
SKOS/
RDF
as
defined
by
the
W3C
Deployment
and
Best
Practices
Working
Group.
(
F)

5.9.1.3
The
system
shall
have
the
capability
to
extract
and
export
a
term,
terms
or
an
entire
term
set,
along
with
selected
fields/
relationships,
such
as
a
terms
and
all
its
synonyms,
a
term
and
its
related
terms,
a
term
and
its
definitions,
etc.
(
N)

5.10
User
Interface
5.10.1.1
The
system
shall
allow
the
system
administrator
to
customize
the
interface
including
the
display
fields,
order
of
the
fields
and
whether
the
field
is
read
only.
(
N)

5.10.1.2
The
system
shall
record
user
feedback/
comments.
(
N)

5.10.1.3
The
system
shall
be
508
compliant.
(
N)

5.10.1.4
The
system
shall
have
the
capability
to
support
browsers
back
one
previous
version
on
both
MACS
and
PCs.
(
N)

5.10.1.5
The
system
shall
support
internationalized
or
localized
interfaces,
for
example
in
Spanish
or
Korean.
(
D)

5.11
Validation
and
Error
Prevention
5.11.1.1
The
system
shall
have
the
capability
to
alert
the
user
or
administrator
to
the
entry
of
duplicate
information
both
on
individual
and
batch
loads
to
support
proper
version
control.
(
N)

5.11.1.2
The
system
shall
have
the
capability
to
spell­
check
terms.
(
N)

5.11.1.3
The
system
shall
have
the
capability
to
alert
the
user
to
potential
format
errors
when
adding
individual
terms
and
terms
in
batch.
(
N)

5.11.1.4
The
system
shall
have
an
undo
function.
(
N)

5.12
Workflow
Doc.
No.:
28­
TRS­
SRS­
0089
­
20
5.12.1.1
The
system
shall
have
the
capability
to
assign
roles
and
limit
access
and
functionality
based
on
those
roles.
One
such
role
shall
involve
the
stewards
of
the
term
sets.
(
N)

5.12.1.2
The
system
shall
have
the
capability
to
establish
a
workflow
for
terms
which
includes
the
input
of
candidate
terms
and
term
sets
from
across
the
agency,
a
review
by
one
or
more
coordinators,
and
"
publication"
of
those
terms
via
the
ETS,
and
the
ability
to
deprecate
terms
and
archive
them.
(
N)

5.12.1.3
The
system
shall
have
the
capability
to
change
archived
terminology
to
active
status.
(
N)
Doc.
No.:
28­
TRS­
SRS­
0089
­
21
5.13
System
Interfaces
5.13.1.1
The
system
shall
have
an
open
environment,
allowing
interfaces
via
APIs
or
web
services
to
support
integration
with
a
variety
of
other
EPA
systems.
(
N)

5.13.1.2
The
system
shall
have
the
capability
to
interface
with
other
tools
for
building
a
variety
of
knowledge
organization
systems
including
tools
for
building
taxonomies,
pick
lists,
thesauri,
etc.
(
N)

5.13.1.3
The
system
shall
have
the
capability
to
interface
with
other
tools
for
building
a
variety
of
knowledge
organization
systems
including
tools
for
building
taxonomies,
pick
lists,
thesauri,
etc.
(
N)

5.13.1.4
The
system
shall
have
the
capability
to
interface
with
other
ontology
building
tools.
(
D)

5.13.1.5
The
system
shall
have
the
capability
to
support
the
tagging
of
web
pages
from
the
authoritative
terminology.
(
N)

5.13.1.6
The
system
shall
have
the
capability
for
users
to
link
geospatial
data
to
nongeospatial
terms
for
tagging
and
retrieval.
(
D)

5.13.1.7
The
system
shall
have
the
capability
to
interface
with
other
terminology
collections
inside
and
outside
the
EPA.
(
D)

5.13.1.8
The
system
shall
have
the
capability
to
exchange
terminology
with
other
webbased
systems.
(
N)

5.13.1.9
The
system
shall
have
the
capability
to
support
full­
text
searches
from
EPA
websites.
(
N)

5.13.1.10
The
system
shall
have
the
capability
to
mine
terminology
from
other
sources.
(
F)

5.13.1.11
The
system
shall
have
the
capability
to
exchange
terminology
from
machine
to
machine.
(
N)

5.13.1.12
The
system
shall
have
the
capability
to
export
selected
terminology
into
a
desktop
portlet.
(
N)

5.13.1.13
The
system
shall
have
the
capability
to
exchange
data
with
the
EPA
Portal
tool.
(
N)

5.13.1.14
The
system
shall
have
the
capability
to
exchange
terminology
with
the
EPA's
Enterprise
Content
Management
System.
(
N)

5.13.1.15
The
system
shall
have
the
capability
to
interface
with
the
taxonomy
tool
XML
registry.
(
N)
Doc.
No.:
28­
TRS­
SRS­
0089
­
22
5.14
Non­
Functional
Requirements
5.14.1
Usability
5.14.1.1
The
system
shall
have
the
capability
to
maintain
an
on­
line,
context
sensitive
Help
Feature
including
"
Frequently
Asked
Questions".
(
N)

5.14.2
Performance
5.14.2.1
The
system
shall
respond
to
requests
within
an
average
of
2
to
5
seconds.
(
N)

5.14.2.2
The
system
shall
have
the
capability
to
respond
to
a
minimum
of
50
identical
requests
simultaneously.
(
N)

5.14.3
Availability
5.14.3.1
The
system
shall
be
operational
within
the
EPA
network
and
accessible
from
the
Internet
24/
7.
(
N)

5.14.3.2
The
system
shall
have
documented
recovery
procedures.
(
N)

5.14.4
Standards
The
system
shall
consider
the
following
standards.

o
Section
508
of
the
Rehabilitation
Act
o
EPA
System
Development
and
Security
Standards
o
EPA
User
Interface
Standards
o
ISO
704:
2000
 
Terminology
work
 
Principles
and
Methods
o
ISO/
CD
704
[
2005]
 
Terminology
work
 
Principles
and
Methods
o
ISO
860:
1996
 
Terminology
work
 
Harmonization
of
concepts
and
terms
o
ISO/
CD
860
[
2005]
 
Terminology
work
 
Vocabulary
 
Harmonization
of
concepts
and
terms
o
ISO1087­
1:
2000
 
Terminology
work
 
Vocabulary
 
Part
1:
Theory
and
applications
o
ISO
1087­
2:
2000
 
Terminology
work
 
Vocabulary
 
Part
2:
Computer
applications
o
ISO/
DIS
1951
[
2005]
 
Presentation/
representation
of
entries
in
dictionaries
o
ISO
2788:
1986
 
Documentation
 
Guidelines
for
the
establishment
and
development
of
monolingual
thesauri
o
ISO
5964:
1985
Documentation
 
Guidelines
for
the
establishment
and
development
of
multilingual
thesauri
o
ISO/
IEC
11179­
3:
2003
­
Information
technology
­­
Data
Management
and
Interchange
­­
Metadata
Registries
(
MDR)
­
Part
3,
Registry
Meta­
model
and
Basic
Attributes
Doc.
No.:
28­
TRS­
SRS­
0089
­
23
o
ISO
12200:
1999
­
Computer
applications
in
terminology
 
Machine­
readable
terminology
interchange
format
(
MARTIF)
 
Negotiated
interchange
o
ISO
12620:
1999
­
Computer
applications
in
Terminology
 
Data
categories
o
ISO/
CD
12620
[
2005]
­
Computer
applications
in
Terminology
 
Data
categories
o
ISO
15188:
2001
 
Project
management
guidelines
for
terminology
standardization
o
ISO/
CD
16503
[
2005]
­
Computer
applications
in
terminology
 
Representations
of
terminological
data
 
MARTIF­
compatible
format
with
specified
constraints
(
MSC)

o
ISO
16642:
2003
 
Computer
applications
in
terminology
 
Terminological
markup
framework
o
ISO/
WD
24156
[
2005]
 
Guidelines
for
applying
concept
modeling
in
terminology
work
o
ANSI/
NISO
Z39.19
 
2003
­
Guidelines
for
the
Construction,
Format,
and
Management
of
Monolingual
Thesauri
Doc.
No.:
28­
TRS­
SRS­
0089
­
24
5.14.5
Security
5.14.5.1
The
system
shall
be
in
compliance
with
all
National
Computing
Center
(
NCC)
security
directives,
Technology
Information
Security
Staff
(
TISS)
policies,
procedures
and
directives
and
with
National
Institute
for
Standards
and
Technology
(
NIST)
security
guidance.
(
N)

5.14.5.2
The
system
shall
have
the
capability
to
set
different
access
levels
for
users.
(
N)

5.14.5.3
The
system
shall
require
a
log­
on
for
users
who
are
maintaining
content,
but
not
for
agency
or
public
users
who
are
only
searching
and
viewing
the
content.
(
N)

5.15
Support
Requirements
5.15.1
Training
5.15.1.1
The
system
shall
include
an
on­
line
user's
guide.
(
N)

5.15.1.2
The
system
shall
include
an
on­
line
tutorial.
(
N)

5.15.2
Documentation
5.15.2.1
The
system
shall
have
a
documented
procedure
for
updates,
maintenance
migration,
and
documented
methods
for
applying
user
customization
when
upgrades
and
patches
are
applied.
(
N)

5.15.2.2
The
system
shall
be
documented
as
if
the
development
environment
is
certified
at
and
operating
at
the
Software
Engineering
Institute
(
SEI)
Capability
Maturity
Model
for
Software
(
CMM)
Level
3
 
"
The
Defined
Level."
(
D)

5.15.3
System
Acceptance/
Testing
5.15.3.1
The
system
shall
be
usability
tested
according
to
standard
Office
of
Environmental
Information
(
OEI)
protocols.
(
N)

5.15.4
Change
Control
5.15.4.1
The
system
shall
have
a
formal
change
control
process
that
will
be
tested
and
delivered
when
the
system
is
operational.
(
N)
Doc.
No.:
28­
TRS­
SRS­
0089
­
25