Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt
- 19 November 2002
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
Abstract
Requirements, specifications, and programs are distinguished by the phenomena they concern. Requirements are about phenomena of the application domain and describe properties of the domain that the machine is required to bring about and maintain. The ...Keywords
This publication has 18 references indexed in Scilit:
- Domain descriptionsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Expressing the relationships between multiple views in requirements specificationPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Formally specifying temporal constraints and error recoveryPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Goal-directed concept acquisition in requirements elicitationPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Goal-directed requirements acquisitionScience of Computer Programming, 1993
- Larch: Languages and Tools for Formal SpecificationPublished by Springer Nature ,1993
- Representing and using nonfunctional requirements: a process-oriented approachIEEE Transactions on Software Engineering, 1992
- The Temporal Logic of Reactive and Concurrent SystemsPublished by Springer Nature ,1992
- Specifying Message Passing and Time-Critical Systems with Temporal LogicLecture Notes in Computer Science, 1992
- Proof of correctness of data representationsActa Informatica, 1972