Aktuelle Änderungen Printable View Änderungen Bearbeiten
ExtendingPython > LexicalClosures > Closures > ClojureOnDotNet > MetaProgramming > PSPad2Wordpress > GoogleChartsAPI > CurriculumVitae > MarketingPython > AndersHejlsberg > FunctionObjects > Functor > TrampolineStyle > MaintainableCode > AbstractDataType > OopVsAdt > DesignByContractClear TrailThe idea of DBC is to specify that part of the behaviour which must remain unchanged (by means of assertions and suchlike). This leads to a more precise notion of subtype. [1]
The use of pre and post conditions allows the development of software to be thought of as an implicit, or explicit, contract between the calling environment and the called subprogram. The calling environment fulfils its part of the contract by ensuring that it only ever calls the subprogram with a set of actual parameters which comply with the pre-condition. The subprogram in its turn fulfils the contract by ensuring that if it is supplied with acceptable input parameters it will always provide results which comply with its post-condition. That is to say that it will fulfil its advertised specification to transform its input data into the output data.