Abstract
There is a wide gap between informal requirements and a formal object-oriented specification. To help bridge this gap, we propose that a formal and executable user-centred model should be constructed initially. The user-centred model, which specifies the behaviour that the environment expects from the system, is expressed in terms of agent views and gives very early feedback to the requirements' capture process. Once the user-centred model has been validated with respect to the environment, it can be used as a step in the construction and validation of the formal object-oriented specification.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
Bolognesi, T. and Brinksma, E. 1987. Introduction to the ISO specification language LOTOS. Computer Networks and ISDN Systems, 14:25–59.
Brinksma, E. 1988. LOTOS—A Formal Description Technique Based on the Temporal Ordering of Observational Behaviour. ISO 8807.
Clark, R. and Moreira, A. 1997. Using a formal user-centred model to build a formal system-centred model. Computing Science and Mathematics, University of Stirling, TR 140.
Coad, P. and Yourdon, E. 1991. Object Oriented Analysis (2nd edition). Yourdon Press, Prentice-Hall.
Easterbrook, S. and Nuseibeh, B. 1996. Using viewpoints for inconsistency management. Software Engineering Journal, 11:31–43.
Eertink, H. and Wolz, D. 1993. Symbolic execution of LOTOS specifications, Formal Description Techniques V. North-Holland, pp. 295–310.
Ehrig, H. and Mahr, B. 1985. Fundamentals of Algebraic Specifications. Springer-Verlag, vol. 1.
Glinz, P. 1995. An integrated formal model of scenarios based on statecharts. Proc. ESEC'95, Springer-Verlag LNCS 989, pp. 254–271.
Hoare, C. 1985. Communicating Sequential Processes. Prentice-Hall.
Hsia, P., Samuel, J., Gao, J., Kung, D., Toyoshima, Y., and Chen, C. 1994. Formal approach to scenario analysis. IEEE Software, (3):33–41.
Jacobson, I. 1992. Object-Oriented Software Engineering. Addison-Wesley.
Milner, R. 1989. Communication and Concurrency. Prentice-Hall.
Moreira, A. and Clark, R. 1994. Combining object-oriented analysis and formal description techniques. Eighth European Conference on Object-Oriented Programming: ECOOP'94, Bologna, Italy, Springer-Verlag LNCS 821, pp. 344–364.
Moreira, A. and Clark, R. 1996a. LOTOS in the object-oriented analysis process, Formal Methods in Object Technology. Springer-Verlag, Chap. 3, pp. 33–46.
Moreira, A. and Clark, R. 1996b. Adding rigour to object-oriented analysis. Software Engineering Journal, 11:270–280.
Quemada, J., Azcorra, A., and Pavon, S. 1995. The LOTOSphere design methodology, LOTOSphere: Software Development with LOTOS. Kluwer Academic Publishers, pp. 29–58.
Rubin, K. and Goldberg, A. 1992. Object behaviour analysis. Comm. ACM, 35:48–62.
Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., and Lorensen, W. 1991. Object-Oriented Modelling and Design. Prentice-Hall.
Rumbaugh, J. 1994. Getting started: Using use cases to capture requirements. J. Object Oriented Programming, 7(9):8–23.
Shlaer, S. and Mellor, S. 1992. Object Lifecycles—Modeling the World in States. Prentice-Hall.
Somé, S., Dssouli, R., and Vaucher, J. 1996. Towards an automation of requirements engineering using scenarios. J. Computing and Information, 2:1070–1092.
Turner, K.J. and van Sinderen, M. 1995. LOTOS specification style for OSI, LOTOSphere: Software Development with LOTOS. Kluwer Academic Publishers, pp. 137–159.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Clark, R.G., Moreira, A.M. Formal Specifications of User Requirements. Automated Software Engineering 6, 217–232 (1999). https://doi.org/10.1023/A:1008752609513
Issue Date:
DOI: https://doi.org/10.1023/A:1008752609513