Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...

Articles Figures Tables About

Documenting Component Specifications

Implementations always include some element of specification (but not vice versa), so the two kinds of document are never entirely separate. First, an implementation need not be complete down to the finest detail it might interconnect a few smaller component specifications, leaving their implementations to be chosen separately. Second, the concepts the participants talk about when they interact can also be specified rather than implemented using types, we can define what information must be sent without deciding its representation. [Pg.222]

Component specification The boundary. Specification of the behavior of a component, saying nothing about its internal design. The document may also show collaborations between the component and the objects around it (whether soft, hard, or live). It is... [Pg.222]

System or component specification One or more documents, each of which describes a black-box view of a software system or component, specified as a type. In turn, it may be structured as... [Pg.233]

A Replacement in Kind (RIK) is a replacement that does not vary from documented plant specifications—a replacement of an instrument, electrical, piping, or other component with an identical part or an equivalent approved and specified by the applicable engineering standard. Some RIK examples include, but are not limited to ... [Pg.258]

D1.3 Are documented configuration specifications in place for each network component (e.g., Mainframes, Servers, Storage Devices, Transceivers, Repeaters, Bridges and Renters, etc.) ... [Pg.868]

Batch manufacturing documentation to be used should be prepared after these critical parameters of the process have been identified, and machine settings, component specifications and environmental conditions have been determined and specified. [Pg.175]

The tendency to have a pack component specification which is all-embracing is also changing. A simpler procedure utilises a series of information documents which lay out the procedures that a supplier has to follow for selective package forms, i.e. glass bottles, plastic bottles, laminates, labels, collapsible tubes, etc. It is then possible to have an abbreviated specification document which covers critical, major and minor defect classifications, advice on delivery and identification, and basic information on the material to be employed, etc. The specification therefore cross-references to its respective information (component manual) document and becomes considerably simplified in terms of both layout and detail. This is particularly important now that specifications are being computerised in conjunction with stock control and purchasing. [Pg.27]

For either situation (i.e. of a special or common standard component) the purchaser must document the component specification. The specification must be approved and authorised by the relevant departments of the organisation and accepted by the supplier as the contract specification. [Pg.76]

It is to identify and emphasise the fact that, in spite of the efforts of quality project teams, defects can occur, and specification details can be unrealistic, that the first component specification and the first QC procedure must be considered provisional. A review of both documents should be the last operations of the quality project team within an agreed time scale, say after the first five deliveries, or 6-12 months. This will allow practical experience through manufacture, distribution and use to be applied to the final specifications. [Pg.77]

Each preliminary subsystem specification and preliminary design-to baseline should be evolved into a subsystem specification and a design-to baseline, respectively. Preliminary component specifications and build-to baselines should be defined for the components of the subsystem being developed. Final subsystem documents should include identification of recotmnended components and interfaces resolution of sub-... [Pg.22]

Requirements are the basis for the design and manufacturing of every car component. In order to reduce costs and prevent failures, a systematic requirements management approach is necessary. However, many requirements are not component specific, but apply to every assembly. In the case of Volkswagen, these requirements are collected in so called template requirements documents, which are enriched with component specific requirements. In order to improve the reuse of component requirements and to consider lessons learnt, Volkswagen introduced a new requirements management methodology called master requirements document (MRD). [Pg.126]

The proposed variant of Scrum - SafeScrum, is motivated by the need to make it possible to use methods that are flexible with respect to planning, documentation and specification while still being acceptable to lEC 61508, as well as making Scrum a useful approach for developing safety critical systems. The rest of this section explains the components and concepts of this combined approach. [Pg.448]

A modular scanner system for NDE has been developed. It consists of a selection of individual electronics and motor module components, supported by scanner configuration and control software. The modules are used as standard building blocks for construction of job specific, dedicated scanners as well and general purpose scanners. The use of modular scanner components significantly reduce the work, time and cost not only for the design and manufacture but also for establishing documentation and ensure compliance with the relevant EU-directive requirements. [Pg.805]

Regularly interstratified (1 1) chlorite and vermiculite has been attributed to the mineral corrensite [12173-14-7] (141). Chlorite mixed layers have been documented with talc, vermicuhte, smectite, iUite, biotite, kaolinite, serpentine, and muscovite. The mixed-layer mineral is named after the components, eg, talc—chlorite. The eadier Hterature, however, has reference to specific minerals such as kulkeite [77113-95-2] (talc—chlorite and tosudite... [Pg.199]

A system is an ordered set of ideas, principles, and theories or a chain of operations that produces specific results to be a chain of operations, the operations need to work together in a regular relationship. A quality system is not a random collection of procedures (which many quality systems are) and therefore quality systems, like air conditioning systems, need to be designed. All the components need to fit together, the inputs and outputs need to be connected, sensors need to feed information to processes which cause changes in performance and all parts need to work together to achieve a common purpose i.e. to ensure that products conform to specified requirements. You may in fact already have a kind of quality system in place. You may have rules and methods which your staff follow in order to ensure product conforms to customer requirements, but they may not be documented. Even if some are documented, unless they reflect a chain of operations that produces consistent results, they cannot be considered to be a system. [Pg.160]

Product specifications should specify requirements for the manufacture, assembly, and installation of the product in a manner that provides acceptance criteria for inspection and test. They may be written specifications, engineering drawings, diagrams, inspection and test specifications, and schematics. With complex products you may need a hierarchy of documents from system drawings showing the system installation to component drawings for piece-part manufacture. Where there are several documents that make up the product specification there should be an overall listing that relates documents to one another. [Pg.252]

The review of the data portion of the Indian Point 2 (IP2) and 3 (IPS) PRA (a 1982 internal document prepared by Consolidated Edison and the New York Power Authority) is confined to the plant-specific and generic component failure and service hour data sections because these were the only segments available to the reviewers. The LERs produced during a ten-year span of IP2 s operation were evaluated to determine their applicability to the PRA data needs. It was eventually decided to use only the LERs generated after IP2 became critical (from May 23, 1973 to December 31, 1979) for the component data base development, based on the availability of failure event information and more uniform operability, testing, and reporting criteria. [Pg.119]

Inspection tolerance can be divided into two major components the accuracy variability of the instruction and the repeatability of the measuring method. The calibration and accuracy of the instrument are documented and certified by its manufacturer, and it is periodically checked. Understanding the overall inspection process is extremely useful in selecting the proper method for measuring a specific dimension. When all the inspection methods available provide an acceptable level of accuracy, the most economical method should be used. [Pg.443]


See other pages where Documenting Component Specifications is mentioned: [Pg.228]    [Pg.228]    [Pg.21]    [Pg.302]    [Pg.44]    [Pg.549]    [Pg.312]    [Pg.87]    [Pg.340]    [Pg.356]    [Pg.366]    [Pg.98]    [Pg.87]    [Pg.2354]    [Pg.1]    [Pg.202]    [Pg.120]    [Pg.316]    [Pg.357]    [Pg.460]    [Pg.981]    [Pg.2216]    [Pg.451]    [Pg.57]    [Pg.540]    [Pg.577]    [Pg.254]    [Pg.144]    [Pg.76]    [Pg.535]   


SEARCH



Specific component

© 2024 chempedia.info