Formal methods are usually intended to include all the details of the final system in the specification, with the aim of proving that it possesses certain mathematical properties. Telecommunications services are large and complex, making detailed formal specification impractical with current technology (Mataga & Zave, 1993). Fortunately, the behaviour of the services provided to telephone users is often simple enough to sketch and much of the complexity stems from details of the implementation of services. The principal characteristics of a service can be approximated by simple varieties of logic, even though the services themselves cannot usually be formalised. We address the problem of determining these services, from a library of services accompanied by their behavioural approximations, which might be appropriate for re-use, by using graphical input examples to sketch the behaviour desired and a case-based approach to identify behaviourally similar telecommunications services. The simple logic employed also enables the user to evaluate the behaviour of the services without being confronted with the formal representation itself. The CABS system can also perform simple verifications against the input examples and identify when the service does not include all the behaviour exemplified in the input examples. Seventeen telephone features such as call waiting, redirect call, call back and three way call, have been explored and formalised. These services are stored in the case library as cases, each consisting of a set of transition rules. Graphical input examples have been sketched for these features and CABS identifies the corresponding formalised services with high accuracy. If there are no input examples matching the desired behaviour, the logic from the input examples can be used as a starting point for producing a new case.
[1]
Alan Bundy.
Tutorial Notes: Reasoning about Logic Programs
,
1992,
Logic Programming Summer School.
[2]
Janis A. Bubenko,et al.
Challenges in requirements engineering
,
1995,
Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).
[3]
P Funk,et al.
Case-Based Selection of Requirements Specifications for Telecommunications Systems
,
1994
.
[4]
Mike Uschold,et al.
Building Ontologies: Towards a Unified Methodology
,
1996
.
[5]
Michael Jackson,et al.
Four dark corners of requirements engineering
,
1997,
TSEM.
[6]
Anthony Hall,et al.
Seven myths of formal methods
,
1990,
IEEE Software.
[7]
Ian D. Watson,et al.
Applying case-based reasoning - techniques for the enterprise systems
,
1997
.
[8]
David Harel,et al.
Statecharts: A Visual Formalism for Complex Systems
,
1987,
Sci. Comput. Program..
[9]
David C. Gooding,et al.
Knowledge Acquisition with Visual Functional Programming
,
1993,
EKAW.
[10]
Daniela E. Herlea Damian.
Challenges in Requirements Engineering
,
2000
.
[11]
Daniel E. O'Leary,et al.
Verification and validation of case-based systems
,
1993
.
[12]
Roel Wieringa,et al.
Requirements Engineering: Frameworks for Understanding
,
1996
.