Introduction to the personal software process
Introduction to the personal software process
Introduction to the team software process
Introduction to the team software process
A Discipline for Software Engineering
A Discipline for Software Engineering
A Critical Analysis of PSP Data Quality: Results from aCase Study
Empirical Software Engineering
A Replicated Empirical Study of the Impact of the Methodsin the PSP on Individual Engineers
Empirical Software Engineering
Teaching the PSP: Challenges and Lessons Learned
IEEE Software
IEEE Software
Psp(sm): a self-improvement process for software engineers
Psp(sm): a self-improvement process for software engineers
Tsp(sm)-coaching development teams
Tsp(sm)-coaching development teams
A Methodology for Collecting Valid Software Engineering Data
IEEE Transactions on Software Engineering
Assessing PSP effect in training disciplined software development: A Plan-Track-Review model
Information and Software Technology
MCPR'11 Proceedings of the Third Mexican conference on Pattern recognition
Methodology Mashups: An Exploration of Processes Used to Maintain Software
Journal of Management Information Systems
Teaching software process modeling
Proceedings of the 2013 International Conference on Software Engineering
Hi-index | 0.00 |
Discipline is an essential prerequisite for the development of large and complex software-intensive systems. However, discipline is also important on the level of individual development activities. A major challenge for teaching disciplined software development is to enable students to experience the benefits of discipline and to overcome the gap between real professional scenarios and scenarios used in software engineering university courses. Students often do not have the chance to internalize what disciplined software development means at both the individual and collaborative level. Therefore, students often feel overwhelmed by the complexity of disciplined development and later on tend to avoid applying the underlying principles. The Personal Software Process (PSP) and the Team Software Process (TSP) are tools designed to help software engineers control, manage, and improve the way they work at both the individual and collaborative level. Both tools have been considered effective means for introducing discipline into the conscience of professional developers. In this paper, we address the meaning of disciplined software development, its benefits, and the challenges of teaching it. We present a quantitative study that demonstrates the benefits of disciplined software development on the individual level and provides further experience and recommendations with PSP and TSP as teaching tools.