A device, computer program, or system that behaves or operates like a given system when provided a set of controlled inputs. Contrast with emulator. A simulator provides inputs or responses that resemble anticipated process parameters. Its function is to present data to the system at known speeds and in a proper format

A way of simultaneously designing products, and the processes for manufacturing those products, through the use of cross functional teams to assure manufacturability and to reduce cycle time

A term used generally to indicate that a process is well-controlled, i.e., ±6 sigma from the centerline in a control chart. The term is usually associated with Motorola, which named one of its key operational initiatives Six Sigma Quality

Statistical Process Control The application of statistical methods to analyze data, study and monitor process capability and performance. Use of control charts to monitor process performance

The cause(s) of variation in a process which have a source that is identified, and can be eventually eliminated. [Same as assignable cause] / Or / Causes of variation in a process that are not inherent in the process itself but originate from circumstances that are out of the ordinary. Special causes are indicated by points that fall outside the limits of a control chart

Test data based on input values that are likely to require special handling by the program. See: error guessing; testing. special case

A document that specifies, in a complete, precise, verifiable manner, the requirements, design, behavior, or other characteristics of a system or component, and often, the procedures for determining whether these provisions have been satisfied. Contrast with requirement. See: specification, formal; specification, requirements; specification, functional; specification, performance; specification, interface; specification, design; coding standards; design standards

Evaluation of each safety-critical software requirement with respect to a list of qualities such as completeness, correctness, consistency, testability. robustness, integrity, reliability, usability, flexibility, maintainability, portability, interoperability, accuracy, audibility, performance. internal instrumentation, security and training

A specification that documents the interface requirements for a system or system component. Often part of a requirements specification. Contrast with requirement

A specification that documents the requirements of a system or system component. It typically includes functional requirements. performance requirements, interface requirements, design requirements [attributes and constraints], development [coding] standards, etc Contrast with requirement

A specification that documents how a system is to be built. It typically includes system or component structure, algorithms, control logic, data structures, data set [file] use information, input/output formats, interface descriptions, etc Contrast with design standards, requirement. See: software design description

(1) A specification written and approved in accordance with established standards. (2) A specification expressed in a requirements specification language. Contrast with requirement

A specification that documents the functional requirements for a system or system component. It describes what the system or component is to do rather than how it is to be built. Often part of a requirements specification. Contrast with requirement

A visual reporting tool for the performance of a number of indicators. Also known as a "radar chart" this tool makes visible the gaps between the current and desired performance

A model of the software development process in which the constituent activities, typically requirements analysis, preliminary and detailed design. coding, integration, and testing, are performed iteratively until the software is complete Syn: evolutionary model, Contrast with incremental development; rapid prototyping; waterfall model

Statistical Quality Control: The application of statistical techniques to measure variation in materials, parts, components, and products. The process of maintaining acceptable levels of product quality by using statistical techniques

A process from which all special causes of variation have been eliminated and only common causes remain / Or / A process which is free of assignable causes, e.g., in statistical control

Written procedures [prescribing and describing the steps to be taken in normal and defined conditions] which are necessary to assure control of production and processes

A diagram that depicts the states that a system or component can assume, and shows the events or circumstances that cause or result from a change from one state to another. Syn: state graph. See: state-transition table

(1) (NBS) Analysis of a program that is performed without executing the program. (2) (IEEE) The process of evaluating a system or component based on its form, structure, content, documentation. Contrast with dynamic analysis. See: code audit, code inspection, code review, code walk-through, design review, symbolic execution

A quantitative condition which describes a process that is free of assignable/special causes of variation, e.g., variation in the central tendency and variance. Such a condition is most often evidenced on a control chart, i.e., a control chart which displays an absence of nonrandom variation / Or / Is the condition of a process from which all special causes of variation have been eliminated and only common causes remain. Statistical control is evidenced on ,a control chart by the absence of points beyond the control limits and by the absence of any non random patterns or trends

(SPC) Analysis and control of a process through the use of statistical techniques, particularly control charts / Or / the application of statistical techniques to control a process. Often the term statistical quality control is used interchangeably with statistical process control

Analysis and control of quality through the use of statistical techniques, focus is on the  product not the process

A structured software design technique; data and processing steps are defined broadly at first, and then further defined with increasing detail

A contract vehicle sponsored by the Department of Defense. The contract provides business process reengineering support services focused on the higher order strategic and management assessment functions. Reengineering services include fully qualified BPR experts with functional knowledge in all aspects of process engineering, state of the art analytical tools and time tested methodologies for comprehensive process improvement

Variation caused by regular, systematic changes in output, such as seasonal patterns and long-term trends

A diagram that identifies modules, activities, or other entities in a system or computer program and shows how larger or more general entities break down into smaller, more specific entries. Note: The result is not necessarily the same as that shown in a call graph. Syn: hierarchy chart, program structure chart. Contrast with call graph

A logical grouping of objects or events which displays only random event to event variations, e.g., the objects or events are grouped to create homogenous groups free of assignable or special causes. By virtue of the minimum within group variability, any change in the central tendency or variance of the universe will be reflected in the "subgroup to subgroup' variability

A major part of a system which itself has the characteristics of a system, usually consisting of several components

Anyone whose output (materials, information, service, etc.) becomes an input to another person or group in a process of work. A supplier can be external or internal to the organization / Or / Those responsible for providing the input to a process

Confidence that a supplier’s product or service will fulfill its customers’ needs. This confidence is achieved by creating a relationship between the customer and supplier that ensures the product will be fit for use with minimal corrective action and inspection. According to J. M. Juran, there are nine primary activities needed: 1) define product and program quality requirements, 2) evaluate alternative suppliers, 3) select suppliers, 4) conduct joint quality planning, 5) cooperate with the supplier during the execution of the contract, 6) obtain proof of conformance to requirements, 7) certify qualified suppliers, 8) conduct quality improvement programs as required, and 9) create and use supplier quality ratings

A post-registration quality audits to ensure the quality systems is still effectively implemented and continuous improvement is evident

A combination of several components or pieces of equipment integrated to perform a specific function / or / (1) (ANSI) People, machines, and methods organized to accomplish a set of specific functions. (2) (DOD) A composite, at any level of complexity, of personnel, procedures, materials, tools, equipment, facilities, and software The elements of this composite entity are used together in the intended operational or support environment to perform a given task or achieve a specific purpose, support. or mission requirement

The person that is charged with the overall administration, and operation of a computer system. The System Administrator is normally an employee or a member of the establishment. Syn: system manager

(ISO) A systematic investigation of a real or planned system to determine the functions of the system and how they relate to each other and to any other system. See: requirements phase

(ISO) A process of defining the hardware and software architecture, components, modules, interfaces, and data for a system to satisfy specified requirements. See: design phase, architectural design, functional design

(ISO) The collection of documents that describe the requirements, capabilities, limitations, design, operation, and maintenance of an information processing system. See: specification, test documentation, user's guide

(ISO) The progressive linking and testing of system components into a complete system. See: incremental integration

The course of developmental changes through which a system passes from its conception to the termination of its use; a.g., the phases and activities associated with the analysis. acquisition, design, development, test, integration, operation, maintenance, and modification of a system. See: software life cycle

(DOD) The application of engineering and management principles, criteria, and techniques to optimize all aspects of safety within the constraints of operational effectiveness, time, and cost throughout all phases of the system life cycle. See: risk assessment, software safety change analysis, software safety code analysis, software safety design analysis, software safety requirements analysis, software safety test analysis, software engineering

Method searches for the most appropriate and effective means of accomplishing given objectives. ... Systematic diagrams can be divided into two types: The constituent component analysis diagram breaks down the main subject into its basic elements and depicts their relationships to the objectives and means of obtaining those objectives. The plan development diagram systematically shows the means and procedures necessary to successfully implement a given plan. It is typically represented graphically either a horizontal or vertical tree structure connecting the elements / Or / is a hierarchical graphic representation of the prerequisite steps necessary to go accomplish a goal or task