Statemate: a working environment for the development of complex reactive systems
ICSE '88 Proceedings of the 10th international conference on Software engineering
Managing the software process
Foundations for the Arcadia environment architecture
SDE 3 Proceedings of the third ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments
ISPW '88 Proceedings of the 4th international software process workshop on Representing and enacting the software process
The software engineering laboratory: an operational software experience factory
ICSE '92 Proceedings of the 14th international conference on Software engineering
People, Organizations, and Process Improvement
IEEE Software
Metric-driven analysis and feedback systems for enabling empirically guided software development
ICSE '91 Proceedings of the 13th international conference on Software engineering
5th ISPW 5th Intl Software Process Workshop
The software process and software environments (panel session)
ICSE '85 Proceedings of the 8th international conference on Software engineering
Modeling Concurrency in Rule-Based Development Environments
IEEE Expert: Intelligent Systems and Their Applications
Automating process discovery through event-data analysis
Proceedings of the 17th international conference on Software engineering
Cost-Effective Analysis of In-Place Software Processes
IEEE Transactions on Software Engineering
Discovering models of software processes from event-based data
ACM Transactions on Software Engineering and Methodology (TOSEM)
Software process validation: quantitatively measuring the correspondence of a process to a model
ACM Transactions on Software Engineering and Methodology (TOSEM)
OMEGA: a language and system for on-line monitoring of software-intensive processes
ACM SIGSOFT Software Engineering Notes
An Empirical Investigation Of Software Project ScheduleBehaviour
Empirical Software Engineering
On the discovery of process models from their instances
Decision Support Systems
A design for evidence - based soft research
REBSE '05 Proceedings of the 2005 workshop on Realising evidence-based software engineering
Agile management of uncertain requirements via generalizations: a case study
Proceedings of the 2004 workshop on Quantitative techniques for software agile process
Representing the behaviour of software projects using multi-dimensional timelines
Information and Software Technology
Information and Software Technology
ACM SIGSOFT Software Engineering Notes
Hi-index | 0.00 |
Features are often the basic unit of development for a very large software system and represent long-term efforts, spanning up to several years from inception to actual use. Developing an experiment to monitor (by means of sampling) such lengthy processes requires a great deal of care in order to minimize casts and to maximize benefits. Just as prototyping is often a necessary auxiliary step in a large-scale, long-term development effort, so, too, is prototyping a necessary step in the development of a large-scale, long-term process monitoring experiment. Therefore, we have prototyped our experiment using a representative process and reconstructed data from a large and rich feature development. This approach has yielded three interesting sets of results. First, we reconstructed a 30-month time diary for the lead engineer of a feature composed of both hardware and software. These data represent the daily state (where the lead engineer spent the majority of his time) for a complete cycle of the development process. Second, we found that we needed to modify our experimental design. Our initial set of states did not represent the data as well as we had hoped. This is exemplified by the fact that the "Other" category is too large. Finally, the data provide evidence for both a waterfall view and an interactive, cyclic view of software development. We conclude that the prototyping effort is a necessary part of developing and installing any large-scale process monitoring experiment.