QA/QC Appendix D

Glossary

The following terms, which are listed in alphabetical order, are used in this document in ways that may not be familiar to some readers.

Baseline	A system or module that has been designed, developed, and initially tested to meet a particular need, either internal to the Laboratory or for a client.
Change Request	A written request (or a verbal request written down) by a client or other user of an environmental software system to modify that system. Changes can include enhancements or revisions to solve identified problems. Each change is tracked separately.
Change Request Summary	A summary of all activities related to a particular change in a module or system. The summary is completed by the project custodian.
Code	Information provided to guide a computer system through a particular process. Both modules and frameworks depend on code to function properly.
Component	A piece of a software system, for example, module, module user interface, model, pre/post-processor, or framework user interface.
Design	The process of determining appropriate ways of meeting client and user requirements.
Development	The process of implementing a design.
Environmental Software System	A set of modules with a framework designed to analyze risk to human health or the environment through multiple environmental media.
Error/Bug	A difficulty encountered by the user when applying the software system that hinders the application for which the system was intended.
Framework	A mechanism for holistically linking a variety of models while ensuring compatible input and outputs and maintaining the development of testing legacy of individual components.
Input	Data, information, or code that is needed by a module to function.
Implementation	The act of transferring a set of modules within a framework to a client for application at their organization.
Model	The set of scientific calculations that define a particular module.
Modification	A change to or the process of changing a baselined module or framework. Modifications can be enhancements or revisions to fix a particular problem such as an error or bug.
Module	A user interface, scientific model, and possible pre/post-processors that together provide a tool for analyzing environmental phenomena, these modules may be related to a particular environmental media (water, air, soil, etc.), health risk based, statistically based, or any other set of scientific formulations used to model the environment.
Module User Interface	The computer screens that make it easy to collect the data necessary to run the model. Besides gathering the necessary data, the user interface often provides online help to the user, reference storage options for collected data, flexible unit inputs, and other user support functions.
Multiple Media	Potential portions of the environment through which a human, animal, or plant might be exposed to contamination (for example, water, air, soil, etc.).
Object-Oriented	The practice of breaking down a system into its unique and logical components, then developing those components only once and applying them to the system. Each individual components purpose is well defined and testable.
Output	Data, information, or code that results from a module functioning.
Package	The information, documentation, print outs, diagrams, and/or electronic files that document the activities conducted under a particular project or task for a particular stage in the software development life cycle (requirements package for requirements analysis, software development package for design and development, software test package for testing, user's guidance and training package for implementation, and change package for modifying baselined systems or modules).
Pre/Post Processor	Additional code necessary to reconcile module input/output with output/input needs from other the system framework.
Project Management Plan	Description of the ways in which an activity will be conducted to meet client needs.
Project Team	The various staff assigned to develop a system or module to meet client needs.
Requirements	Objectives, activities, constraints, and other information that specify what the client needs the new system or module to accomplish.
Requirements Package	The information, documentation, print outs, diagrams, and/or electronic files that document the objectives, activities, constraints, and other information that specify what the client needs the new system or module to accomplish and how the client will use the system.
Software Development Package	The information, documentation, print outs, diagrams, and/or electronic files that document the methods by which client requirements will be met.
Software Test Package	The information, documentation, print outs, diagrams, and/or electronic files that document the how the system, module, or change will be tested to ensure that it meets client requirements.
Statement of Work	Description of activities to be accomplished for a particular client and the methods by which they will be accomplished.
Technology Transfer	The process of providing the systems or modules to the client's organization for use by their staff.
Testing	The process of checking that systems or modules meet the client requirements and function within the necessary settings.
User	The person who will use the system or module to estimate risks to human health or the environment.