Skip to main content

Do interactive systems need specifications?

  • Conference paper

Part of the book series: Eurographics ((EUROGRAPH))

Abstract

The obvious advantages of prototyping and incremental development for interactive systems lead some people to believe that specifications of such systems are unnecessary or even harmful. I question whether there really is a conflict between specifications and prototypes. In fact the two schools have more in common than is usually supposed. Both specifications and prototypes can be understood as theories about the system to be developed. Both have important and complementary roles in development.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Abowd, G. D., Dix, A. J.: Integrating status and event phenomena in formal specifications of interactive systems. Proceedings of the 2nd ACM SIGSOFT Symposium on the Foundations of Software Engineering, Software Engineering Notes 19 (5), 44–52

    Google Scholar 

  2. Buckingham Shum, S., Blandford, A., Duke. D., Good, J., May, J., Paternó, F., Young, R. M.: Multidisciplinary modelling for User-centred system design: An air-traffic control case study. In: Sasse, A. Cunningham, J., Winder, R. (eds): People and Computers XI. Proceedings of HCI’96. London, Springer Verlag. pp. 201 – 219.

    Google Scholar 

  3. Hall, A.: Using formal methods to develop an ATC information system, IEEE Software 13 (2), March 1996, 66 – 76

    Article  Google Scholar 

  4. Jackson, M. A.: Software Requirements and Specifications, ACM Press Addison Wesley, 1997

    Google Scholar 

  5. Knight, J. C. Brilliant, S. S.: Preliminary evaluation of a formal approach to user interface specification. In: Bowen, J. P., Hinchey, M. G. (eds): ZUM’97: The Z Formal Specification Notation. Springer 1997 (Lecture Notes in Computer Science, vol 1212, pp. 329 – 346 )

    Google Scholar 

  6. Popper, K.: The Logic of Scientific Discovery.

    Google Scholar 

  7. Sutcliffe, A.: A technique combination approach to requirements engineering, Proceedings of the 3rd International Symposium on Requirements Engineering, January 1997, IEEE Computer Society Press, 65–74.

    Google Scholar 

  8. Zave, P., Jackson, M.: Where do operations come from? A multiparadigm specification technique, IEEE Transactions on Software Engineering, 22 (7) July 1996, 508 – 528

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 1997 Springer-Verlag/Wien

About this paper

Cite this paper

Hall, A. (1997). Do interactive systems need specifications?. In: Harrison, M.D., Torres, J.C. (eds) Design, Specification and Verification of Interactive Systems ’97. Eurographics. Springer, Vienna. https://doi.org/10.1007/978-3-7091-6878-3_1

Download citation

  • DOI: https://doi.org/10.1007/978-3-7091-6878-3_1

  • Publisher Name: Springer, Vienna

  • Print ISBN: 978-3-211-83055-0

  • Online ISBN: 978-3-7091-6878-3

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics