Metric-driven analysis and feedback systems for enabling empirically guided software development
ICSE '91 Proceedings of the 13th international conference on Software engineering
Tolerating Deviations in Process Support Systems via Flexible Enactment of Process Models
IEEE Transactions on Software Engineering
Measuring the software process: statistical process control for software process improvement
Measuring the software process: statistical process control for software process improvement
Validating the ISO/IEC 15504 measures of software development process capability
Journal of Systems and Software
The Rational Unified Process: An Introduction, Second Edition
The Rational Unified Process: An Introduction, Second Edition
Software Engineering Using the Upedu
Software Engineering Using the Upedu
A Comparative Review of Process-Centered Software Engineering Environments
Annals of Software Engineering
Empirical Software Engineering
What Cognitive Activities Are Performed in Student Projects?
CSEET '03 Proceedings of the 16th Conference on Software Engineering Education and Training
Using Prior-Phase Effort Records for Re-estimation During Software Projects
METRICS '03 Proceedings of the 9th International Symposium on Software Metrics
Issues in Using Students in Empirical Studies in Software Engineering Education
METRICS '03 Proceedings of the 9th International Symposium on Software Metrics
Journal of Systems and Software - Special issue: Software engineering education and training
Opportunistic Problem Solving in Software Engineering
IEEE Software
Harmonizing ISO-IEC 15504 and CMMI
Software Process: Improvement and Practice - Special Issue using ISO-IEC 15504
Software project control centers: concepts and approaches
Journal of Systems and Software
Hi-index | 0.00 |
Traditional software engineering processes are composed of practices defined by roles, activities and artifacts. Software developers have their own understanding of practices and their own ways of implementing them, which could result in variations in software development practices. This paper presents an empirical study based on six teams of five students each, involving three different projects. Their process practices are monitored by time slips based on the effort expended on various process-related activities. This study introduces a new 3-pole graphical representation to represent the process patterns of effort expended on the various discipline activities. The purpose of this study is to quantify activity patterns in the actual process, which in turn demonstrates the variability of process performance. This empirical study provides three examples of patterns based on three empirical axes (engineering, coding and V&V). The idea behind this research is to make developers aware that there is wide variability in the actual process, and that process assessments might be weakly related to actual process activities. This study suggests that in-process monitoring is required to control the process activities. In-process monitoring is likely to provide causal information between the actual process activities and the quality of the implemented components.