Supporting requirements verification using XSLT

Durán, Amador; Ruiz–Cortés, Antonio; Corchuelo, Rafael; Toro, Miguel

doi:10.1109/icre.2002.1048519

Cited by 17 publications

(28 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As described in [4], the experience of some of the authors in the verification of use cases developed by students using REM led to the definition of several metrics-based, defect Fig. 3, the OCL definition of the metrics used in the verification heuristics, based on the metamodel in Fig.…”

Section: Verification Heuristicsmentioning

confidence: 99%

“…In this paper, the evolution of the use case metamodel implemented in the REM requirements management tool [3] is described. This evolution has been driven not by a theoretical analysis but by the analysis of empirical data obtained during the assessment of several metrics-based verification heuristics for use cases developed by some of the authors (for a description of the verification heuristics and their implementation in REM using XSLT, see [4]; for their empirical assessment and review, see [5]). This empirical analysis has revealed that some common defects in use cases developed by software engineering students had their roots in the underlying REM metamodel, therefore making its evolution necessary in order to increase requirements quality.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Empirically Driven Use Case Metamodel Evolution

Durán¹,

Bernárdez²,

Genero³

et al. 2004

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Metamodel evolution is rarely driven by empirical evidences of metamodel drawbacks. In this paper, the evolution of the use case metamodel used by the publicly available requirements management tool REM is presented. This evolution has been driven by the analysis of empirical data obtained during the assessment of several metrics-based verification heuristics for use cases developed by some of the authors and previously presented in other international fora. The empirical analysis has made evident that some common defects found in use cases developed by software engineering students were caused not only by their lack of experience but also by the expressive limitations imposed by the underlying use case metamodel used in REM. Once these limitations were clearly identified, a number of evolutionary changes were proposed to the REM use case metamodel in order to increase use case quality, i.e. to avoid those situations in which the metamodel were the cause of defects in use case specifications.

show abstract

Section: Verification Heuristicsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Empirically Driven Use Case Metamodel Evolution

Durán¹,

Bernárdez²,

Genero³

et al. 2004

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…These metrics have been defined for the use case model of REM [9], a requirements management tool that can automatically calculate its values. In this model, a use case is basically seen as a sequence of steps.…”

Section: Mbr a Metric-based Reading Techniquementioning

confidence: 99%

“…The detailed aspects of the development of this technique are collected in [8,9]. The intuition behind these heuristics is that there are several use case metrics (see The heuristics and their corresponding metrics usual ranges were proposed after analyzing 414 use cases which have been developed by students, as described in [8].…”

Section: Mbr a Metric-based Reading Techniquementioning

confidence: 99%

“…Since the main purpose of use cases technique is to specify part of the functional requirements of the system to be built [4], a use case defect detection technique is defined and empirically improved in our previous works [5,9] (see section 2). This technique called MBR (Metric-Based Reading) is based on a set of heuristics whose usage during the requirements inspection leads this process in a systematic approach that should improve the effectiveness and efficiency of requirements inspection.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

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

Bernárdez

Genero

Durán

et al.

10th International Symposium on Software Metrics, 2004. Proceedings.

Self Cite

View full text Add to dashboard Cite

show abstract

A model-based approach for specifying changes in replications of empirical studies in computer Science

Cruz¹,

Bernárdez²,

Durán³

et al. 2022

Computing

View full text Add to dashboard Cite

The need of replicating empirical studies in Computer Science is widely recognized among the research community. It is essential to report the changes of each replication to promote not only the comprehensibility of the evolution of the experimental validity across a family of studies, but also replicability itself. Unfortunately, the lack of proposals for systematic reporting of changes in replications undermines these desirable objectives. The main goal of the work presented in this article is to provide researchers in Computer Science with a systematic tool-supported approach for the specification and reporting of changes in the replications of their empirical studies. Applying Design Science Research, we have developed and validated a composite artifact consisting of (i) a metamodel that formalizes all the relevant concepts related to replications and their changes; (ii) templates and linguistic patterns that facilitate their reporting; and (iii) a proof-of-concept model-based software tool that supports the proposed approach. For its validation, we have carried out a multiple case study that includes 9 families of empirical studies not only from Computer Science, but also from an area as different as Agrobiology , to check the external validity of our approach. The 9 families encompass 23 replication studies and a total of 92 replication changes, for which we have analyzed the suitability of our proposal. The multiple case study revealed some initial limitations of our approach related to threats to experimental validity and context variables. After several improvement iterations on the artifact, all of the 92 replication changes could be properly specified, including also their qualitatively estimated effects on experimental validity and their corresponding visualization. Our proposal for the specification of replication changes seems to fit the needs not only of replications in Computer Science, but also in other research areas. Nevertheless, further research is needed to improve it and disseminate its use among the research community.

show abstract

Supporting requirements verification using XSLT

Abstract: Abstract

Cited by 17 publications

References 7 publications

Empirically Driven Use Case Metamodel Evolution

Empirically Driven Use Case Metamodel Evolution

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

A model-based approach for specifying changes in replications of empirical studies in computer Science

Contact Info

Product

Resources

About