Reference implementation

In the software development process, a reference implementation (or, less frequently, sample implementation or model implementation) is the standard from which all other implementations and corresponding customizations are derived. An improvement to a reference implementation reflects an unchanging specification. Conversely, a failed attempt at an implementation may prove that the specification is not suitable and needs improvement itself. Testing the implementation-vs.-specification relationship further enhances the production's inter-process efficiencies:

A reference implementation is, in general, an implementation of a specification to be used as a definitive interpretation for that specification (This definition is a bit grandiloquent but works). During the development of the ... conformance test suite, at least one relatively trusted implementation of each interface is necessary to (1) discover errors or ambiguities in the specification, and (2) validate the correct functioning of the test suite.[1]
Characteristics of a Reference Implementation:
  1. Developed concurrently with the specification and test suite;
  2. Verifies that specification is implementable;
  3. Enables the test suite to be tested;
  4. Serves as a Gold Standard against which other implementations can be measured;
  5. Helps to clarify the intent of the specification in situations where conformance tests are inadequate[2]

Reference implementations of algorithms, for instance cryptographic algorithms, are often the result or the input of standardization processes. In this function they are often dedicated to the public domain with their source code as public domain software. Examples are the first CERN's httpd,[3] Serpent cipher, base64 variants,[4] and SHA-3.[5] The Openwall Project maintains a list of several algorithms with their reference source code in the public domain.[6]

A reference implementation may or may not be production quality. For example, the Fraunhofer reference implementation of the MP3 standard usually does not compare favorably to other common implementations, such as LAME, in listening tests that determine sound quality.

References

  1. ↑ Dalci, Eric; Fong, Elizabeth; Goldfine, Alan (2003). Requirements for GSC-IS Reference Implementations. National Institute of Standards and Technology, Information Technology Laboratory.
  2. ↑ Curran, Patrick (2003). Conformance Testing: An Industry Perspective. Sun Microsystems.
  3. ↑ The birth of the web Licensing the web on cern.ch (2014)
  4. ↑ libb64 on sourceforge
  5. ↑ KeccakReferenceAndOptimized-3.2.zip mainReference.c "The Keccak sponge function, designed by Guido Bertoni, Joan Daemen, Michaël Peeters and Gilles Van Assche. For more information, feedback or questions, please refer to our website: http://keccak.noekeon.org/Implementation by the designers, hereby denoted as "the implementer". To the extent possible under law, the implementer has waived all copyright and related or neighboring rights to the source code in this file. http://creativecommons.org/publicdomain/zero/1.0/"
  6. ↑ Source code snippets and frameworks placed in the public domain on openwall.info
This article is issued from Wikipedia - version of the 5/25/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.