1999
DOI: 10.1007/s002360050153
|View full text |Cite
|
Sign up to set email alerts
|

Transformational design of real-time systems Part I: From requirements to program specifications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
15
0

Year Published

1999
1999
2009
2009

Publication Types

Select...
7
2

Relationship

0
9

Authors

Journals

citations
Cited by 17 publications
(15 citation statements)
references
References 30 publications
0
15
0
Order By: Relevance
“…Users can also define their own axioms in PVS for convenience. Work along this line can be found in [24], [25], [117], and [193].…”
Section: Theorem Provingmentioning
confidence: 96%
“…Users can also define their own axioms in PVS for convenience. Work along this line can be found in [24], [25], [117], and [193].…”
Section: Theorem Provingmentioning
confidence: 96%
“…The Provably Correct Systems (ProCoS) project also devised a refinement procedure that starts from the tracebased Duration Calculus and targets occam-like programming language code [18,19]. The ProCoS methodology is fundamentally different from ours, however, because it involves translating from a Duration Calculus specification to the regular expression-based SL language, and from there to the occam-like PL language.…”
Section: Related Workmentioning
confidence: 96%
“…Focussing on specification (19) causes the tool to apply Opening Rule C and extend the current context with the following new hypothesis, among others.…”
Section: Reading the Inputsmentioning
confidence: 99%
“…A systematic development of OCCAM programs from specifications has been studied as part of the European basic research project ProCoS (Provably Correct Systems), see Bowen et al [1996] for an overview and the papers by Schenke [1999], Schenke and Olderog [1999], and Olderog and Rössig [1993] for more details.…”
Section: Bibliographic Remarksmentioning
confidence: 99%