Procedure declaration

Fraunhofer Institute for Molecular Biology and Applied Ecology 1999. Revised proposal for a list of priority substances in the context of the water framework directive (COMMPS procedure). Declaration ref. 98/788/3040/DEB/E1. Final report [pdf] 97 p. Available from environment/water/water-framework/preparation priority ... 

The distinction between declarative and procedural knowledge has been abandoned by researchers in Artificial Intelligence as not fruitful for their enterprise. The problem with the distinction from their point of view is that any expression becomes executable, hence procedural, if one programs an interpreter for it conversely, the code for any procedure can be treated as data by other procedures, and hence function declaratively. But these observations ate not directly relevant to cognitive psychology. The question whether the human mind has the procedural-declarative distinction embedded in it or not is an empirical question that cannot be settled by reference to the properties of programming languages. 

Definition 4-1 A specification of a procedure for predicate r//i, denoted Spec r), is composed of a procedure declaration, a type declaration for each parameter, a set of restrictions on parameters, a set of directionalities, and a relation definition. 

This behavioural description requires the buffers contained within the BUFFERS block to enable and disable the input and output ports connecting die random sequence generator to die external bus. The code demonstrates another way of declaring and defining a procedure - bodi the procedure declaration and body are contained within the entity declarative part. 

A procedure is a subprogram that can receive and return any number of values. Like a function, it can consist of both a separate declaration and a body. When storing the procedure in a package, the procedure declaration is placed in the package declaration and die procedure body is stored in the package body. The syntax for both statements is ... 

When equipment or plant is taken out of service, either for maintenance or for repair, it should not be re-introduced into service without being subject to formal acceptance tests that are designed to verify that it meets your declared standard operating conditions. Your procedures need to provide for such activities and for records of the tests to be maintained. 

It is advisable to identify all your quality records within your procedures. This will avoid arguments on what is or is not a quality record, because once you have chosen to identify a record as a quality record you have invoked all the requirements that are addressed in this chapter. Any document which describes the achieved features and characteristics of a product or service are quality records. Those records which will demonstrate that work has been planned, organized, resourced, monitored, verified, and corrected when found deficient are also quality records. The note following the requirement acknowledges that quality records can be in hard copy or held on a computer disk or magnetic tape. Should both forms be held, you will need to declare which are the masters and provide the appropriate security to prevent inadvertent loss or damage (see below). 

The impact of this requirement depends upon what constitutes the specified requirements. The standard does not require you to demonstrate conformance with every requirement of ISO 9001. However, if your customer has invoked ISO 9001 in the contract, this clause requires that you maintain sufficient records to demonstrate compliance. As stated elsewhere in this book, there is no definition clarifying what specified requirements are. If specified requirements are a//the requirements that you have specified in your quality system, your plans, procedures, specifications, etc., this requirement may well be viewed as the most onerous in the standard. A pragmatic approach to take is to declare in your quality manual that the specified requirements are specified customer requirements . 

In standard Pascal, although only in a few implementations of the language, a function or procedure name may also be a parameter to a sub-prograrn. The constants, types, and variables used in a sub-program, as well as those in the main program, must be declared (see following declarations). 

SWS/SWA, in particular, may play an important role in somatic and cognitive restoration, including the consolidation of certain forms of procedural and declarative memory. A substantial diminution in the amount of SWS/SWA occurs across the human lifespan. This decline is beginning already in adolescence and middle-aged adults have only 25% of the SWS observed in young adults, whereas the elderly have almost none. While the clinical importance of these phenomena is unknown, it is reasonable to speculate that they may be related to the increase of sleep complaints associated with aging. 

If a manufacturer has modified their own device they can avail of a special 510(k) procedure for declaring substantial equivalence to their existing device, provided that the intended use or the basic technology has not changed. They must apply design controls and risk analysis to the development process, but the advantage is that they can receive a faster review process. 

It is clear from the preceding discussion that the deficiencies of the existing frequency- and time-domain representations of process trends stem from their procedural character (Cheung and Stephanopoulos, 1990), i.e. they represent trends as the outputs of a computational process, which quite often bears no relationships to the process physics and chemistry. What is needed is a declarative representation, which can capture explicitly all the desirable characteristics of process trends. 

At the completion of a primary screening of a compound library, a collection of hits will be identified that meet or exceed the inhibition percentage cutoff for hit declaration (as described above). The next step is to ensure the validity of these primary screening results through a series of experimental procedures aimed at addressing two aspects of hit validation hit confirmation and hit verification. 

Sampling Procedures for Inspection by Attributes - Part 4 Procedures for Assessment of Declared Quality Levels , ISO 2859-4 2002, International Organization for Standardization (ISO), Geneva, Switzerland, 2002. 

---