Before establishing a specification, procurement practitioners should clearly understand: Specifications and other standards can be imposed outside, as described above, but also internal manufacturing and quality specifications. These exist not only for food or pharmaceutical products, but also for processing machines, quality processes, packaging, logistics (cold chain) etc. And are exemplary according to iso 14134 and ISO 15609. [22] [23] In the development of the system (material, software or enterprise), an architectural specification is the documentation that describes the structure, behavior and other views of this system. A specification describes the requirements of supply. This is the basis of all offers and therefore the basis of a contract. A specification becomes an essential contract management document, which is used to ensure that the selected supplier provides what is indicated. It is therefore necessary to define clearly and precisely what a supplier expects of it in terms of outputs or functional and performance requirements. Data systems that process, store and transmit information on food and food need formal specifications for the presentation of food and food data in order to function effectively and efficiently. Web service specifications are often under the aegis of a quality management system.

[29] These types of documents define how to write a particular document, which may include the systems of a document name, version, layout, referencing, structuring, appearance, appearance, language, copyright, hierarchy or format, etc., but this is not limited to that. [32] [33] [34] In software development, a functional specification (including functional specifications or functional specifications or document functional specifications (FSDs) is the set of documentation describing the behavior of a computer program or larger software system. The documentation usually describes different entries that can be made available to the software system and how the system reacts to those inputs. The types of specifications for UK projects can be divided into two main descriptive and performance categories. Prescribed specifications define requirements using generic or proprietary descriptions of what is needed, while technical performance specifications focus on results, not component characteristics. Although there is a tendency to think that the „specifications of a drawing“ deviate from the drawings in the event of a discrepancy between the text document and the drawings, the actual intent must be explicitly stated in the contract between the owner and the contractor. The Standard AIA (American Institute of Architects) and the EJCDC (Engineering Joint Contract Documents Documents Committee) stipulate that the drawings and specifications are complementary and together provide the information necessary for a complete installation. Many public bodies, such as the Naval Facilities Command (NAVFAC), indicate that the specifications announced the designs.

This is based on the idea that words are easier for a jury (or mediator) to interpret than drawings in the event of a dispute. Specification standards can be provided by government authorities, standards bodies (SAE, AWS, NIST, ASTM, ISO, CEN, DoD, etc.), industry organizations, businesses and others. With regard to specifications, the UK standards are as follows: when a pharmaceutical product does not fall under the above standards, it can be assessed by the additional source of pharmacopoeia from other countries, by industrial specifications or by a standardised formula such as the specification of Programme A, the definition of what a computer program expects to do.