Download jurnal

Download Jurnal penelitian yang diambil dari IEEE transaction dan Empirical Software Engineering:

An Extended Replication of an Experiment for Assessing Methods for Software Requirements Inspections

KRISTIAN SANDAHL ZeLab, Ericsson Radio Systems AB, Box 12 48, S-581 12 Link¨oping, Sweden
OLA BLOMKVIST Quality Technology and Management, Department of Mechanical Engineering, Link¨oping University, S-581 83 Link¨oping, Sweden
JOACHIM KARLSSON Focal Point AB, Teknikringen 1E, S-583 30 Link¨oping, Sweden
CHRISTIAN KRYSANDER Department of Computer and Information Science, Link¨oping University, S-581 83 Link¨oping, Sweden
MIKAEL LINDVALL Department of Computer and Information Science, Link¨oping University, S-581 83 Link¨oping, Sweden
NICLAS OHLSSON Department of Computer and Information Science, Link¨oping University, S-581 83 Link¨oping, Sweden

Abstract. We have performed an extended replication of the Porter-Votta-Basili experiment comparing the Scenario method and the Checklist method for inspecting requirements specifications using identical instruments. The experiment has been conducted in our educational context represented by a more general definition of a defect compared to the original defect list. Our study involving 24 undergraduate students manipulated three independent variables: detection method, requirements specification, and the order of the inspections. The dependent variable measured is the defect detection rate. We found the requirements specification inspected and not the detection method to be the most probable explanation for the variance in defect detection rate. This suggests that it is important to gather knowledge of how a requirements specification can convey an understandable view of the product and to adapt inspection methods accordingly. Contrary to the original experiment, we can not significantly support the superiority of the Scenario method. This is in accordance with a replication conducted by Fusaro, Lanubile and Visaggio, and might be explained by the lack of individual defect detection skill of our less experienced subjects.

Keywords: Controlled experiments, inspections, replicated study, method evaluation

Download this Journal here

Investigating the Role of Use Cases in the Construction of Class Diagrams

BENTE ANDA bentea@simula.no
DAG I. K. SJØBERG

Simula Research Laboratory, P.O. Box 134, 1325 Lysaker, Norway

Abstack

Several approaches have been proposed for the transition from functional requirements to objectoriented design. In a use case-driven development process, the use cases are important input for the identification of classes and their methods. There is, however, no established, empirically validated technique for the transition from use cases to class diagrams. One recommended technique is to derive classes by analyzing the use cases. It has, nevertheless, been reported that this technique leads to problems, such as the developers missing requirements and mistaking requirements for design. An alternative technique is to identify classes from a textual requirements specification and subsequently apply the use case model to validate the resulting class diagram. This paper describes two controlled experiments conducted to investigate these two approaches to applying use case models in an object-oriented design process. The first experiment was conducted with 53 students as subjects. Half of the subjects used a professional modelling tool; the other half used pen and paper. The second experiment was conducted with 22 professional software developers as subjects, all of whom used one of several modelling tools. The first experiment showed that applying use cases to validate class diagrams constructed from textual requirements led to more complete class diagrams than did the derivation of classes from a use case model. In the second experiment, however, we found no such difference between the two techniques. In both experiments, deriving class diagrams from the use cases led to a better structure of the class diagrams. The results of the experiments therefore show that the technique chosen for the transition from use cases to class diagrams affects the quality of the class diagrams, but also that the effects of the techniques depend on the categories of developer applying it and on the tool with which the technique is applied.

Keywords: UML, use cases, object-oriented design, modelling tool, controlled experiment, replicated experiment.

Download this Journal here