| 1. |
|
|
| 2. |
- Bratthall, L., et al.
(author)
-
Survey of lead-time challenges in the development and evolution of distributed real-time systems
- 2000
-
In: Information and Software Technology. - 0950-5849. ; 42:13, s. 947-958
-
Journal article (peer-reviewed)abstract
- This paper presents a survey that identifies lead-time consumption in the development and evolution of distributed real-time systems DRTSs. Data has been collected through questionnaires, focused interviews and non-directive interviews with senior designers. Quantitative data has been analyzed using the Analytic Hierarchical Process (AHP). A trend in the 11 organizations is that there is a statistically significant shift of the main lead-time burden from programming to integration and testing, when distributing systems. From this, it is concluded that processes, tools and technologies that either reduce the need for or the time for testing have an impact on the development and evolution of lead-time of DRTSs.
|
|
| 3. |
- Höst, Martin, et al.
(author)
-
A Subjective Effort Estimation Experiment
- 1997
-
In: Information and Software Technology. - 0950-5849. ; 39:11, s. 755-762
-
Journal article (peer-reviewed)abstract
- Abstract Effort estimation is difficult in general, and in software development it becomes even more complicated if the software process is changed. In this paper a number of alternative interview-based effort estimation methods is presented. The main focus of the paper is to present an experiment in which software engineers were asked to use different methods to estimate the actual effort it would take to perform a number of tasks. The result from the subjective data is compared with the actual outcome from performing the tasks.
|
|
| 4. |
- Karlsson, Joachim, et al.
(author)
-
An evaluation of methods for prioritizing software requirements
- 1998
-
In: Information and Software Technology. - 0950-5849. ; 39:14-15, s. 939-947
-
Journal article (peer-reviewed)abstract
- This article describes an evaluation of six different methods for prioritizing software requirements. Based on the quality requirements for a telephony system, the authors individually used all six methods on separate occasions to prioritize the requirements. The methods were then characterized according to a number of criteria from a user's perspective. We found the analytic hierarchy process to be the most promising method, although it may be problematic to scale-up. In an industrial follow-up study we used the analytic hierarchy process to further investigate its applicability. We found that the process is demanding but worth the effort because of its ability to provide reliable results, promote knowledge transfer and create consensus among project members.
|
|
| 5. |
- Ohlsson, Magnus C., et al.
(author)
-
A project effort estimation study
- 1998
-
In: Information and Software Technology. - 0950-5849. ; 40:14, s. 831-839
-
Journal article (peer-reviewed)abstract
- This paper outlines a four step effort estimation study and focuses on the first and second step. The four steps are formulated to successively introduce a more formal effort experience base. The objective of the study is to evaluate the needed formalism to improve effort estimation and to study different approaches to record and reuse experiences from effort planning in software projects. In the first step (including seven projects), the objective is to compare estimation of effort based on a rough figure (indicating approximate size of the projects) with an informal experience base. The objective of the second step is on reuse of experiences from an effort experience base, where the outcomes of seven previous projects were stored. Seven new projects are planned based on the previous experiences. The plans are, after project completion, compared with the initial plans and with the data from six out of the seven new projects, to plan the seventh. It is clear from the studies that effort estimation is difficult and that the mean estimation error is in the range of 14%-19% independent of the approach used. Further, it is concluded that the best estimates are obtained when the projects use the previous experience and complement this information with their own thoughts and opinions. Finally, it is concluded that data collection is not enough in itself, the data collected must be processed, i.e. interpreted, generalized and synthesized into a reusable form.
|
|
| 6. |
|
|
| 7. |
- Thelin, Thomas, et al.
(author)
-
Confidence intervals for capture-recapture estimations in software inspections
- 2002
-
In: Information and Software Technology. - 0950-5849. ; 44:12, s. 683-702
-
Journal article (peer-reviewed)abstract
- Software inspections are an efficient method to detect faults in software artefacts. In order to estimate the fault content remaining after inspections, a method called capture-recapture has been introduced. Most research published in fault content estimations for software inspections has focused upon point estimations. However, confidence intervals provide more information of the estimation results and are thus preferable. This paper replicates a capture -recapture study and investigates confidence intervals for capture -recapture estimators using data sets from two recently conducted software inspection experiments. Furthermore, a discussion of practical application of capture-recapture with confidence intervals is provided. In capture-recapture, used for software inspection, most research papers have reported Mh-JK to be the best estimator, but only one study has investigated its subestimators. In addition, confidence intervals based on the log-normal distribution have not been evaluated before with software inspection data. These two investigations together with a discussion provide the main contribution of this paper. The result confirms the conclusions of the replicated study and shows when confidence intervals for capture-recapture estimators can be trusted. (C) 2002 Elsevier Science B.V. All rights reserved.
|
|
| 8. |
- Thelin, Thomas, et al.
(author)
-
Usage-Based Reading - An Experiment to Guide Reviewers with Use Cases
- 2002
-
In: Information and Software Technology. - 0950-5849. ; 43:15, s. 925-938
-
Journal article (peer-reviewed)abstract
- Reading methods for software inspections are used for aiding reviewers to focus on special aspects in a software artefact. Many experiments have been conducted for checklist-based reading and scenario-based reading concluding that the focus is important for software reviewers. This paper describes and evaluates a reading technique called usage-based reading (UBR). UBR utilises prioritised use cases to guide reviewers through an inspection. More importantly, UBR drives the reviewers to focus on the software parts that are most important for the customer. An experiment was conducted on 27 third year Bachelor's software engineering students, where one group used use cases sorted in a prioritised order and the control group used randomly ordered use cases. The main result is that reviewers in the group with prioritised use cases are significantly more efficient and effective in detecting the most critical faults from a customer's point of view. Consequently, UBR has the potential to become an important reading technique. Future extensions to the reading technique are suggested and experiences gained from the experiment to support replications are provided.
|
|
| 9. |
|
|
| 10. |
- Wohlin, Claes, et al.
(author)
-
Subjective Evaluation as a Tool for Learning from Software Project Success
- 2000
-
In: Information and Software Technology. - 0950-5849. ; 42:14, s. 983-992
-
Journal article (peer-reviewed)abstract
- This paper presents a method for using subjective factors to evaluate project success. The method is based on collection of subjective measures with respect to project characteristics and project success indicators. The paper introduces a new classification scheme for assessing software projects. Further, it is illustrated how the method may be used to predict software success using subjective measures of project characteristics. The classification scheme is illustrated in two case studies. The results are positive and encouraging for future development of the approach.
|
|
