Software Requirements
Specification
for
the Design Tool for
Inventory and Monitoring
(DTIM)
DRAFT
1/26/2010
Software Requirements Specification for the Design Tool for Inventory and Monitoring
Table of Contents
Table of Contents ...........................................................................................................................2
1. Introduction ................................................................................................................................3
1.1 Purpose ............................................................................................................................................... 3
1.2 Document Conventions ...................................................................................................................... 4
1.3 Intended Audience and Reading Suggestions .................................................................................... 4
1.4 Project Scope ...................................................................................................................................... 4
1.5 Project Documentation ....................................................................................................................... 5
2. Overall Description ....................................................................................................................5
2.1 Product Perspective ............................................................................................................................ 5
Figure 1—DTIM inputs and outputs, and association with ATIM. ......................................................... 7
2.2 Product Features ................................................................................................................................. 7
2.3 User Classes and Characteristics ........................................................................................................ 7
2.4 Operating Environment ...................................................................................................................... 9
2.5 Design and Implementation constraints ............................................................................................. 9
2.6 User Documentation ........................................................................................................................... 9
2.7 Assumptions and Dependencies ....................................................................................................... 10
3. System Features .......................................................................................................................10
4. External Interface Requirements ...........................................................................................15
4.1 User Interfaces .................................................................................................................................. 15
5. Other Requirements ................................................................................................................15
5.1 Performance Requirements............................................................................................................... 15
5.2 Safety Requirements ......................................................................................................................... 15
5.3 Security Requirements...................................................................................................................... 15
5.4 Software Quality Attributes .............................................................................................................. 15
Appendix B: Glossary ..................................................................................................................17
Version 2/24/2012
Page 2 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
1. Introduction
1.1 Purpose
This document contains the software requirements for the Design Tool for Inventory and
Monitoring (DTIM). Although the tool will be accessible to the public, this project is
focused on helping Forests and Regions improve inventory and monitoring program
design by developing a nationally consistent tool that utilizes existing national datasets.
Initially, work will focus on vegetation monitoring, but the plan is to expand to
monitoring other resources where data are collected from plot-based natural resource
samples. Inventory and monitoring programs will be reviewed and reworked based on
available resources (staff and budget) and the desired level of confidence in statistically
sound estimates of vegetation status and trends. Vegetation and its associated attributes
are fundamental components of Forest Plan desired conditions and objectives. Common
relevant forest monitoring items include broad-level incidence and spread of invasive
plant species; wildlife habitat including cumulative effects analysis for project level
planning; and fuels abundance and distribution. Adaptive approaches are needed to
address emerging monitoring requirements at the forest and landscape levels associated
with climate change, carbon, biofuels and forest certification.
In order to monitor key components of vegetation diversity, over time, the inventory that
is used to derive current estimates must have the same attributes, at the same locations,
remeasured over a meaningful time period. Forest Inventory and Analysis (FIA) data on
forest and nonforest National Forest lands, where available, and data from similar
National Forest inventories provide statistically-based inventories appropriate to use for
broad-level planning, monitoring, and assessment. Unbiased estimates and confidence
intervals can be derived for large landscapes, such as a National Forest. In addition, since
the inventories are a spatially balanced sample across all lands, they can be associated
with various spatial datasets such as ecological section or existing vegetation layers to
describe vegetation characteristics within each map strata.
DTIM would enable the National Forest System (NFS) to use inventory data to design
forest monitoring programs that align pertinent questions answerable with FIA data with
the objectives and desired conditions of the forest plan. The tool would also be used to
evaluate whether existing data are sufficient to answer monitoring questions. If they are
deemed insufficient, then information on precision of the estimates and available
resources for data collection would be used by the DTIM to determine appropriate
sample sizes.
DTIM currently resides in a complex spreadsheet with embedded macros. It provides an
intuitive user interface with prompt outputs while performing necessary statistical
calculations behind the scenes. Iterative work on DTIM will continue to ensure that the
tool is being built as designed, to accommodate user needs identified through
demonstrations and stakeholder input, to adapt to changing needs and new technology,
and to minimize investment risk. This software requirement documentation describes the
current functionality desired in DTIM, following test of the spreadsheet on national
forests in Florida, Michigan, Missouri, and Mississippi. Further requirements testing will
continue in Western forests in the latter half of FY 2009. Based on user feedback from
early releases of DTIM and continued user engagement; additional specifications may be
defined as appropriate and as requested.
Version 2/24/2012
Page 3 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
1.2 Document Conventions
Requirements are numbered REQ-#.# (e.g. REQ-1.3) where the first number represents
the implementation phase and the second number is a sequential number.
1.3 Intended Audience and Reading Suggestions
This document is intended for developers, project managers, team members, testers,
documentation writers, and all interested stakeholders. All acronyms are explained in the
text and included in the list of acronyms in the appendix. The glossary (see appendix)
includes a description of some technical terms to accommodate a diverse audience.
Detailed Use Cases are stored in a separate document. To obtain detail on a particular
requirement, refer to the Use Case document which will be accessed via a link similar to:
http://sforge.fs.fed.us/sf/go/doc4518?nav=1
1.4 Project Scope
The intent of DTIM is to provide forest staffs with a method for designing the forest
vegetation aspect of their monitoring program based on available FIA and intensified grid
data. DTIM will allow the forest staffs to determine what inventory and key monitoring
questions could be addressed using available FIA data and intensified grid data to
estimate the current condition and monitor trends. DTIM will also identify actions and
costs associated with addressing unmet information needs by determining additional data
needs and estimating acquisition costs.
DTIM will work with the Analysis Tool for Inventory and Monitoring (ATIM) to access
available data and determine appropriate sample sizes. However, the scope of the DTIM
project does not include gathering, loading, compilation, or analysis of data. DTIM is a
hands-on tool that requires the input of planning and monitoring staff and is contingent
on their desire to clearly define monitoring goals and utilize available national datasets.
Scope of this project does include expansion of DTIM abilities to inventory and
monitoring program design based on any local or regional dataset, vegetation-based or
otherwise, that uses plot-based sampling to acquire data. Requirements for this extended
ability will be defined through preliminary user experiences and tool demonstrations.
DTIM runs on standard Forest Service software and environment.. Any other software
required would need to be allowed from download by the CIO. Ideally DTIM and ATIM
would be tightly aware of each other when both are present and will provide a seamless
data interface between the two, requiring minimal user direction. Users must be able to
enter estimates and their sampling errors into DTIM by hand. DTIM could also pass a
list of tables that DTIM defined or the Protocol Sample Design (not currently a
requirement).
Version 2/24/2012
Page 4 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
1.5 Project Documentation
All documents related to this project are stored in Source Forge and can be accessed via
the following link:
http://sforge.fs.fed.us/sf/docman/do/listDocuments/projects.rig_datim_2/docman.root
2. Overall Description
2.1 Product Perspective
Procedures for developing monitoring programs and the analysis of the monitoring data
(required under planning regulations at 36CFR 219.6(a)(1), and planning directives at
FSM 1920 and FSH 1909.12) are not directly outlined for implementation, and are not
supported by national applications. Forests are expected to monitor and evaluate
conditions and trends of ecological, social, and economic systems, especially the
contribution of forests to sustainability, but each region or national forest is left to
develop its own monitoring and analytical approach. Field personnel and resource
program managers have routinely sought assistance in monitoring design from a variety
of sources within and external to the agency. Thus, there is an opportunity to improve the
consistency and efficiency of monitoring designs and analyses.
Where there is an opportunity for consistency in monitoring program design, DTIM
provides a tool for all national forests that uses national datasets to answer common
monitoring questions. Although forests have many unique qualities, most have needs
related to vegetation in the forest plan desired conditions and objectives that can be met
using similar language to develop monitoring questions and using FIA data to answer
those questions. Forests also face similar challenges in allocating limited staff and budget
resources to inventory and monitoring needs. These challenges can often be managed by
using the quantitative, unbiased methods provided in the DTIM.
Version 2/24/2012
Page 5 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
Information Needs
FIA and Other Data
Sources
Design Tool
Forest Plan
Monitoring Guide
Plot List
Computed Variable
Protocols
List of Tables
Protocol Sample
Database
Data
Recorder
Field Data
Compilation
Tool
FSVeg and/or
FIADB
Spatial Data
Analysis
Tool
Results for Forest
Planning or
Cumulative Effects
Figure 1 depicts the association between ATIM and DTIM, plus Portable Data Recorder
and Data Compilation software.
Version 2/24/2012
Page 6 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
FIA and Other Data
Sources
Information Needs
Forest Plan
Monitoring Guide
Design Tool
Plot List
List of Tables
Computed Variable
Protocols
Protocol Sample
Database
Analysis
Tool
Results for Forest
Planning or
Cumulative Effects
Figure 1—DTIM inputs and outputs, and association with ATIM.
2.2 Product Features
Creates list of plots to achieve desired level of confidence
Creates list of protocols for each variable applicable to sample scheme
Links to protocols for computed variables associated with field data.
Creates list of desired tables to output from ATIM
Links to ATIM to compile and analyze data, and output estimates and associated
precision for forest planning or cumulative effects.
Ability to integrate with ATIM
Supporting documentation and training materials.
2.3 User Classes and Characteristics
Resource Specialists: Use DTIM to identify existing data and align them with inventory
and monitoring needs. Translate inventory and monitoring needs into concise resource
questions. Consistency in documenting monitoring questions, vegetation estimates, and
associated uncertainty can strengthen monitoring reports, assessments and project
Version 2/24/2012
Page 7 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
planning and analysis (needs for change, potential management practices, purpose &
need, effects analysis, and specialist reports).
Planners and Analysts: Use DTIM to construct a forest monitoring plan that will allow
statistically-sound analysis of current vegetation conditions. DTIM outputs will guide
creation of a monitoring plan with answerable questions that result in timely evaluations
for future courses of action for a Region, Forest, landscape or other land area. Monitoring
plans based on plot-based sampling support valid hypothesis tests comparing current
conditions to Desired Conditions as a basis for adaptive management, systematize
reporting and analysis for monitoring reports including the Comprehensive Evaluation
Report, and assist with calibrating state and transition models used for generating
forecasts.
Geographic Information System (GIS) Specialists: Uses DTIM to define boundaries for
inventory and monitoring, identify areas that need intensified sampling, and lay out the
sampling scheme recommended by DTIM for plot-based samples.
Forest Service Cooperators: Use DTIM to identify areas of overlapping information
needs with national forests, and to create sampling strategies based on available resources
that meet their own needs for vegetation monitoring, habitat monitoring, and invasive
species monitoring.
Interested Public: Use DTIM to identify how forest area changes over time that has been
caused either by nature or human.
In addition there are maintenance and support roles and responsibilities:
Regional Specialists: Maintain the point spatial layer associated with FIA and intensified
grid locations, as well as Regional spatial layer(s) in Oracle SDE that are associated with
the inventory point layer in order to subset the data for analysis by ATIM and for creating
map products using ATIM results. Regional specialists also oversee classifications and
specific algorithms incorporated into ATIM to meet Regional and Forest information
needs. Other Regional Inventory Specialist responsibilities include:
1) Working with FIA Region on an annual basis to update point locations in regards to
FIA plots;
2) Ensuring that all employees within the Region who have access to FIA plot locations
have confidentiality agreements signed on an annual basis;
3) Reviewing data for accuracy; archiving information that is no longer from current
inventory, modifying ownership status as needed, and informing FIA Regional
contact of any changes;
4) Providing technical expertise on inventory data available in Region and appropriate
uses thereof;
5) Providing training and technical transfer, as needed.
Forest Specialists: Work with Regional specialist to ensure that needed classification
algorithms are available in ATIM, and work with Forest and Region Geospatial
specialists to ensure that needed spatial datasets are available within ATIM.
Version 2/24/2012
Page 8 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
2.4 Operating Environment
Operates on standard corporate software with Windows XP operating system
Back end Oracle servers (Linux or similar Operating System) and Microsoft Access (or
similar PC-based database). It is desirable to write code to be database agnostic.
Other Forest Service Natural Resource Applications (FSNRAs) will coexist in this
environment
Anything else? Data stores for off-line work
2.5 Design and Implementation constraints
Access to a development and testing environment as specified in 2.4 above (needed to
progress according to schedule)
Difficulty in implementing national architectural standards (e.g. look and feel, shared
components)
Difficulty in implementing security standards (Certification and Accreditation)
Data access constraints
Network performance
E-Authentication difficulties
Software versions of key commercial products (e.g. Oracle, Access, Java, .Net) are not
available
Migration and customization issues of existing Regional systems
National data and software policies
Unknown issues with the backup and server management procedures
Regional or local inventory and monitoring data and spatial data practices that do not fit
well with this project
Full understanding of the limitations and/or capabilities of NITC (e.g. commercial
software updates and DTIM updates)
Integrate with other FSNRAs (and other National Forest System applications), such as
FSVeg, FSVeg Spatial, FACTS, and Geospatial Interface Tool.
2.6 User Documentation
User instructions will be available for DTIM. All user documentation components will
comply with FSNRA documentation standards. Documentation includes a User Guide
and training materials. Documentation and training materials will be available on the
Version 2/24/2012
Page 9 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
web via Robo Help. In addition, training materials will be available for use in Forest
Service training sessions.
Documentation will include instructions on how to obtain and install client software.
This will include a list of all software and/or hardware prerequisites and instructions on
how to obtain missing prerequisites. It will also include instructions on obtaining,
installing, and quick-checking the new software.
2.7 Assumptions and Dependencies
Assumptions that have direct impact on the requirements are:
1. Forest ID teams are open to a consistent method for designing forest plan
monitoring programs.
2. Questions supported by DTIM and FIA datasets meet the needs of forest
monitoring programs.
3. Use of DTIM for monitoring program development does not place unanticipated
burden on inventory and monitoring staff related to hardware, software, or
network requirements or development of specialized technical skills.
4. The NITC Data Center is established and reliably maintained (e.g. backups,
adequate capacity, contain version management, tuned for top performance).
5. User interface design complies with FSNRA interface standards, where
applicable.
6. All data have been checked for errors using Portable Data Recorder software and
during loading and compilation in the Oracle database.
7. The FIA program will load and maintain data sets in NIMS as well as FSVeg, as
per NFS-FIA MOU.
8. The data will be available in FSVeg within 6 months after field season.
9. Census Water plots are included in the database. DTIM will rely on ATIM to
determine whether or not the plots are used (as appropriate)..
10. NFS can negotiate with the FIA program to load and maintain data sets in NIMS
as well as FSVeg for certain periodic inventories.
11. The Regions will also be responsible for defining and maintaining the Predefined/Corporate spatial data identified see REQ-1.1.
12. NFS Regions will load and maintain regional data sets in FSVeg.
13. Population values (estimation units, sampling design, and strata) are made
available as part of the data.
14. FIA is responsible for developing mid-point diameter growth models for mortality
and removal trees.
3. System Features
Phase I Requirements:
REQ-1.1: Define I&M Information Needs
REQ-1.2: Evaluate Existing Data
REQ-1.3: Explore Monitoring Alternatives
REQ-1.4: Select Inventory
REQ-1.4: Provide Guidance for Implementation Plan
Version 2/24/2012
Page 10 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
REQ-1.1: Define I&M Information Needs
Requirement:
1. Identify national and regional needs
2. Identify specific user needs
Specifications:
1. Identify nationally and regionally defined needs. National and regional authenticated
users can do the following:
a. Maintain (edit, delete, add) pre-loaded national and regional needs in DTIM to
their level of authority (national or regional). Label as national or by region,
and provide optional citation/source and hyperlink. Also see the Standard
Data Management (SDM) project for cataloging protocols and datasets. Use
standard nomenclature, such as SAUNA (see Andy Peavy). If not connected
to web, use what is available, then check for updates when connected.
b. Provide expert question/objective pick list based on needs identified by
regional inventory and monitoring coordinators.
c. Provide customized question/objective list for each region.
d. Provide national and regional inventory cost data (e.g., FIA or NFS) with
associated annotation (i.e., costs included in the estimates).
e. Optionally provide customized cost estimates by strata (e.g., forest types,
terrain, and distance to road).
2. Identify specific user needs. Use national and regional needs. If not connected to
web, use what is available, then check for updates when connected.
a. Prompt user for objectives
b. Prompt user for I&M questions
c. Evaluate timing of remeasurement and reporting. At a minimum, allow the
user to specify the remeasurement cycle based on their reporting cycles
(annual and periodic).
d. Provide prioritization matrix (field) and output prioritized list for full
collection of monitoring questions/metrics. This allows the user to determine
the marginal cost of answering specific questions with specific metrics.
e. Identify population(s) of interest and geographic extent
f. Create list of output tables (metrics and categorical variables)
g. Create list of spatial products and their requirements (consider methods,
attributes, and sample sizes).
h. Create a master repository for user needs so they can be shared.
REQ-1.2: Evaluate Existing Data
Requirement:
1. Identify the various data sources for evaluation
2. Use ATIM for its data sources (see 1.a. Access Different Design-based Inventory
Datasets)
Version 2/24/2012
Page 11 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
3. Identify limitations of all appropriate sources.
4. If can answer the monitoring questions with existing data, then stop. Else return to
2.a.ii to re-evaluate information needs or to 2.c. Explore Alternatives.
Specifications:
1. Identify the various data sources for evaluation
a. Draw from full list of corporate and regional data sources
b. Prompt user for local data sources of plot-based information not located on
corporate system.
2. Use ATIM for its data sources (see 1.a. Access Different Design-based Inventory
Datasets)
3. Identify limitations of all appropriate sources.
a. Identify scale/resolution limitations
b. Identify species-specific limitations
c. Identify limitations by geographic region
4. If can answer the monitoring questions with existing data, then stop. Else return to
REQ-1.1 to re-evaluate information needs or go to REQ-1.3 to explore alternatives.
REQ-1.3: Explore Monitoring Alternatives
Requirement:
1. Consider Costs
2. Consider Options
Specifications:
1. Consider Costs
a. Modify whole-plot cost assumptions, as needed, including the creation of
sampling (cost) strata, such as for difficult/easy forest types, terrain, or
distance to road.
b. Allow users to save the costs for use on other projects.
c. Specify maximum inventory cost.
2. Consider Options
a. Precision
i. Specify precision requirements for key attributes.
ii. Import estimates and sampling errors from ATIM or enter from other
sources
b. Protocols
i. Applying national and regional sets of NFS minimum data standards.
Provide warnings/errors for deviations from these standards.
ii. Automatically select indicator suites based on attributes selected.
Provide warnings/errors for selecting parts of suites or dropping Core
attributes.
Version 2/24/2012
Page 12 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
c.
d.
e.
f.
iii. Prompt user for decision on temporary or permanent plots. Use input to
determine what kind of change estimates can be made (net change only
if temporary) and their precision.
iv. Allow FSVeg protocols from CSE to be used as long as the data can be
used in ATIM (see data standards). Note: consider PDR software issues
(Exam software or MIDAS). Currently having turn around time
problems with FIA.
v. Provide warning to user that dropping standard FIA attributes may affect
the ability to use FIA’s data collection software and ability to use in
FIADB or for Forest and State reporting.
Sampling Design
i. Default to Simple Random Sampling (spatially balanced)—with or
without intensification of an existing sample. Assumes that user can use
post-stratification.
ii. Allow stratification for special areas or other map-based domains.
Provide warning to user that stratification may affect the ability to use in
FIADB or for Forest and State reporting. Also can affect probabilities of
selection if strata change over time.
Plot Design.
i. Provide warning that changing the plot design affects the ability to use
in FIADB or for Forest and State reporting.
ii. Default to 4 subplots. Allow 1–4 subplots. Provide warning that other
than 4 subplots results in non-standard data.
iii. Limit plot selection by regional rules. Do not allowing plot size and
distances to change.
iv. Provide values for crew times and costs based on FIA region, NFS
Region, or Forest.
v. Allow use of co-located plots for other resource attributes, e.g., MSIM.
Logistics
i. Provide recommendations for efficient use of crew’s day and travel time
by region and distance to plots.
Data management capabilities
i. Allow user to enter cost to develop new data management systems.
Output cost to use existing system. Implement rule of thumb: processing
25% of budget, analysis 25%, field costs 50%.
REQ-1.4: Select Inventory
Requirement:
1. Compute total survey costs
2. Output plot design and sampling design
3. Select sample locations
Specifications:
1. Compute total survey costs
Version 2/24/2012
Page 13 of 25
a. Integrate with corporate software
5. Populate Work Plan
4. Determine Equipment Needs
f. Compilation Tool
–identify any needed changes to the standard loader.
Software Requirements Specification for the Design Tool for Inventory and Monitoring
a. Use sample sizes and plot costs to compute total survey costs for various
options.
2. Output plot design and sampling design
a. Output plot design, sampling design, and sample size descriptions. (for
various options?)
3. Select sample locations
a. Determine polygon (target population)
b. Select option for choosing plots (simple random, fixed grid, spatial filling
curves, etc.).
c. Optionally reject plots too close to one another?
d. Optionally use existing plots/grids?
e. Output Plot List with unique (not in FIADB or FSVeg) plot identification and
GIS locations (also new or existing).
f. Output FSVeg setting identification. (This team needs to specify which
setting information to use.)
g. Create and maintain GIS coverage of locations and associated metadata to
characterize them, including any relationships to other samples.
REQ-1.4: Provide Guidance for Implementation Plan
Requirement:
1.
2.
3.
4.
5.
6.
Provide instructions on developing the Field Guide
Provide instructions on developing training materials
Determine software needs
Determine equipment needs
Populate work plan
Develop contract
Specifications:
1. Provide instructions on developing the Field Guide
a. Provide link to the current regional FIA manual
b. List the changes to the Guide (add/drops)
2. Provide instructions on developing Training Materials
a. Provide link to the current regional FIA training materials
b. List the changes to the training materials (add/drops)
3. Determine Software Needs
a. Protocol Sample Design?
b. Migrate and prepare any prior plot data
c. Data Recorder–MIDAS? (keep flexible to handle changes for now)
d. Auditing/Editing software
e. Data loading
Version 2/24/2012
Page 14 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
6.
Develop Contract, as appropriate (give examples)
4. External Interface Requirements
4.1 User Interfaces
5. Other Requirements
5.1 Performance Requirements
- Ability to operate this system in a reasonable (TBD) amount of time
5.2 Safety Requirements
There are no known safety requirements
5.3 Security Requirements
Keberos
E-Authorization
This project does not access or manipulate sensitive data.
This project conforms to the agency Computer Security Rules of Behavior which can be
found at:
http://fsweb.nris.fs.fed.us/rulesofbehavior.shtml
5.4 Software Quality Attributes
There are no additional software quality attributes.
Version 2/24/2012
Page 15 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
Appendix A: Acronyms
ATIM
Analytical Tool for Inventory and Monitoring
DTIM
Design Tool for Inventory and Monitoring
FIA
Forest Inventory and Analysis
FIADB
FIA’s database
FGDC
Federal Geographic Data Committee
FSNRAs Forest Service Natural Resource Applications
GI
Geospatial Interface
GIS
Geographic Information System
I&M
Inventory and Monitoring
MOU
Memorandum of Understanding
NFS
National Forest System
NITC
National Information Technology Center
NRCS
Natural Resource Conservation Service
NRIS
National Resource Information System
OCIO
Office of the Chief Information Officer
R1
Region 1, U.S. Forest Service, Northern Region
R2
Region 2, U.S. Forest Service, Rocky Mountain Region
R3
Region 3, U.S. Forest Service, Southwestern Region
R4
Region 4, U.S. Forest Service, Intermountain Region
R5
Region 5, U.S. Forest Service, Pacific Southwest Region
R6
Region 6, U.S. Forest Service, Pacific Northwest Region
R8
Region 8, U.S. Forest Service, Southern Region
R9
Region 9, U.S. Forest Service, Eastern Region
R10
Region 10, U.S. Forest Service, Alaska Region
SRS
Southern Research Station
TBD
To be determined
Version 2/24/2012
Page 16 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
Appendix B: Glossary
For some terms, one or more definitions are given, and often more than one is in common
usage.
accuracy The degree to which a measured quantity approaches the true value of what is
being measured (Lincoln et al. 1998).
analytical (1) Of or relating to analysis or analytics. (2) Separating into elemental parts
or basic principles. (3) Reasoning from a perception of the parts and interrelations of a
subject. (Webster 1984).
association A physiognomically uniform group of existing vegetation stands that share
dominant overstory and understory species. These occur as repeatable patterns across the
landscape (adapted from FGDC 1997).
attribute A discrete or continuous variable, usually associated with the classification or
measurement of area or vegetation (Bechtold, Patterson 2005).
business needs Ongoing tasks related to a particular business or project and the
information and other support contributing to the completion of these tasks (Brohman and
Bryant 2005).
basal area/ac The cross-sectional area of a single stem, including the bark, measured at
breast height (4.5 ft or 1.37 m above the ground) per acre (adapted from Helms 1998).
biofuels
The fuel component of biomass (adapted from Helms 1998).
biomass (1) Ecology the total dry organic matter at a given time of living organisms of
one or more species per unit area (species biomass) or of all the species in the community
(community biomass). (2) The living or dead weight of organic matter in a tree, stand, or
forest in units such as living or dead weight, wet or dry weight, ash-free weight, etc. (3)
Harvesting the wood product obtained (usually) from in-woods chipping of all or some
portion of trees including limbs, tops, and unmerchantable stems, usually for energy
production (Helms 1998).
biosystem Ecosystem q.v. (Lincoln et al. 1998).
biota
The total flora and fauna of a given area; bios (Lincoln et al. 1998).
biotope (1) The smallest geographical unit of the biosphere or of a habitat that can be
delimited by convenient boundaries and is characterized by its biota. (2) The location of a
parasite within the host’s body (Lincoln et al. 1998).
Version 2/24/2012
Page 17 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
buffer (1) A vegetation strip or management zone of varying size, shape, and character
maintained along a stream, lake, road, recreation site, or different vegetative zone to
mitigate the impacts of actions on adjacent lands, to enhance aesthetic values, or as a best
management practice— synonym buffer strip, buffer zone. (2) GIS a zone of a specified
distance around features (Helms 1998).
Citrix Software that enables organizations to securely access Windows-based line-ofbusiness applications over the Internet with just a Web browser. The software makes
centrally maintained information and applications easy to update and retrieve from just
about anywhere.
classification (1) The process of grouping similar entities into named types or classes
based on shared characteristics. (2) The grouping of similar types (in this case,
vegetation) according to criteria (in this case, physiognomic and floristic) that are
considered significant for this specific purpose. The rules for classification must be
clarified before the types are identified in the classification standard. The classification
methods should be clear, precise, quantitative where possible, and based on objective
criteria so that the outcome will be the same no matter who developed the definition (or
description). Classification by definition involves definition of class boundaries (FGDC
1997, citing UN-EP/FAO 1995).
coordinates In mapping, pairs of numbers that express horizontal distances along
orthogonal axes; or, triplets of numbers measuring horizontal and vertical distances
(FGDC 1998).
dataset Collection of related data. See also geospatial data (USDA Forest Service
2004).
desired future condition (DFC) A description of the land or resource conditions that
are believed necessary if goals and objectives are fully achieved (Helms 1998)
down woody material Dead pieces of wood > 3.0 inches in diameter. Down woody
material includes downed, dead tree and shrub boles, large limbs, and other woody pieces
that are severed from their original source of growth or are leaning more than 45 degrees
from vertical (Bechtold, Patterson 2005).
dominance The extent to which a given species has a strong influence in a community
because of its size, abundance, or coverage. Strong dominance affects the fitness of
associated species (adapted from Lincoln et al. 1998).
E-Authentication USDA e-Authentication account identification consists of a User ID,
a password, and a customer profile that enables one to access a range of USDA
Version 2/24/2012
Page 18 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
applications. It provides the convenience of transacting business with USDA online,
anytime, anywhere.
ecoregion A contiguous geographic area having a relatively uniform macroclimate,
possibly with several vegetation types, and used as an ecological basis for management or
planning (Helms 1998).
ecosystem A complete interacting system of organisms and their environment (USDA
Forest Service 1991).
evaluation The comparison of dynamic sampling results to management objectives
consisting of predetermined standards, expected norms, threshold values, and/or trigger
points (Brohman and Bryant 2005).
Federal Geographic Data Committee (FGDC) An interagency committee, organized
in 1990 under the Office of Management and Budget (OMB) Circular A-16 that promotes
the coordinated use, sharing, and dissemination of geospatial data on a national basis. The
FGDC is composed of representatives from 17 Cabinet-level and independent Federal
agencies (USDA Forest Service 2004).
GeoDB An ArcGIS geodatabase is a collection of geographic datasets of various types
held in a common file system folder, a Microsoft Access database, or a multiuser
relational database (such as Oracle, Microsoft SQL Server, or IBM DB2).
geographic information system (GIS) The term frequently applied to geographically
oriented computer technology. In its broadest sense, GIS is a system for capturing,
storing, checking, manipulating, analyzing, and displaying data that are spatially
referenced to the Earth (Lachowski et al. 1996).
geospatial data Information that identifies the geographic location and characteristics
of natural or constructed features and boundaries on the earth. This information may be
derived from remote sensing, mapping, and surveying technologies (FGDC 1998).
Geospatial Interface (GI) Geospatial Interface (GI) is an ArcMap extension that helps
resource specialist’s work efficiently with ArcMap by providing tools which simplify
loading data and providing various custom products to display and output data.
grid (1) A set of grid cells forming a regular, or nearly regular, tessellation of a surface.
(2) Set of points arrayed in a pattern that forms a regular, or nearly regular, tessellation of
a surface. The tessellation is regular if formed by repeating the pattern of a regular
polygon, such as a square, equilateral triangle, or regular hexagon. The tessellation is
nearly regular if formed by repeating the pattern of an “almost” regular polygon such as a
rectangle, nonsquare-parallelogram, or nonequilateral triangle (FGDC 1998).
Version 2/24/2012
Page 19 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
habitat (1) The combination of environmental or site conditions and ecological
processes influencing a plant community (Jennings et al. 2004). (2) Area or type of
environment in which an organism or population normally lives or occurs (Brohman and
Bryant 2005).
holocoen
Holocenosis q.v.; ecosystem q.v. (Lincoln et al. 1998).
holocenosis The concept of the environment or an ecosystem as a single integrated,
coherent comples in which all parts interact (Lincoln et al. 1998).
interface computers A hardware and software link that connects two computer
systems, or a computer and its peripherals, for data communication (Helms 1998).
invasive species A species that is 1) non-native (or alien) to the ecosystem under
consideration and 2) whose introduction causes or is likely to cause economic or
environmental harm or harm to human health. Invasive species can be plants, animals,
and other organisms (e.g., microbes). Human actions are the primary means of invasive
species introductions (NISIC 2006).
inventory The systematic acquisition, analysis, and organization of resource
information needed for planning and implementing land management (adapted from
USDA NRCS 1997).
iterative (1) Marked by or involving repetition. (2) math of, relating to, or being a
computational procedure to produce a desired result by replication of a series of
operations that successively better approximates the desired result (Webster 1984).
lichen A composite organism formed from the symbiotic association of a true fungus
and an alga (Helms 1998).
litter The surface layer of the forest floor that is not in an advanced stage of
decomposition, usually consisting of freshly fallen leaves, needles, twigs, stems, bark,
and fruits (Helms 1998).
map (1) A spatial representation, usually graphic on a flat surface, of spatial
phenomena (FGDC 1998). (2) A representation, usually on a plane surface, of a region of
the Earth or heavens (Robinson et al.1978).
map scale The extent of reduction required to display a portion of the Earth’s surface
on a map; defined as a ratio of distances between corresponding points on the map and on
the ground (Robinson et al. 1978). Scale indirectly determines the information content
and size of the area being represented. The mapping scale is determined by the agency’s
business needs and the characteristics of the data obtained for the project area. Maps
Version 2/24/2012
Page 20 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
generated from digital imagery can appropriately be displayed at a range of scales
(Brohman and Bryant 2005).
map unit A collection of features defined and named the same in terms of their
vegetation characteristics (USDA Soil Survey Division Staff 1993). Each map unit differs
in some respect from all others in a geographic extent. Map units are differentiated in
map unit design and defined in a map unit description. Design of map units generalizes
the taxonomic units present to the smallest set that (1) meets the objectives of the map,
and (2) is feasible to delineate with available resources and technology (Brohman and
Bryant 2005).
media
The physical devices used to record, store, and (or) transmit data (FGDC 1998).
metadata Refers to “data about data”; describes the content, quality, condition, and
other characteristics of a given set of data. Its purpose is to provide information about a
dataset or some larger data holdings to data catalogues, clearinghouses, and users.
Metadata is intended to provide a capability for organizing and maintaining an
institution’s investment in data to provide information for the application and
interpretation of data received through a transfer from an external source (Jennings et al.
2004, as modified from FGDC 1997).
modeling In reference to geospatial data, the process of creating a new GIS layer by
combining or operating on existing layers. Modeling creates images) that contain several
types of information comprising several GIS variables; e.g., a scene may be considered in
terms of its vegetation, elevation, water, and climate at the same time (Lachowski et al.
1996).
monitoring (1) The systematic collection, analysis, and interpretation of resource data
to evaluate progress toward meeting management objectives (adapted from SRM 1989).
(2) The collection and analysis of resource data to measure changes in the amounts,
spatial distribution, or condition of resource types or parameters over time (Brohman and
Bryant 2005).
nearest neighbor (neighbour) method A method of plotless sampling of populations
in which the distance is measured from an individual (chosen on the basis of its proximity
to a randomly selected point) to its nearest neighbour, and the procedure repeated;
population density estimates can be based on these measurements as for example, by the
formula m=1/4r2 where m is the mean density per unit area and r is the mean distance
between nearest neighbours (Lincoln et el. 1998).
National Information Technology Center (NITC) Is part of the Office of the Chief
Information Officer (OCIO) for the USDA. The mission of NITC is to provide reliable
Version 2/24/2012
Page 21 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
and cost-effective Information Technology Solutions to achieve effective mission
performance delivery for the USDA, its agencies, and others.
physiognomic class A level in the classification hierarchy defined by the relative
percent canopy cover of the tree, shrub, dwarf shrub, herb, and nonvascular life-form in
the uppermost strata during the peak of the growing season (FGDC 1997).
post-stratification A statistical tool used to sort existing plots into a particular
stratification (see stratification).
Robo Help A software program that assists in implementing on-line customer help by
linking directly to the appropriate part of the electronic User Guide.
SDE ESRI interface between RDBMS and the ESRI line of GIS display systems,
including ArcGIS, ArcGIS Engine, ArcGIS Server, and ArcIMS. SDE works with a type
of data called FEATURES and RASTERS contained in GeoDataBases, in comparison
with previous ESRI architectures of COVERAGES or SHAPEFILES that represented
points, lines and polygons, and GRIDS that represented surfaces.
spatial data Data that record the geographic location and shape of geographic features
and their spatial relationships to other features (USDA Forest Service 2004).
species In biological classification, the category below genus and above the level of
subspecies and variety; the basic unit of biological classification (adapted from Lincoln et
al. 1998).
strata Nonoverlapping subdivisions of the population such that each primary sampling
unit is assigned to one and only one subdivision (or stratum). The relative sizes of these
strata are used to compute strata weights (Bechtold, Patterson 2005).
stratification A statistical tool used to reduce the variance of the attributes of interest
by partitioning the population into homogenous strata. It may also involve partitioning a
highly variable but small portion of the population (Bechtold, Patterson 2005).
stratum In general, one of a series of layers, levels, or gradations in an ordered system.
In the natural environment, the term is used in the sense of (1) a region of sea,
atmosphere, or geology that is distinguished by natural or arbitrary limits, or (2) a layer
of vegetation, usually of the same or similar height (adapted from FGDC 1998).
tabular data Data that describe things using characters and numbers formatted in
columns and rows (USDA Forest Service 2004).
Version 2/24/2012
Page 22 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
trees Woody plants that generally have a single main stem and have more or less
definite crowns. In instances where life form cannot be determined, woody plants at least
5 meters in height are considered trees (FGDC 1997).
understory
All forest vegetation growing under an overstory (Helms 1998).
Use Case Descriptions of the major functions that the system will perform for external
actors, and also the goals that the system achieves for those actors along the way.
vegetated Areas having at least 1 percent or more of the land or water surface with live
vegetation cover at the peak of the growing season (FGDC 1997).
vegetation The total plant life or cover in an area; also used as a general term for plant
life; the assemblage of plant species in a given area; cf. faunation (Lincoln et al. 1998).
volume table A listing showing, for one or more species, the average cubic or
merchantable contents of trees or logs according to easily measured tree dimensions, such
as tree diameter or height—note such tables are constructed from samples of felled trees
or from detailed thee dimensional data, and are used for estimating the timber contents of
either individual trees or stands (Helms 1998).
Glossary References
Bechtold, W.A.; Patterson, P.L. eds. 2005. The enhanced forest inventory and analysis
program—national sampling design and estimation procedures. Gen. Tech. Rep. SRS-80.
Asheville, NC: U.S. Department of Agriculture Forest Service, Southern Research
Station. 85 p.
Brohman, R.; Bryant, L. eds. 2005. Existing Vegetation Classification and Mapping
Technical Guide. Gen. Tech. Rep. WO–67. Washington, CD: U.S Department of
Agriculture Forest Service, Ecosystem Management Coordination Staff. 305 p.
Federal Geographic Data Committee (FGDC)—Vegetation Subcommittee. 1997.
Vegetation classification standard. FGDC-STD-005. Reston, VA: Federal Geographic
Data Committee, U.S. Geological Survey [online]. Available:
http://www.fgdc.gov/standards/projects/FGDC-standardsprojects/vegetation/vegclass.pdf [February 2, 2009].
Federal Geographic Data Committee (FGDC). 1998. Content standard for digital
geospatial metadata. FFGDC-STD-001-1998. Reston, VA: Federal Geographic Data
Committee. U.S. Geological Survey [online]. Available:
Version 2/24/2012
Page 23 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/basemetadata/v2_0698.pdf. [February 2, 2009].
Helms, J.A., editor. 1998. The dictionary of forestry. Bethesda, MD: Society of American
Foresters.
Jennings, M.; Faber-Iangendoen, D.; Peet, R.; et al. 2004. Guidelines for describing
associations and alliances of the U.S. national vegetation classification. Version 3.0.
Vegetation Classification Panel. Washington, DC: Ecological Society of America.
Lachowski, H.J.; Powell, T.; Wirth, P.; et al. 1996. Monitoring aspen decline using
remote sensing and GIS: Gravelly mountain landscape, southwestern Montana. Dillon,
MT: U.S. Department of Agriculture, Forest Service, Beaverhead-Deerlodge National
Forest.
Lincoln, R.J.; Boxshall, G.A.; Clark, P.F. 1998. A dictionary of ecology, evolution and
systematics. 2nd ed. New York: Cambridge University Press, USA.
National Invasive Species Information Center (NISIC) 2006. U.S. Department of
Agriculture, National Agricultural Library. Definition submitted by the definitions
subcommittee of the Invasive Species Advisory Committee (ISAC). Aproved by ISAC
April 27, 2006 [online]. Available: http://www.invasivespeciesinfo.gov/whatis.shtml
[February 3, 2009].
Robinson, A.H.; Sale, R.; Morrison, J.L. 1978. Elements of cartography. 4th ed. New
York: John Wiley & Sons.
U.S. Department of Agriculture (USDA), Forest Service. 1991a. FSH 2090.11—
Ecological classification and inventory handbook. Missoula, MT: Department of
Agriculture, Forest Service, Northern Region.
U.S. Department of Agriculture (USDA), Forest Service. 1991b. FSM 2060—Ecosystem
Classification, Interpretation, and Application. Washington, DC: Department of
Agriculture, Forest Service.
U.S. Department of Agriculture (USDA), Natural Resource Conservation Service
(NRCS). 1997. National range and pasture handbook. Washington, DC: U.S. Department
of Agriculture, Natural Resources Conservation Service.
U.S. Department of Agriculture (USDA), Forest Service. 2004. Forest Service metadata
users guide—metadata terms and definitions. Washington, DC: U.S. Department of
Agriculture, Forest Service, Geospatial Advisory Committee [online]. Available:
http://www.fs.fed.us/gac/metadata/glossary.html [February 3, 2009].
Version 2/24/2012
Page 24 of 25
Software Requirements Specification for the Design Tool for Inventory and Monitoring
Webster’s II new Riverside university dictionary. 1984. Boston, MA: The Riverside
Publishing Company. 1536 p.
Version 2/24/2012
Page 25 of 25