Glossary | |
| Terms that are on use on this site. | |
| You can always search for entries (regexp permitted). | |
|
Submit Term | |
All | 1 | 3 | 5 | 7 | 8 | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z
| |
| All | |
| There are 859 entries in the glossary. | |
| Pages: «1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 » | |
| Term | Definition |
| Type II error | Accepting something that should have been rejected. Also known as beta error |
| U chart | A control chart showing the count of defects per unit in a series of random samples |
| Unambiguous | (1) Not having two or more possible meanings. (2) Not susceptible to different interpretations. (3) Not obscurer not vague. (4) Clear, definite, certain |
| Unnatural Pattern | Any pattern in which a significant number of the measurements do not group them selves around a center line; when the pattern is unnatural, it means that outside disturbances are present and are affecting the process |
| Upper control limit (UCL) | Control limit for points above the central line in a control chart / A horizontal line on a control chart (usually dotted) which represents the upper limits of process capability |
| User | (ANSI) Any person, organization, or functional unit that uses the services of an information processing system. See: end user |
| User's guide | (ISO) Documentation that describes how to use a functional unit, and that may include description of the rights and responsibilities of the user, the owner, and the supplier of the unit. Syn: user manual, operator manual |
| V&V | Verification and validation |
| VA VE | Value Analysis/Value Engineering |
| Valid | (1) Sound. (2) Well grounded on principles of evidence (3) Able to withstand criticism or objection |
| Valid input | (NBS) Test data that lie within the domain of the function represented by the program |
| Validate | To prove to be valid |
| Validation | Establishing proof that a design, product, or process will perform to specifications |
| Validation protocol | (FDA) A written plan stating how validation will be conducted, including test parameters, product characteristics. production equipment, and decision points on what constitutes acceptable test results. See: test plan |
| Validation, process | (FDA) Establishing documented evidence which provides a high degree of assurance that a specific process will consistently produce a product meeting its predetermined specifications and quality characteristics |
| Validation, software | (NBS) Determination of the correctness of the final program or software produced from a development project with respect to the user needs and requirements. Validation is usually accomplished by verifying each stage of the software development life cycle. See: verification, software |
| Validation. prospective | (FDA) Validation conducted prior to the distribution of either a new product, or product made under a revised manufacturing process, where the revisions may affect the product's characteristics |
| Validation. retrospective | (FDA) (1) Validation of a process for a product already in distribution based upon accumulated production. testing and control data. (2) Retrospective validation can also be useful to augment initial premarket prospective validation for new products or changed processes. Test data is useful only if the methods and results are adequately specific. Whenever test data are used to demonstrate conformance to specifications, it is important that the test methodology be qualified to assure that the test results are objective and accurate |
| Validation. verification. and testing | (NIST) Used as an entity to define a procedure of review, analysis, and testing throughout the software life cycle to discover errors. determine functionality, and ensure the production of quality software. |
| Value Added | Any action, activity, or process that adds direct value to the output of the action, activity, or process / Or / Each time work is done to inputs to transform them into something of greater usefulness as an end product |
| Value Added Activity | An activity in a process that adds value to an output product or service, that is, the activity merits the cost of the resources it consumes in production |
| Value-adding process | Those activities that transform an input into a customer-usable output. The customer can be internal or external to the organization |
| Variable | A characteristic that may take on different values |
| Variable Cost | A cost element that varies directly with the amount of product or service produced by an activity or cost. Variable costs go to zero if the activity stops |
| Variables data | Data that is measured on a continuous and infinite scale such as temperature, distance, and pressure rather than in discreet units or yes/no options. Variables data is used to create histograms, some control charts, and sometimes run charts / Or / Quantitative data, where measurements are used for analysis / Or / measurement information. Control charts based on variables data include average (X-bar) chart, range (R) chart, and sample standard deviation (s) chart |
| Variance | A measure of deviation from the mean in a sample or population |
| Variation Research | Procedures, techniques, and methods used to isolate one type of variation from another (for example, separating product variation from test variation) |
| Vendor | A person or an organization that provides software and (or hardware and/or firmware and/or documentation to the user for a fee or in exchange for services. Such a firm could be a medical device manufacturer |
| Verifiable | Can be proved or confirmed by examination or investigation. See: measurable |
| Verification | Establishing proof that a design, product, or process is within specifications |
| Verification, software | (NIBS): In general the demonstration of consistence completeness, and correctness of the software at each stage and between each stage of the development life cycle. See: validation, software |
| Version | An initial release or a complete re-release of a software item or software element. See: release |
| Version number | A unique identifier used to identify software items and the related software documentation which are subject to configuration control. The execution of a virus program compromises a computer system by performing unwanted or unintended functions which may be destructive |
| VI | Visual Information |
| Vision | Often incorporated into an organizational mission (or vision) statement to clarify what the organization hopes to be doing at some point in the future. The vision should act as a guide in choosing courses of action for the organization |
| Vision Statement | Vision and Mission have a cause and effect relationship. Vision should reflect what the organization sees for itself 5 10 years down the road. The short time frame helps assure that the organization revitalizes itself every decade or so. The Vision statement should contain direction (improve, decrease, etc.) + indicator (quality, customer satisfaction, etc.) + target value (how much, #, %, etc.) + time limit (by when) |
| Vital few, useful many | A term used by J. M. Juran to describe his use of the Pareto principle, which he first defined in 1950. (The principal was used much earlier in economics and inventory control methodologies.) The principle suggests that most effects come from relatively few causes; that is, 80% of the effects come from 20% of the possible causes. The 20% of the possible causes are referred to as the ‘vital few’; the remaining causes are referred to as the ‘useful many’. When Juran first defined this principle, he referred to the remaining causes as the ‘trivial many’ but realizing that no problems are trivial in quality assurance, he changed it to ‘useful many’ |
| Voice of the Customer | Customer feedback both positive and negative including likes, dislikes, problems and suggestions |
| Voice of the Process | Statistical data that is feedback to the people in the process to make decisions about the process stability and/or capability as a tool for continuous improvement |
| Volume | A portion of data, together with its data carrier, that can be handled conveniently as a unit; e.g., a reel of magnetic tape, a disk pack, a floppy disk |
| VV&A | Verification, Validation, and Accreditation |
| VV&C | Verification, Validation and Certification |
| VV&T | Validation, verification, and testing |
| Waiver | Written authorization to use or release a quantity of material, components, or stores already manufactured but not conforming to the specified requirements |
| WAN | Wide area network |
| Warrant | Warrant is an industry standard document required for all newly tooled or revised products in which the supplier confirms that inspections and tests on production parts show conformance to customer requirements |
| Workaround | A sequence of actions the user should take to avoid a problem or system limitation until the computer program is changed. They may include manual procedures used in conjunction with the computer system |
| Workflow | A system whose elements are activities, related to one another by a trigger relation, and triggered by external events, which represent a business process starting with a commitment and ending with the termination of that commitment |
| World-class quality | A term used to indicate a standard of excellence: best of the best |
| X&R Charts | A control chart which is a representation of process capability over time; displays the variability in the process average and range across time |
All | 1 | 3 | 5 | 7 | 8 | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z
| |
Glossary