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