Search Results

The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards that form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards.

The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards which form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards.

The CDIF Family of Standards is primarily designed to be used as a description of a mechanism for transferring information between CASE tools. It facilitates a successful transfer when the authors of the importing and exporting tools have nothing in common except an agreement to conform to CDIF. The language that is defined for the Transfer Format also has applicability as a general language for Import/Export from repositories. The CDIF Integrated Meta-model defined for CASE also has applicability as the basis of standard definitions for use in repositories. The standards which form the complete family of CDIF Standards are documented in EIA/IS-106 CDIF - CASE Data Interchange Format - Overview. These standards cover the overall framework, the transfer format and the CDIF Integrated Meta-model. The diagram in Figure 1 depicts the various standards that comprise the CDIF Family of Standards. The shaded box depicts this Standard and its position in the CDIF Family of Standards.

This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes the software portion of firmware. This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.

This guide provides implementation consideration guidance for the normative clauses of IEEE/EIA 12207.0. The guidance is based on software industry experience with the life cycle processes presented in IEEE/EIA 12207.0.

This document is applicable to electronic component and equipment manufacturing.

This standard is intended to provide a uniform method of determining proportion nonconforming in finished components and to provide a standardized definition of the quality index referred to as PPM. The method used here is primarily directed at components whose production or procured volume is large enough, during some predefined sampling period, to give statistically meaningful information.

This Assessment Guide is applicable to any assessment technique that wishes to embrace the principles and concepts presented in the EIA-599 National Electronic Process Certification Standard.

Conventional attribute sampling plans based upon nonzero acceptance numbers are no longer desirable. In addition, emphasis is now placed on the quality level that is received by the customer. This relates directly to the Lot Tolerance Percent Defective (LTPD) value or the Limiting Quality Protection of MIL-STD-105. Measuring quality levels in percent nonconforming, although not incorrect, has been replaced with quality levels measured in parts per million (PPM). As a result, this standard addresses the need for sampling plans that can augment MIL-STD-105, are based upon a zero acceptance number, and address quality (nonconformance) levels in the parts per million range. This document does not address minor nonconformances, which are defined as nonconformances that are not likely to reduce materially the usability of the unit of product for its intended purpose.

This Standard is applicable to suppliers of electronic components, assemblies, equipment and related materials. This standard establishes the general requirements to achieve a certified process. The use of this standard is intended for any manufacturing or service company whose goal is to achieve customer satisfaction through continuous improvement.

The procedure outlined in this document is applicable to any manufacturing or service process. It may be used on part of a process or and entire process or a series of sequential processes.

This standard specifies requirements for the approval and maintenance of a manufacturer's capability and the procedures for the test and release of passive electronic components manufactured under capability approval. It also includes requirements for generic specifications that invoke this standard. It applies to all passive electronic components to be released under the capability requirements of an EIA generic and/or sectional and/or detail specification.

The general requirements of an SPC system shall encompass, but are not limited to, the following elements: a Overall quality system b Management commitment c SPC system documentation d Critical process nodes e Gage characterization and capability f Process characterization and capability g Control system documentation h On-line/off-line control i Training j Supplier SPC systems k Calibration l Preventive maintenance m Self audit

This standard is intended to provide a uniform method of calculating an estimate of the proportion nonconforming in finished components and to provide a standardized definition of the quality index referred to as Average Outgoing Quality (AOQ). The method used here is primarily directed at components whose production or procured volume is large enough, during some predefined sampling period, to give statistically meaningful information.

This model is designed to enhance insight into the application of meaningful metrics. The emphasis is on business processes which may best provide indication of the level of risk to the customer when contemplating or continuing business with the supplier base. (E.g., the RFP/RFQ, proposal, supplier selection, and performance).