Reference implementation: Difference between revisions

Content deleted Content added
SG495 (talk | contribs)
Removed a spurious part of the testing quote: "(This definition is a bit grandiloquent but works)" is not part of the quote in the linked source.
m Testing: clean up
Line 12:
[[Software testing|Testing]] the implementation-vs-specification relationship further enhances the [[Product family engineering|production]]'s inter-process efficiencies:
 
{{quoteblockquote|A reference implementation is, in general, an implementation of a specification to be used as a definitive interpretation for that specification. During the development of the&nbsp;... 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.<ref>Dalci, Eric; Fong, Elizabeth; Goldfine, Alan (2003). ''Requirements for GSC-IS Reference Implementations''. National Institute of Standards and Technology, Information Technology Laboratory. [https://web.archive.org/web/20060928231404/http://xw2k.sdct.itl.nist.gov/smartcard/document/ref-imp51.pdf Requirements for GSC-IS Reference Implementations]</ref>}}
Requirements for GSC-IS Reference Implementations]</ref>}}
 
{{quoteblockquote|Characteristics of a Reference Implementation:
# Developed concurrently with the specification and test suite;
# Verifies that specification is implementable;