1998
DOI: 10.1007/s002870050102
|View full text |Cite
|
Sign up to set email alerts
|

Qualitätssicherung Software-basierter technischer Systeme - Problembereiche und Lösungsansätze

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
9
0

Year Published

1999
1999
2023
2023

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 14 publications
(10 citation statements)
references
References 0 publications
0
9
0
Order By: Relevance
“…However, thorough verification / validation is vital for testing safetyrelated technical systems [21]. Questions of how to build up confidence or whether or not to apply a specific testing technique are considered in [15] [27].…”
Section: Issues In Testing Dependable Event-based Systemsmentioning
confidence: 99%
See 2 more Smart Citations
“…However, thorough verification / validation is vital for testing safetyrelated technical systems [21]. Questions of how to build up confidence or whether or not to apply a specific testing technique are considered in [15] [27].…”
Section: Issues In Testing Dependable Event-based Systemsmentioning
confidence: 99%
“…With respect to reliability, the FMCEA (Failure Mode, Effects and Criticality Analysis) was used [21]. Load and stress testing determines whether the response time meets the requirement, and the stability of the system degrades if the system is tested to the limits of its memory.…”
Section: Testing Of Non-functional Quality Featuresmentioning
confidence: 99%
See 1 more Smart Citation
“…This thus makes it possible to evaluate design alternatives before their implementation and validation, and not only afterwards. In this way design errors-which constitute up to 40% of software errors and are among the most expensive ones to resolve when discovered only after implementation [17]-can indeed be detected early on in the development, leading to considerable reductions in cost and serious improvements of quality. To the best of our knowledge, this case study is one of the first successful applications of model checking to the verification of publish/subscribe notification services in a groupware setting.…”
Section: Introductionmentioning
confidence: 99%
“…Model checking allows the evaluation of design alternatives before implementation and validationand not just afterwards. In this way, design errors-which constitute up to 40% of software errors and are among the most expensive ones to resolve if discovered after implementation [24]-can be detected in the design phase, leading to considerable reductions in cost and to improved quality.…”
Section: Introductionmentioning
confidence: 99%