A controlled experiment for evaluating a metric-based reading technique for requirements inspection

Bernárdez, Beatriz; Genero, Marcela; Durán, Amador; Toro, Miguel

doi:10.1109/metric.2004.1357908

Cited by 8 publications

(5 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Indeed, there are few controlled experiments about use cases to be found in the literature at all; for instance [11,12,13] which are concerned with guidelines for writing good use cases, [14] looking at the transition from use cases to class diagrams, and [15,16,17] investigating inspection of use cases. Looking at conceptual modeling more generally, there are experiments comparing the effectiveness of representation languages, for instance ER or EER diagrams with relational tuples, one well known example being [18].…”

Section: Related Workmentioning

confidence: 99%

Safety Hazard Identification by Misuse Cases: Experimental Comparison of Text and Diagrams

Stålhane

Sindre

Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

Abstract. In general, diagrams and text are both considered to have their advantages and disadvantages for the representation of use case models, but this is rarely investigated experimentally. This paper describes a controlled experiment where we compare safety hazard identification by means of misuse cases based on use case diagrams and textual use cases. The experiment participants found use case diagrams and textual use cases equally easy to use. In most cases those who used textual use cases were able to identify more failure modes or threats. The main reason for this seems to be that use cases encourage analysts to specifically focus on threats related to the functions mentioned in the use case, and textual use cases include more functional details than diagrams. The focus is decided by information in each use case which will thus decide the number of threats identified.

show abstract

Section: Related Workmentioning

confidence: 99%

Safety Hazard Identification by Misuse Cases: Experimental Comparison of Text and Diagrams

Stålhane

Sindre

Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

show abstract

“…Using a controlled experiment, a metricbased reading technique for inspecting requirements was proposed in [17]. A study on faults and failures based on empirical data is presented in [18].…”

Section: Background and Related Workmentioning

confidence: 99%

Errors on Space Software Requirements: A Field Study and Application Scenarios

Véras

Villani

Ambrosio

et al. 2010

2010 IEEE 21st International Symposium on Software Reliability Engineering

View full text Add to dashboard Cite

This paper presents a field study on real errors found in space software requirements documents. The goal is to understand and characterize the most frequent types of requirement problems in this critical application domain. To classify the software requirement errors analyzed we initially used a well-known existing taxonomy that was later extended in order to allow a more thorough analysis. The results of the study show a high rate of requirement errors (9.5 errors per each 100 requirements), which is surprising if we consider that the focus of the work is critical embedded software. Besides the characterization of the most frequent types of errors, the paper also proposes a set of operators that define how to inject realistic errors in requirement documents. This may be used in several scenarios, including: evaluating and training reviewers, estimating the number of requirement errors in real specifications, defining checklists for quick requirement verification, and defining benchmarks for requirements specifications.

show abstract

“…Uma observação, que merece atenção, é que a série de experimentos sobre UBR foi realizada pela mesma equipe que definiu a técnica, o que poderia ter acarretado inconscientemente o viés dos resultados [Silva e Travassos 2004]. MBR (Metric-Based Reading) -MBR [Bernardez et al 2004] é uma técnica de leitura para detecção de defeitos em modelos de casos de uso. Descrição -MBR adota um conjunto de heurísticas para orientar os revisores a detectarem defeitos em modelos de casos de uso.…”

Section: Ubr (Usage-basedunclassified

Técnicas de Leitura de Software: Uma Revisão Sistemática

Mafra¹,

Travassos²

2005

Anais Do XIX Simpósio Brasileiro De Engenharia De Software (SBES 2005)

View full text Add to dashboard Cite

A orientação a objetos (OO) alcançou considerável sucesso no desenvolvimento industrial. Entretanto, a condução de atividades de verificação e validação em software OO ainda é um desafio. Acreditamos que a utilização de técnicas de leitura em inspeções de software seja uma alternativa viável para garantir a qualidade do software OO. Em vista disso, o presente artigo descreve os resultados de uma revisão sistemática conduzida com o objetivo de identificar, analisar e avaliar técnicas de leitura aplicáveis na garantia de qualidade no desenvolvimento de sistemas OO, cujos resultados apontam para novos desafios de pesquisa nesta área.

show abstract

A controlled experiment for evaluating a metric-based reading technique for requirements inspection

Abstract: Abstract

Cited by 8 publications

References 21 publications

Safety Hazard Identification by Misuse Cases: Experimental Comparison of Text and Diagrams

Safety Hazard Identification by Misuse Cases: Experimental Comparison of Text and Diagrams

Errors on Space Software Requirements: A Field Study and Application Scenarios

Técnicas de Leitura de Software: Uma Revisão Sistemática

Contact Info

Product

Resources

About