1997
DOI: 10.1007/3-540-63531-9_16
|View full text |Cite
|
Sign up to set email alerts
|

Providing automated support to deductive analysis of time critical systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
10
0

Year Published

1999
1999
2000
2000

Publication Types

Select...
5
2
1

Relationship

1
7

Authors

Journals

citations
Cited by 10 publications
(11 citation statements)
references
References 7 publications
1
10
0
Order By: Relevance
“…Several prototype tools are available to support the method: a graphical interactive editor supporting the documentation of all phases, from requirement specification to architectural design; a test case generation tool [15,16]; a correctness prover -or disprover-based on the translation of the TRIO formalism into PVS [1].…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…Several prototype tools are available to support the method: a graphical interactive editor supporting the documentation of all phases, from requirement specification to architectural design; a test case generation tool [15,16]; a correctness prover -or disprover-based on the translation of the TRIO formalism into PVS [1].…”
Section: Discussionmentioning
confidence: 99%
“…In the rest of the paper the following convention is adopted: 1 The courier font denotes TC meta-classes.…”
Section: The Tc Languagementioning
confidence: 99%
“…In some cases, a repeated pattern becomes a single proof step. For example, the TAME strategy called APPLY INV LEMMA, with the appropriate arguments, introduces the desired invariant lemma, instantiates it, expands the invariant, and dis- 1 Here and below, a name in bold capital letters denotes a TAME strategy.…”
Section: Proofmentioning
confidence: 99%
“…• Theorem proving. Given a set of TRIO axioms and a candidate TRIO theorem, a semiautomatic tool helps deciding whether the candidate theorem can actually be derived from the axioms [AG&97]. This technique can be used to a) validate specifications by deriving some logical consequences thereof to check whether they are consistent with user expectations; b) verify that a lower level specification fulfills the requirements stated in an upper level; c) verify that the code implementation is correct with respect to requirement specification.…”
Section: Validation and Verificationmentioning
confidence: 99%