... Thomas Thelin Corresponding Author Contact Information , E-mail The Corresponding Author and ... more ... Thomas Thelin Corresponding Author Contact Information , E-mail The Corresponding Author and Per Runeson E-mail The Corresponding Author. ... (1992); further studies and improvements are presented in Eick et al., 1993; Vander Wiel and Votta, 1993; Wohlin et al., 1995 ...
15th International Symposium on Software Reliability Engineering, 2004
... The actions are described with typed variables. In MaTeLo, we use a type description compatib... more ... The actions are described with typed variables. In MaTeLo, we use a type description compatible with the following two standards: ASN.1 [14] and TTCN-3 [1]. The types are: integer, real, boolean, object identifier, bit string, octet string, enumerated, and charstring. ...
2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings., 2003
The two most common strategies for verification and validation, inspection and testing, are in a ... more The two most common strategies for verification and validation, inspection and testing, are in a controlled experiment evaluated in terms of their fault detection capabilities. These two techniques are in the previous work compared applied to code. In order to compare the efficiency and effectiveness of these techniques on a higher abstraction level than code, this experiment investigates inspection of
"5th International Workshop on Software Process Simulation and Modeling (ProSim 2004)" W11L Workshop - 26th International Conference on Software Engineering, 2004
Perspective-Based Reading (PBR) is a scenario-based inspection technique where several reviewers ... more Perspective-Based Reading (PBR) is a scenario-based inspection technique where several reviewers read a document from different perspectives (e.g. user, designer, tester). The reading is made according to a special scenario, specific for each perspective. The basic assumption behind PBR is that the perspectives find different defects and a combination of several perspectives detects more defects compared to the same amount of reading with a single perspective. This paper presents a study which analyses the differences in perspectives. The study is a partial replication of previous studies. It is conducted in an academic environment using graduate students as subjects. Each perspective applies a specific modelling technique: use case modelling for the user perspective, equivalence partitioning for the tester perspective and structured analysis for the design perspective. A total of 30 subjects were divided into 3 groups, giving 10 subjects per perspective. The analysis results show that (1) there is no significant difference among the three perspectives in terms of defect detection rate and number of defects found per hour, (2) there is no significant difference in the defect coverage of the three perspectives, and (3) a simulation study shows that 30 subjects is enough to detect relatively small perspective differences with the chosen statistical test. The results suggest that a combination of multiple perspectives may not give higher coverage of the defects compared to single-perspective reading, but further studies are needed to increase the understanding of perspective difference.
Eleventh Annual International Workshop on Software Technology and Engineering Practice, 2003
Software validation is an important activity with the aim to test the requirements of a software ... more Software validation is an important activity with the aim to test the requirements of a software product. Several testing techniques have been developed, and one of these is statistical usage testing (SUT). The main purpose of SUT is to test a software product from a user's point of view. Hence, usage models are designed and then test cases are developed
Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005., 2005
ABSTRACT There is a need to identify factors that affect the result of empirical studies in softw... more ABSTRACT There is a need to identify factors that affect the result of empirical studies in software engineering research. It is still the case that seemingly identical replications of controlled experiments result in different conclusions due to the fact that all factors describing the experiment ...
Proceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04., 2004
... The impact of this study is that the software organization will apply the new readingtechniqu... more ... The impact of this study is that the software organization will apply the new readingtechnique in future requirements inspections. 1. Introduction ... The technique applied by the reviewer to visually examine the artifact is called reading technique. ...
10th International Symposium on Software Metrics, 2004. Proceedings., 2004
... 2. Usage-Based Reading Usage-based reading (UBR) is a reading technique, which focus on the q... more ... 2. Usage-Based Reading Usage-based reading (UBR) is a reading technique, which focus on the quality of the product from a user's point ... The results indicate that CBR is the bestreading technique of the three for object-oriented code in-spections. ...
The main objective of software inspections is to find faults in software documents. The benefits ... more The main objective of software inspections is to find faults in software documents. The benefits of inspections are reported from researchers as well as software organizations. However, inspections are time consuming and the resources may not be sufficient to inspect all documents. Sampling of documents in inspections provides a systematic solution to select what to be inspected in the case resources are not sufficient to inspect everything. The method presented in this paper uses sampling, inspection and resource scheduling to increase the efficiency of an inspection session. A pre-inspection phase is used in order to determine which documents need most inspection time, i.e. which documents contain most faults. Then, the main inspection is focused on these documents. We describe the sampling method and provide empirical evidence, which indicates that the method is appropriate to use. A Monte Carlo simulation is used to evaluate the proposed method and a case study using industrial data is used to validate the simulation model. Furthermore, we discuss the results and important future research in the area of sampling of software inspections.
... Thomas Thelin Corresponding Author Contact Information , E-mail The Corresponding Author and ... more ... Thomas Thelin Corresponding Author Contact Information , E-mail The Corresponding Author and Per Runeson E-mail The Corresponding Author. ... (1992); further studies and improvements are presented in Eick et al., 1993; Vander Wiel and Votta, 1993; Wohlin et al., 1995 ...
... Thomas Thelin Corresponding Author Contact Information , E-mail The Corresponding Author and ... more ... Thomas Thelin Corresponding Author Contact Information , E-mail The Corresponding Author and Per Runeson E-mail The Corresponding Author. ... (1992); further studies and improvements are presented in Eick et al., 1993; Vander Wiel and Votta, 1993; Wohlin et al., 1995 ...
15th International Symposium on Software Reliability Engineering, 2004
... The actions are described with typed variables. In MaTeLo, we use a type description compatib... more ... The actions are described with typed variables. In MaTeLo, we use a type description compatible with the following two standards: ASN.1 [14] and TTCN-3 [1]. The types are: integer, real, boolean, object identifier, bit string, octet string, enumerated, and charstring. ...
2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings., 2003
The two most common strategies for verification and validation, inspection and testing, are in a ... more The two most common strategies for verification and validation, inspection and testing, are in a controlled experiment evaluated in terms of their fault detection capabilities. These two techniques are in the previous work compared applied to code. In order to compare the efficiency and effectiveness of these techniques on a higher abstraction level than code, this experiment investigates inspection of
"5th International Workshop on Software Process Simulation and Modeling (ProSim 2004)" W11L Workshop - 26th International Conference on Software Engineering, 2004
Perspective-Based Reading (PBR) is a scenario-based inspection technique where several reviewers ... more Perspective-Based Reading (PBR) is a scenario-based inspection technique where several reviewers read a document from different perspectives (e.g. user, designer, tester). The reading is made according to a special scenario, specific for each perspective. The basic assumption behind PBR is that the perspectives find different defects and a combination of several perspectives detects more defects compared to the same amount of reading with a single perspective. This paper presents a study which analyses the differences in perspectives. The study is a partial replication of previous studies. It is conducted in an academic environment using graduate students as subjects. Each perspective applies a specific modelling technique: use case modelling for the user perspective, equivalence partitioning for the tester perspective and structured analysis for the design perspective. A total of 30 subjects were divided into 3 groups, giving 10 subjects per perspective. The analysis results show that (1) there is no significant difference among the three perspectives in terms of defect detection rate and number of defects found per hour, (2) there is no significant difference in the defect coverage of the three perspectives, and (3) a simulation study shows that 30 subjects is enough to detect relatively small perspective differences with the chosen statistical test. The results suggest that a combination of multiple perspectives may not give higher coverage of the defects compared to single-perspective reading, but further studies are needed to increase the understanding of perspective difference.
Eleventh Annual International Workshop on Software Technology and Engineering Practice, 2003
Software validation is an important activity with the aim to test the requirements of a software ... more Software validation is an important activity with the aim to test the requirements of a software product. Several testing techniques have been developed, and one of these is statistical usage testing (SUT). The main purpose of SUT is to test a software product from a user's point of view. Hence, usage models are designed and then test cases are developed
Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005., 2005
ABSTRACT There is a need to identify factors that affect the result of empirical studies in softw... more ABSTRACT There is a need to identify factors that affect the result of empirical studies in software engineering research. It is still the case that seemingly identical replications of controlled experiments result in different conclusions due to the fact that all factors describing the experiment ...
Proceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04., 2004
... The impact of this study is that the software organization will apply the new readingtechniqu... more ... The impact of this study is that the software organization will apply the new readingtechnique in future requirements inspections. 1. Introduction ... The technique applied by the reviewer to visually examine the artifact is called reading technique. ...
10th International Symposium on Software Metrics, 2004. Proceedings., 2004
... 2. Usage-Based Reading Usage-based reading (UBR) is a reading technique, which focus on the q... more ... 2. Usage-Based Reading Usage-based reading (UBR) is a reading technique, which focus on the quality of the product from a user's point ... The results indicate that CBR is the bestreading technique of the three for object-oriented code in-spections. ...
The main objective of software inspections is to find faults in software documents. The benefits ... more The main objective of software inspections is to find faults in software documents. The benefits of inspections are reported from researchers as well as software organizations. However, inspections are time consuming and the resources may not be sufficient to inspect all documents. Sampling of documents in inspections provides a systematic solution to select what to be inspected in the case resources are not sufficient to inspect everything. The method presented in this paper uses sampling, inspection and resource scheduling to increase the efficiency of an inspection session. A pre-inspection phase is used in order to determine which documents need most inspection time, i.e. which documents contain most faults. Then, the main inspection is focused on these documents. We describe the sampling method and provide empirical evidence, which indicates that the method is appropriate to use. A Monte Carlo simulation is used to evaluate the proposed method and a case study using industrial data is used to validate the simulation model. Furthermore, we discuss the results and important future research in the area of sampling of software inspections.
... Thomas Thelin Corresponding Author Contact Information , E-mail The Corresponding Author and ... more ... Thomas Thelin Corresponding Author Contact Information , E-mail The Corresponding Author and Per Runeson E-mail The Corresponding Author. ... (1992); further studies and improvements are presented in Eick et al., 1993; Vander Wiel and Votta, 1993; Wohlin et al., 1995 ...
Uploads
Papers by Thomas Thelin