Proceedings 17th IEEE International Conference on Automated Software Engineering, 2002
DOI: 10.1109/ase.2002.1115016
|View full text |Cite
|
Sign up to set email alerts
|

Towards usable and relevant model checking techniques for the analysis of dependable interactive systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
14
0

Year Published

2006
2006
2017
2017

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 18 publications
(15 citation statements)
references
References 4 publications
1
14
0
Order By: Relevance
“…In a similar fashion we would like to be able to perform some reverse trace analysis to determine what initial configurations and possible paths exist given any of the above properties and some undesired state x? This is similar to work performed in the area of safety critical systems analysis [36].…”
Section: Figure 3: Safety Propertiessupporting
confidence: 63%
“…In a similar fashion we would like to be able to perform some reverse trace analysis to determine what initial configurations and possible paths exist given any of the above properties and some undesired state x? This is similar to work performed in the area of safety critical systems analysis [36].…”
Section: Figure 3: Safety Propertiessupporting
confidence: 63%
“…The technical requirements for an integration of this technique into a design process were identified in Loer and Harrison (2002). Three technical tasks must be addressed: (i) obtaining a model that represents relevant aspects of the interactive system (the device, the environment and user) in a form that can be used by the designer to understand and to analyse the design, (ii) supporting the formulation of property specifications representing the desired requirement and providing mechanisms that are clear in terms of allowing designers to see that a property expresses the requirement that is to be satisfied, (iii) visualising the information provided by model-checking traces so that it can be used to aid the analysis.…”
Section: Bringing the Communities Togethermentioning
confidence: 99%
“…However, their adoption in practice is much lower than it could be. There are three categories of challenges in using C model checkers [1,2]: First, it is difficult to formalize the to-be-verified application-level properties at the level of C, so model checkers are used only to verify implicit C-level properties (e.g., program does no crash, no overflow occurs). However, this is often not enough for end users.…”
Section: Introductionmentioning
confidence: 99%