Do interactive systems need specifications?
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.
KeywordsRequirement Engineering Interactive System Current Drive Semantic Level Requirement Engineer
Unable to display preview. Download preview PDF.
- 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–52Google 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
- 4.Jackson, M. A.: Software Requirements and Specifications, ACM Press Addison Wesley, 1997Google 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