The total range of inherent variation in a stable process. It is determined using data from control charts. The control charts shall indicate stability before capability calculations can be made. Histograms are to be used to examine the distribution pattern of individual values and verify a normal distribution. When analysis indicates a stable process and a normal distribution, the indices Cp and Cpk can be calculated. If analysis indicates a non normal distribution, advanced statistical tools such as PPM analysis, will be required to determine capability. If control charts show the process to be non stable, the index Ppk can be calculated

Also called the fishbone chart because of its appearance and the Ishakowa chart after the man who popularized its use in Japan. Its most frequent use is to list the cause of particular problems. The lines coming off the core horizontal line are the main causes and the lines coming off those are sub causes

A member of senior management who is responsible for the logistical and business aspects of the program

The processes, authorities for, and procedures to be used for all changes that are made to the computerized system and/or the system's data. Change control is a vital subset of the Quality Assurance [QA] program within an establishment and should be clearly described in the establishment's SOPs, See: configuration control

An analytical technique for displaying the relationship between process parameters and manufacturing stations

A form used to display information obtained through data collection when measuring defects and/or problems

A document that specifies the purpose of a team, its power, it's reporting relationships, and its specific responsibilities

A simple data-recording device. The check sheet is custom-designed by the user, which allows him or her to readily interpret the results. The check sheet is one of the seven tools of quality. Check sheets are often confused with data sheets and checklists (see individual entries).

A tool used to ensure that all important steps or actions in an operation have been taken. Checklists contain items that are important or relevant to an issue or situation. Checklists are often confused with check sheets and data sheets (see individual entries).

A term used in a broad sense to describe the relationship between the receiver and the provider of a service. In the world of microcomputers, the term client-server describes a networked system where front-end applications, as the client, make service requests upon another networked system. Client-server relationships are defined primarily by software. In a local area network [LAN], the workstation is the client and the file server is the server. However, client-server systems are inherently more complex than file server systems. Two disparate programs must work in tandem, and there are many more decisions to make about separating data and processing between the client workstations and the database server. The database server encapsulates database files and indexes, restricts access, enforces security, and provides applications with a consistent interface to data via a data dictionary

An independent review of source code by a person, team, or tool to verify compliance with software design documentation and programming standards. Correctness and efficiency may also be evaluated. Contrast with code inspection, code review, code walkthrough. See: static analysis

(Myers/NBS): A manual [formal] testing [error detection] technique where the programmer reads source code, statement by statement, to a group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards. Contrast with, code audit, code review, code walkthrough. This technique can also be applied to other software and configuration items. Syn: Fagan Inspection. See: static analysis

A meeting at which software code is presented to project personnel, managers, users, customers, or other interested parties for comment or approval. Contrast with code audit, code inspection, code walkthrough. See: static analysis

(MyersINBS): A manual testing [error detection] technique where program (source code] logic [structure] is traced manually [mentally] by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions. Contrast with code audit, code inspection, code review. See: static analysis

Written procedures describing coding [programming] style conventions specifying rules governing the use of individual constructs provided by the programming language, and naming, formatting, and documentation requirements which prevent programming errors, control complexity and promote understandability of the source code. Syn: development standards, programming standards

Is variation caused by the process. It is produced by the interaction of aspects of the process that affect every occurrence 

A system of values, beliefs, and behaviors inherent in a company. To optimize business performance, top management must define and create the necessary culture

The property that all necessary parts of the entity are included. Completeness of a product is often used to express the fact that all requirements have been met by the product. See: traceability analysis

(1) The degree to which a system or component has a design or implementation that is difficult to understand and verify. (2) Pertaining to any of a set of structure based metrics that measure the attribute in (1)

An automated system for the support of software development including an integrated tool set, i.e., programs, which facilitate the accomplishment of software engineering methods and tasks such as project planning and estimation, system and software requirements analysis, design of data structure, program architecture and algorithm procedure, coding, testing and maintenance

An examination of the procedures used in a computer system to evaluate their effectiveness and correctness and to recommend improvements. See: software audit

The protection of computer hardware and software from accidental or malicious access, use, modification, destruction, or disclosure. Security also pertains to personnel, data, communications, and the physical protection of computer installations

Off-the-shelf software (COTS)Application software, sometimes general purpose, written for a variety of industries or users in a manner that permits users to modify the program to meet their individual needs

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. See: change control.

A discipline applying technical and administrative direction and surveillance 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 verifying compliance with specified requirements. See: configuration control, change control

Allowing two or more variables to vary together so that it is impossible to separate their unique effects

Acceptance of a team decision so that everyone on the team can live with the decision and support it

Used in reaching unanimous agreement by voluntarily giving consent. An agreement to support a decision

The degree of uniformity, standardization, and freedom from contradiction among the documents or parts of a system or component

A software tool used to test requirements in design specifications for both consistency and completeness