The merit of this approximation is that it neither imposes any rigid functional form of specification on the structure of utility function nor assumes a specific form of the demand system, for example, a double-log demand model.
Advantages of this form of specification are that the designer does not describe the control flow in terms of explicit states or control variables and that the designer does not describe a particular form of implementation.
If, however, it disallows modifications for computability (see "The limitations of computers"), or requires arbitrary blessing for one form of specification over another (see "Models that represent reality") it may have the opposite effect.
As a consequence, prior knowledge, which may be available in form of specifications, standards and norms cannot be reused and the question what has been learned remains unanswered.
This information, which is usually in the form of specifications, drawings, or schedule information, enables prompt identification, processing, and communication of discrepancies between actual and expected performance.
Textual specifications, that in the past were the original form of specifications, have been substituted by reference software which became the starting point of any design flow leading to implementation.
The results of the country workshops would include the form of specifications for the future scenarios according to the differences of the partner countries (e.g., specifics coming from the post-communist state or conservative WS model today, etc).
In the quest for efficiency, the logical form of the specification has been obscured by concentration on low-level details.
This language and the machine description (MD) libraries and tools are used to write complex machine descriptions and capture the design in a form of hierarchical specification, where each level in the hierarchy can be placed in a separate MD file.
Standards don't have to take the form of technical specifications.
While executable artifacts exist in the form of executable specifications (content and workflow schemata) in the content repository, too, the majority of executable artifacts in the analyzed system are classical software artifacts (programs written in Tcl, Javascript, SQL and HTML templates as used by OpenACS).
