Abstract
A cyber-physical system comprises an assemblage of given material and human domains together with the computing element or elements introduced to control them. Requirements for such systems can be understood as properties of system behaviours: the central task of system development is to design the overall behaviour of the system to satisfy these requirements. This overall behaviour can be regarded as a structure of simplified independent behaviours, modified and recombined to address their interactions. A widely adopted approach to requirements perversely conceals this structure.
Similar content being viewed by others
References
Dijkstra EW (1968) A case against the go to statement. EWD 215, published as a letter to the Editor (Go to statement considered harmful): communications of the ACM 11(3):147–148
Harel D (2009) Statecharts in the making: a personal account. Commun ACM 52(3):67–75
Heimdahl MPE (2005) Let’s not forget validation. In: Meyer B, Woodcock J (eds) Proceedings of VSTTE workshop, ETH Zurich, 2005, Springer LNCS 4171
Heimdahl MPE (2007) Safety and software intensive systems: challenges old and new. In: Proceedings of FOSE’07 workshop, pp 137–152, IEEE
Jackson M (1995) Software requirements and specifications: a lexicon of principle, practices and prejudices Addison-Wesley
Miller SP, Tribble AC, Whalen MW, Heimdahl MPE (2006) Proving the shalls. Int J Softw Tools Technol Transfer 8(4–5):303–319
Poincaré H (1908) Science et Méthode; Flammarion; translated by Francis Maitland, Nelson, 1914, Dover, 1952
Acknowledgments
I thank David Harel, Mats Heimdahl and Daniel Jackson for helpful comments on an earlier draft of this paper.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
About this article
Cite this article
Jackson, M. Topsy-turvy requirements. Requirements Eng 19, 107–111 (2014). https://doi.org/10.1007/s00766-013-0179-2
Received:
Accepted:
Published:
Issue Date:
DOI: https://doi.org/10.1007/s00766-013-0179-2