University of Hertfordshire

From the same journal

Standard

The longitudinal, chronological case study research strategy : a definition, and an example from IBM Hursley Park. / Rainer, A.

In: Information and Software Technology, Vol. 53, No. 7, 2011, p. 730-746.

Research output: Contribution to journalArticlepeer-review

Harvard

APA

Vancouver

Author

Bibtex

@article{1c3302dc52cd4436a41586a564e7c240,
title = "The longitudinal, chronological case study research strategy: a definition, and an example from IBM Hursley Park",
abstract = "Context: There is surprisingly little empirical software engineering research (ESER) that has analysed and reported the rich, fine-grained behaviour of phenomena over time using qualitative and quantitative data. The ESER community also increasingly recognises the need to develop theories of software engineering phenomena e.g. theories of the actual behaviour of software projects at the level of the project and over time. Objective: To examine the use of the longitudinal, chronological case study (LCCS) as a research strategy for investigating the rich, fine-grained behaviour of phenomena over time using qualitative and quantitative data. Method: Review the methodological literature on longitudinal case study. Define the LCCS and demonstrate the development and application of the LCCS research strategy to the investigation of Project C, a software development project at IBM Hursley Park. Use the study to consider prospects for LCCSs, and to make progress on a theory of software project behaviour. Results: LCCSs appear to provide insights that are hard to achieve using existing research strategies, such as the survey study. The LCCS strategy has basic requirements that data is time-indexed, relatively fine-grained and collected contemporaneous to the events to which the data refer. Preliminary progress is made on a theory of software project behaviour. Conclusion: LCCS appears well suited to analysing and reporting rich, fine-grained behaviour of phenomena over time.",
keywords = "chronology, deadline effect, longitudinal case study, qualitative data, software project, theory development",
author = "A. Rainer",
note = "Original article can be found at : http://www.sciencedirect.com/ Copyright Elsevier",
year = "2011",
doi = "10.1016/j.infsof.2011.01.003",
language = "English",
volume = "53",
pages = "730--746",
journal = "Information and Software Technology",
issn = "0950-5849",
publisher = "Elsevier",
number = "7",

}

RIS

TY - JOUR

T1 - The longitudinal, chronological case study research strategy

T2 - a definition, and an example from IBM Hursley Park

AU - Rainer, A.

N1 - Original article can be found at : http://www.sciencedirect.com/ Copyright Elsevier

PY - 2011

Y1 - 2011

N2 - Context: There is surprisingly little empirical software engineering research (ESER) that has analysed and reported the rich, fine-grained behaviour of phenomena over time using qualitative and quantitative data. The ESER community also increasingly recognises the need to develop theories of software engineering phenomena e.g. theories of the actual behaviour of software projects at the level of the project and over time. Objective: To examine the use of the longitudinal, chronological case study (LCCS) as a research strategy for investigating the rich, fine-grained behaviour of phenomena over time using qualitative and quantitative data. Method: Review the methodological literature on longitudinal case study. Define the LCCS and demonstrate the development and application of the LCCS research strategy to the investigation of Project C, a software development project at IBM Hursley Park. Use the study to consider prospects for LCCSs, and to make progress on a theory of software project behaviour. Results: LCCSs appear to provide insights that are hard to achieve using existing research strategies, such as the survey study. The LCCS strategy has basic requirements that data is time-indexed, relatively fine-grained and collected contemporaneous to the events to which the data refer. Preliminary progress is made on a theory of software project behaviour. Conclusion: LCCS appears well suited to analysing and reporting rich, fine-grained behaviour of phenomena over time.

AB - Context: There is surprisingly little empirical software engineering research (ESER) that has analysed and reported the rich, fine-grained behaviour of phenomena over time using qualitative and quantitative data. The ESER community also increasingly recognises the need to develop theories of software engineering phenomena e.g. theories of the actual behaviour of software projects at the level of the project and over time. Objective: To examine the use of the longitudinal, chronological case study (LCCS) as a research strategy for investigating the rich, fine-grained behaviour of phenomena over time using qualitative and quantitative data. Method: Review the methodological literature on longitudinal case study. Define the LCCS and demonstrate the development and application of the LCCS research strategy to the investigation of Project C, a software development project at IBM Hursley Park. Use the study to consider prospects for LCCSs, and to make progress on a theory of software project behaviour. Results: LCCSs appear to provide insights that are hard to achieve using existing research strategies, such as the survey study. The LCCS strategy has basic requirements that data is time-indexed, relatively fine-grained and collected contemporaneous to the events to which the data refer. Preliminary progress is made on a theory of software project behaviour. Conclusion: LCCS appears well suited to analysing and reporting rich, fine-grained behaviour of phenomena over time.

KW - chronology

KW - deadline effect

KW - longitudinal case study

KW - qualitative data

KW - software project

KW - theory development

U2 - 10.1016/j.infsof.2011.01.003

DO - 10.1016/j.infsof.2011.01.003

M3 - Article

VL - 53

SP - 730

EP - 746

JO - Information and Software Technology

JF - Information and Software Technology

SN - 0950-5849

IS - 7

ER -