A field study of the software design process for large systems
Communications of the ACM
Lessons learned from modeling the dynamics of software development
Communications of the ACM
Knowledge exploited by experts during software system design
International Journal of Man-Machine Studies - What programmers know
Why is Software Late? An Empirical Study of Reasons for Delay in Software Development
IEEE Transactions on Software Engineering
Estimeetings: Development Estimates and a Front-End Process for a Large Project
IEEE Transactions on Software Engineering
Science and Substance: A Challenge to Software Engineers
IEEE Software
Prototyping a Process Monitoring Experiment
IEEE Transactions on Software Engineering
Software requirements & specifications: a lexicon of practice, principles and prejudices
Software requirements & specifications: a lexicon of practice, principles and prejudices
An Experiment to Assess the Cost-Benefits of Code Inspections in Large Scale Software Development
IEEE Transactions on Software Engineering
Understanding the sources of variation in software inspections
ACM Transactions on Software Engineering and Methodology (TOSEM)
Cost-Effective Analysis of In-Place Software Processes
IEEE Transactions on Software Engineering
Qualitative Methods in Empirical Studies of Software Engineering
IEEE Transactions on Software Engineering
Empirical analysis in software process simulation modeling
Journal of Systems and Software - Special issue on empirical studies of software development and evolution
Case Studies for Method and Tool Evaluation
IEEE Software
Quantitative Analysis of Faults and Failures in a Complex Software System
IEEE Transactions on Software Engineering
Preliminary guidelines for empirical research in software engineering
IEEE Transactions on Software Engineering
EWSPT '96 Proceedings of the 5th European Workshop on Software Process Technology
Studying Work Practices to Assist Tool Design in Software Engineering
IWPC '98 Proceedings of the 6th International Workshop on Program Comprehension
Sometimes you need to see through walls: a field study of application programming interfaces
CSCW '04 Proceedings of the 2004 ACM conference on Computer supported cooperative work
IT Failure Rates--70% or 10-15%?
IEEE Software
Sampling Open Source Projects from Portals: Some Preliminary Investigations
METRICS '05 Proceedings of the 11th IEEE International Software Metrics Symposium
A Survey of Controlled Experiments in Software Engineering
IEEE Transactions on Software Engineering
Proceedings of the 2006 AVI workshop on BEyond time and errors: novel evaluation methods for information visualization
Information and Software Technology
Ethnographically-informed empirical studies of software practice
Information and Software Technology
A Systematic Review of Software Development Cost Estimation Studies
IEEE Transactions on Software Engineering
A Replicated Quantitative Analysis of Fault Distributions in Complex Software Systems
IEEE Transactions on Software Engineering
ESEM '07 Proceedings of the First International Symposium on Empirical Software Engineering and Measurement
An empirical study of software developers' management of dependencies and changes
Proceedings of the 30th international conference on Software engineering
A Replicated Survey of IT Software Project Failures
IEEE Software
Designing the design process: exploiting opportunistic thoughts
Human-Computer Interaction
Guidelines for conducting and reporting case study research in software engineering
Empirical Software Engineering
How large are software cost overruns? A review of the 1994 CHAOS report
Information and Software Technology
The Linux kernel as a case study in software evolution
Journal of Systems and Software
Representing the behaviour of software projects using multi-dimensional timelines
Information and Software Technology
A review of studies on expert estimation of software development effort
Journal of Systems and Software
Hi-index | 0.01 |
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.