Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Annabella Loconsole

dblp:69/4553 · DBLP profile ↗
← Back
7ranked-venue papers
4as first author
0since 2021 · last 2014
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 7 · 4 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 50% Empirical software engineering · 50%

Topics — the 2 heaviest of 2, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering › software engineering research methodology
industrial case study
0.012004
Empirical Studies on Requirement Management Measures · ICSE 2004
Requirements engineering and software design
requirements management
0.012004
Empirical Studies on Requirement Management Measures · ICSE 2004

Methods — techniques the papers use, named apart from their topics

statistical prediction · 0.0empirical measurement · 0.0
YearPublicationVenuePosition
2014 Challenges and practices in aligning requirements with verification and validation: a case study of six companies
Elizabeth Bjarnason, Per Runeson, Markus Borg, Michael Unterkalmsteiner, Emelie Engström, Björn Regnell, Giedre Sabaliauskaite, Annabella Loconsole, Tony Gorschek, Robert Feldt
Empir. Softw. Eng.8
2010 Challenges in Aligning Requirements Engineering and Verification in a Large-Scale Industrial Context
Giedre Sabaliauskaite, Annabella Loconsole, Emelie Engström, Michael Unterkalmsteiner, Björn Regnell, Per Runeson, Tony Gorschek, Robert Feldt
REFSQ2
2008 A Correlational Study on Four Measures of Requirements Volatility
Annabella Loconsole
EASE1
2007 Are Size Measures Better Than Expert Judgment? An Industrial Case Study on Requirements Volatility
abstract
Expert judgment is a common estimation approach in industry. However, there is very little research on the accuracy of expert judgment outside the area of effort estimation. In this paper, we present an industrial case study investigating subjective and objective measures of requirementss volatility. Data was collected in retrospect for all use cases of a medium-size software project. In addition, we determined subjective volatility by interviewing developers and managers of the project. Our data analysis show that structural measures perform better than expert judgment in estimating the total number of changes to use case based requirements. These results confirm results from a previous case study by the authors and suggest that project managers should not rely on expert judgment alone for decision making.
Annabella Loconsole, Jürgen Börstler
APSEC1
2007 A controlled empirical evaluation of a requirements abstraction model
Tony Gorschek, Mikael Svahnberg, Andreas Borg, Annabella Loconsole, Jürgen Börstler, Kristian Sandahl, Magnus Eriksson
Inf. Softw. Technol.4
2005 An Industrial Case Study on Requirements Volatility Measures
abstract
Requirements volatility is an important risk factor for software projects. Software measures can help in quantifying and predicting this risk. In this paper, we present an industrial case study that investigated measures of volatility for a medium size software project. The goal of the study was twofold: 1) to empirically validate a set of measures associated with the volatility of use case models (UCM); 2) to investigate the correlation between subjective and objective volatility. Measurement data was collected in retrospect for all use case models of the software project. In addition, we determined subjective volatility by interviewing stakeholders of the project. Our data analysis showed a high correlation between our measures of size of UCM and total number of changes, indicating that the measures of size of UCMs are good indicators of requirements volatility. No correlations was found between subjective and objective volatility. These results suggest that project managers at this company should measure their projects because of the risk to take wrong decisions based on their own and the developer's perceptions.
Annabella Loconsole, Jürgen Börstler
APSEC1
2004 Empirical Studies on Requirement Management Measures
abstract
The goal of this research is to demonstrate that a subset of a set of 38 requirements management measures are good predictors of stability and volatility of requirements and change requests. At the time of writing we have theoretically validated ten of these 38 measures. We are currently planning and performing an industrial case study where we want to reach the goal described above.
Annabella Loconsole
ICSE1