IEEE 7-4.3.2-2003 pdf download

IEEE 7-4.3.2-2003 pdf download.IEEE Standard Criteria for Digital Computers in Safety Systems of Nuclear Power Generating Stations
3.1.1 acceptance testing:
(1) Formal testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. See also: qualification testing, system testing.
(2) Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a system or component.
3.1.2 application software: Software designed to fulfill specific needs of a user; for example, software for navigation, payroll, or process control.
3.1.3 architecture: The organizational structure of a system or component.
3.1.4 commercial grade item: An item that is a) not subject to design or specification requirements unique to nuclear facilities; and b) used in applications other than nuclear facilities; and c) ordered from the manu- facturer/supplier on the basis of specifications set forth in the manufacturer’s published product description (for example, a catalog).
3.1.5 commercial grade item dedication: A process of evaluating and accepting commercial grade items to obtain adequate confidence of suitability for safety application.
3.1.6 complexity: (1) The degree to which a system or system component has a design or implementation that is difficult to understand and verify. (2) Pertaining to any set of structure-based metrics that measure the attribute in definition (1).
3.1.7 component: One of the parts that make up a system. A component may be hardware or software and may be subdivided into other components. NOTE—The terms “module,” “component,” and “unit” are often used interchangeably or defined to be supplements of one another in different ways dependent upon the context. The relationship of these terms is not yet standardized.
3.1.8 computer: A functional programmable unit that consists of one or more associated processing units and peripheral equipment, that is controlled by internally stored programs, and that can perform substantial computation, including numerous arithmetic or logic operations, without human intervention.
3.1.9 computer instruction: (1) A statement in a programming language, specifying an operation to be per- formed by a computer and the addresses or values of the associated operands; for example, Move A to B. (2) Loosely, any executable statement in a computer program.
3.1.10 computer program: A combination of computer instructions and data definitions that enable computer hardware to perform computational or control functions.
3.1.11 computer system: A system containing one or more computers and associated software.
3.1.12 configuration: (1) The arrangement of a computer system or component as defined by the number, nature, and interconnections of its constituent parts. (2) In configuration management, the functional and physical characteristics of hardware or software as set forth in technical documentation or achieved in a product.
3.1.13 configuration control: An element of configuration management, consisting of the evaluation, coordination, approval or disapproval, and implementation of changes to configuration items after formal establishment of their configuration identification.
3.1.14 configuration item: An aggregation of hardware, software, or both, that is designated for configuration management and treated as a single entity in the configuration management process.
3.1.15 configuration management: A discipline applying technical and administrative direction and sur- veillance to identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements.
3.1.16 correctness: (1) The degree to which a system or component is free from faults in its specification, design, and implementation. (2) The degree to which software, documentation, or other items meet the spec- ified requirements. (3) The degree to which software, documentation, or other items meet user needs and expectations, whether specified or not.
3.1.17 data: (1) A representation of facts, concepts, or instructions in a manner suitable for communication, interpretation, or processing by humans or by automatic means. (2) Sometimes used as a synonym for documentation.
3.1.18 data structure: A physical or logical relationship among data elements, designed to support specific data manipulation functions.
3.1.19 design: (1) The process of defining the architecture, components, interfaces, and other characteristics of a system or component. (2) The result of the process in definition (1).
3.1.20 document: (1) A medium and the information recorded on it, that generally has permanence and can be read by a person or a machine. Examples in software engineering include project plans, specifications, test plans, user manuals. (2) To create a document as in definition (1). (3) To add comments to a computer program.
3.1.21 documentation: (1) A collection of documents on a given subject. (2) Any written or pictorial information describing, defining, specifying, reporting or certifying activities, requirements, procedures, or results. (3) The process of generating or revising a document. (4) The management of documents, including identification, acquisition, processing, storage, and dissemination.IEEE 7-4.3.2 pdf download.IEEE 7-4.3.2-2003 pdf download