Abstract data types and the development of data structures
Communications of the ACM
Communications of the ACM
Monitors: an operating system structuring concept
Communications of the ACM
On the criteria to be used in decomposing systems into modules
Communications of the ACM
Operating system principles
Analyzing medium-scale software development
ICSE '78 Proceedings of the 3rd international conference on Software engineering
A comparison of techniques for the specification of external system behavior
Communications of the ACM
Understanding and Controlling Software Costs
IEEE Transactions on Software Engineering
Recent advances in software measurement (abstract and references for talk)
ICSE '90 Proceedings of the 12th international conference on Software engineering
An experiment to assess different defect detection methods for software requirements inspections
ICSE '94 Proceedings of the 16th international conference on Software engineering
Further Experiences with Scenarios and Checklists
Empirical Software Engineering
Empirical Software Engineering
Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment
IEEE Transactions on Software Engineering
Requirements engineering: In search of the dependent variables
Information and Software Technology
A systematic literature review to identify and classify software requirement errors
Information and Software Technology
A Framework for Predicting Person-Effort on Requirements Changes
Proceedings of the 2006 conference on New Trends in Software Methodologies, Tools and Techniques: Proceedings of the fifth SoMeT_06
Characterizing software architecture changes: A systematic review
Information and Software Technology
Evolving defect "folklore": a cross-study analysis of software defect behavior
SPW'05 Proceedings of the 2005 international conference on Unifying the Software Process Spectrum
| Hi-index | 0.02 |
We describe in this paper an effective data collection method for evaluating software development methodologies, from definition of the objectives of the data collection to analysis of the results. We show how the data analysis can answer questions with respect to how successfully the goals of the development methodology are met. The A-7 requirements document is used as an example. We provide the results of data analyses conducted partway through the A-7 flight software development cycle, and discuss the utility of information obtained by such partial analyses. Results from the study show that data collection is feasible and useful when performed as part of configuration control, that data distributions based on partial data provide useful feedback to the developers, and that the A-7 Requirements Document is easily maintained and changed.