Achieving quality and schedule targets continue to be serious problems in the software industry. This "software crisis" is not new, and is not helped by the fact that new computer science/engineering graduates often have little experience with schedule estimation. Poor development habits acquired early on are not always corrected by the one or two software engineering courses commonly taught in upper level courses. We are developing ClockIt, a tool and supporting methodology that seek to improve student software development practices starting with introductory courses. As an extension or plug-in to an existing integrated development environment (IDE) ClockIt is being designed to monitor and log student development activities. It will also allow estimation of student effort by project or component, and provide reports and visualizations of student "development profiles." We believe that analysis and presentation of development profiles will provide instructors useful visual and quantitative support for teaching sound development practices. The same information will also provide students with immediate feedback with little conceptual overhead
[1]
Watts S. Humphrey,et al.
Introduction to the Personal Software Process
,
1996
.
[2]
Philip M. Johnson,et al.
Beyond the Personal Software Process: Metrics collection and analysis for the differently disciplined
,
2003,
25th International Conference on Software Engineering, 2003. Proceedings..
[3]
Qin Zhang,et al.
Practical automated process and product metric collection and analysis in a classroom setting: lessons learned from Hackystat-UH
,
2004,
Proceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04..
[4]
Philip M. Johnson,et al.
The Personal Software Process: A Cautionary Case Study
,
1998,
IEEE Softw..
[5]
John C. Knight.
Focusing Software Education on Engineering
,
2004,
CSEE&T.