The evolution of specification techniques

  • Authors:
  • Anthony I. Wasserman

  • Affiliations:
  • -

  • Venue:
  • ACM '77 Proceedings of the 1977 annual conference
  • Year:
  • 1977

Quantified Score

Hi-index 0.00

Visualization

Abstract

The specifications for a software system may be thought of as a description of what a software system does, as opposed to how it does it. Specifications have typicaly been written in a natural language and provide an external, non-procedural elaboration of the capabilities of a system. A specification may contain user documentation, describing how the system is to be used by its eventual users, and may contain information on how the system is to be integrated with other systems in an execution environment. Alternatively, the specification provides a description of a system which fulfills a set of requirements. The specification of a software system may also include information on how the software system should perform, providing constraints on performance measures such as execution time or utilization of primary or secondary memory. Information concerning performance is frequently essential in determining the feasibility of building a system and in providing the implementer with some basis for making design decisions. Often, specifications concerning performance can be used to identify program modules which must be optimized or to recognize that no special efforts are required to achieve the stated performance objectives.