1995
DOI: 10.1002/spe.4380250104
|View full text |Cite
|
Sign up to set email alerts
|

A requirements capture method and its use in an air traffic control application

Abstract: This paper describes our experience in capturing, using a formal specification language, a model of the knowledge-intensive domain of oceanic air traffic control. This model is intended to form part of the requirements specification for a decision support system for air traffic controllers. We give an overview of the methods we used in analysing the scope of the domain, choosing an appropriate formalism, developing a domain model, and validating the model in various ways. Central to the method was the developm… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
11
0

Year Published

1997
1997
2019
2019

Publication Types

Select...
4
3
3

Relationship

1
9

Authors

Journals

citations
Cited by 15 publications
(11 citation statements)
references
References 2 publications
0
11
0
Order By: Relevance
“…To drive the research we used an air traffic control application where a domain theory had been captured in a previous project called FAROAS [21]. The theory, called the CPS , represents aircraft separation criteria and conflict prediction procedures relating to airspace over the North East Atlantic and consisted of axioms in 2 IMProving the quality of formal REquirements SpecificationS msl.…”
Section: Introductionmentioning
confidence: 99%
“…To drive the research we used an air traffic control application where a domain theory had been captured in a previous project called FAROAS [21]. The theory, called the CPS , represents aircraft separation criteria and conflict prediction procedures relating to airspace over the North East Atlantic and consisted of axioms in 2 IMProving the quality of formal REquirements SpecificationS msl.…”
Section: Introductionmentioning
confidence: 99%
“…This allows the model's notation, or an equivalent 'pseudo-natural language' form, to be understandable to non-computing professionals (overcoming at least to some extent Leveson et al's criticism of the use of formal systems in requirements analysis [10]). We chose Many Sorted First Order logic (here abbreviated to 'msl') to encode the model for a number of reasons, detailed in [14]. As msl is a very general language we customised it chiefly through the imaginative and precise use of syntactic constructs.…”
Section: Producing a Customised Modelmentioning
confidence: 99%
“…It draws on ideas from other areas of computing, and is inspired particularly from our work in requirements capture 0-8186-7686496 $05.00 0 1996 IEEE [17] and formal methods [21]. The method's benefits include (i) it can be used to systematically create models for classical planners, (ii) it produces a tight model (the property of a valid state is well defined, and operators can be checked for their operational consistency), (iii) it forces attention on the semantic level of object rather than the literal (iv) we have empirical evidence that the model compilation tools associated with the method produce a huge speed-up in plan generation.…”
Section: Introductionmentioning
confidence: 99%