Glossary

Synthetic Organic Chemical Manufacturers Association

Sodium Carbonate. A common water treatment chemical.

Water treatment equipment that uses a sodium-based ion-exchange resin, principally to remove cations.

A pretreatment process which uses cation exchange resin to remove hardness elements (calcium and magnesium) from water. The cation resin is regenerated with Sodium Chloride (NaCl) and during the exchange process, the calcium and magnesium are removed from the water and replaced with sodium ions (Na+). The resulting sodium salts are much more soluble and do not precipitate, which provides better feed water to the RO system.

The removal of hardness (calcium and magnesium) from water. This is a PRETREATMENT process which uses cation exchange resin to remove the hardness elements from the water. The hardness elements are calcium and magnesium. The cation resin is regenerated with sodium chloride and during the exchange process, the calcium and magnesium are removed from the water and replaces with sodium ions (Na+). The resulting sodium salts are much more soluble than the salts of calcium and magnesium and do not precipitate which provides better feed water to the RO system.

(ANSI) Programs, procedures, rules, and any associated documentation pertaining to the operation of a system.

Any executable program which operates on an automated system.

(IEEE) Computer programs, procedures, and associated documentation and data pertaining to the operation of a computer system.

An inherent, possibly accidental, trait, quality, or property of software; e.g., functionality, performance, attributes, design constraints, number of states, lines or branches.

(IEEE) A representation of software created to facilitate analysis, planning, implementation, and decision making. The software design description is used as a medium for communicating software design information, and may be thought of as a blueprint or model of the system.

(NIST) A collection of material pertinent to the development of a software module. Contents typically include the requirements, design, technical reports, code listings, test plans, test results, problem reports, schedules, notes, etc. for the module. Synonymous: Software Development File

(NIST) The project plan for the development of a software product.

(IEEE) The process by which user needs are translated into a software product. The process involves translating user needs into software requirements, transforming the software requirements into design, implementing the design in code, testing the code, and sometimes installing and checking out the software for operational activities. NOTE: these activities may overlap or be performed iteratively.

(IEEE) A software development technique in which two or more functionally identical variants of a program are developed from the same specification by different programmers or programming teams with the intent of providing error detection, increased reliability, additional documentation or reduced probability that programming or compiler errors will influence the end results.

(NIST) Technical data or information, including computer listings and printouts, in human readable form, that describe or specify the design or details, explain the capabilities, or provide operating instructions for using the software to obtain desired results from a software system.

(IEEE) A deliverable or in- process document produced or acquired during software development or maintenance. Specific examples include but are not limited to:1.Project planning documents; i.e., software development plans, and software verification and validation plans.2.Software requirements and design specifications.3.Test documentation.4.Customer-deliverable documentation.5.Program source code.6.Representation of software solutions implemented in firmware.7.Reports; i.e., review, audit, project status.8.Data; i.e., defect detection, test.

(IEEE) The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software; i.e., the application of engineering to software.

(IEEE) The hardware, software, and firmware used to perform a software engineering effort. Typical elements include computer equipment, compilers, assemblers, operating systems, debuggers, simulators, emulators, test tools, documentation tools, and database management systems.

(ODE, CDRH) The identification of safety-critical software, the classification and estimation of potential hazards, and identification of program path analysis to identify hazardous combinations of internal and environmental program conditions.

(IEEE) Source code, object code, job control code, control data, or a collection of these items.

(NIST) Period of time beginning when a software product is conceived and ending when the product is no longer available for use. The software life cycle is typically broken into phases denoting activities such as requirements, design, programming, testing, installation, and operation and maintenance.