Specification Qualities

  • V. S. Alagar
  • K. Periyasamy
Part of the Texts in Computer Science book series (TCS)


The process model introduced in Chap.  2 integrates the practice of formal method into all phases of life-cycle activities. Given the current maturity of formal methods, it is reasonable to assume that this process model is both practical and justified. Software development activity in this process model includes the formalization of software requirements specification, design specification, program specification, domain and environment specification, and analysis at different stages. The goal of this chapter is to explore the quality characteristics of these specifications that depend on the formal methods and the processes used in creating them.


Global Position System Formal Method Specification Language Conformance Attribute Specification Document 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. 1.
    Alagar VS, Kourkopoulos D (1994) (In)completeness in specifications. Inf Softw Technol 36(6):331–342 CrossRefGoogle Scholar
  2. 2.
    Balzer R, Goldman N (1981) Principles of good software specification and their implications for specification languages. In: National computer conference, pp 393–400 Google Scholar
  3. 3.
    Bauer FL (1976) Programming as an evolutionary process. In: Proceedings of the second international conference on software engineering, San Francisco, CA, pp 223–234 Google Scholar
  4. 4.
    Bauer FL, Bauer M, Partsch P, Pepper P (1981) Report on a wide-spectrum language for program specification and development. Technical Report TUM-18104, Technical University, Munich, May 1981 Google Scholar
  5. 5.
    Craigen D (1990) The Verdi reference manual. Technical Report TR-90-S429-09, Odyssey Research Associates, February 1990 Google Scholar
  6. 6.
    De Vito BL, Roberts L (1996) Using formal methods to assist in the requirements analysis of the space shuttle GPS change request. NASA Report 4752, Prepared for Langley Research Center Google Scholar
  7. 7.
    Hausen HL (2007) Quality specification, testing and certification of bespoken, open source and commercial off-the-shelf systems. In: IFIP international federation for information processing. Springer, Boston Google Scholar
  8. 8.
    ISO (1991) ISO/IEC:9126 information technology-software product evaluation-quality characteristics and guidelines for their use. International Organization for Standardization (ISO) Google Scholar
  9. 9.
    IEEE (1998) IEEE recommended practice for software requirements specifications. IEEE Std 830-1998 (revision of IEEE Std 830-1993) Google Scholar
  10. 10.
    Kahn BK, Strong DM, Wang RY (2002) Information quality benchmarks: product and service performance. Commun ACM 45(4):184–192 CrossRefGoogle Scholar
  11. 11.
    Klausner A, Konchan TE (1980) Rapid prototyping and requirements specification using PDS. In: Gehani N, McGettrick AD (eds) Software specification techniques. Addison Wesley, Reading Google Scholar
  12. 12.
    Wing J (1995) Hints to specifiers. Manuscript CMU-Cs-95-118R Google Scholar

Copyright information

© Springer-Verlag London Limited 2011

Authors and Affiliations

  1. 1.Dept. Computer Science and Software Eng.Concordia UniversityMontrealCanada
  2. 2.Computer Science DepartmentUniversity of Wisconsin-La CrosseLa CrosseUSA

Personalised recommendations