Formal Specifications of User Requirements

Authors:
Robert G. Clark;Ana M. D. Moreira
Affiliations:
Department of Computing Science and Mathematics, University of Stirling, Stirling FK9 4LA, Scotland, UK. rgc@cs.stir.ac.uk;Departamento de Informática, Faculdade de Ciências e Tecnologia, Universidade Nova de Lisboa, 2825 Monte da Caparica, Portugal. amm@di.fct.unl.pt
Venue:
Automated Software Engineering
Year:
1999

Citing 14
Cited 0

Communicating sequential processes

Communicating sequential processes
Introduction to the ISO specification language LOTOS

Computer Networks and ISDN Systems - Special Issue: Protocol Specification and Testing
Object-oriented software engineering

Object-oriented software engineering
Object lifecycles: modeling the world in states

Object lifecycles: modeling the world in states
Object-oriented modeling and design

Object-oriented modeling and design
Object-oriented analysis (2nd ed.)

Object-oriented analysis (2nd ed.)
Object behavior analysis

Communications of the ACM - Special issue on analysis and modeling in software development
Formal Approach to Scenario Analysis

IEEE Software
Communication and Concurrency

Communication and Concurrency
LOTOSphere: Software Development with Lotos

LOTOSphere: Software Development with Lotos
Fundamentals of Algebraic Specification I

Fundamentals of Algebraic Specification I
An Integrated Formal Model of Scenarios Based on Statecharts

Proceedings of the 5th European Software Engineering Conference
Combining Object-Oriented Analysis and Formal Description Techniques

ECOOP '94 Proceedings of the 8th European Conference on Object-Oriented Programming
Symbolic execution of LOTOS specifications

FORTE '92 Proceedings of the IFIP TC6/WG6.1 Fifth International Conference on Formal Description Techniques for Distributed Systems and Communication Protocols: Formal Description Techniques, V

Quantified Score

Hi-index	0.00

Visualization

Abstract

There is a wide gap between informal requirements anda formal object-oriented specification.To help bridge this gap, we propose that a formal and executableuser-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 ofagent views and gives very early feedback to the requirements‘ captureprocess.Once the user-centred model has been validated with respect to theenvironment, it can be used as a step in the construction andvalidation of the formal object-oriented specification.