8. REFERENCES
[1] J. Kim and C. R. Carlson, “Design units-a layered approach
for design driven software development,” Inf. Softw.
Technol., vol. 43, no. 9, pp. 539 – 49.
[2] N. Medvidovic, P. Grunbacher, A. Egyed, and B. W. Boehm,
“Bridging models across the software lifecycle,” in Journal
of Systems and Software, 2003, vol. 68, no. 3, pp. 199–215.
[3] J. van Gurp and J. Bosch, “Design erosion: problems and
causes,” J. Syst. Softw., vol. 61, no. 2, pp. 105 – 19.
[4] M. Lavallee and P. N. Robillard, “Causes of premature aging
during software development: An observational study,” in
IWPSE-EVOL’11 - Proceedings of the 12th International
Workshop on Principles on Software Evolution, 2011, pp.
61–70.
[5] S. Vaucher, F. Khomh, N. Moha, and Y.-G. Gueheneuc,
“Tracking design smells: Lessons from a study of God
classes,” in Proceedings - Working Conference on Reverse
Engineering, WCRE, 2009, pp. 145–154.
[6] H. P. Breivold, I. Crnkovic, and M. Larsson, “A systematic
review of software architecture evolution research,” Inf.
Softw. Technol., vol. 54, no. 1, pp. 16–40, 2012. [7] L. De Silva and D. Balasubramaniam, “Controlling software
architecture erosion: A survey,” J. Syst. Softw., vol. 85, no. 1,
pp. 132–151, 2012.
[8] W. Li, L. Etzkorn, C. Davis, and J. Talburt, “An empirical
study of object-oriented system evolution,” Inf. Softw.
Technol., vol. 42, no. 6, pp. 373 – 81.
[9] G. C. Murphy, D. Notkin, and K. J. Sullivan, “Software
reflexion models: Bridging the gap between design and
implementation,” IEEE Trans. Softw. Eng., vol. 27, no. 4, pp.
364–380, 2001.
[10] G. Antoniol, B. Caprile, A. Potrich, and P. Tonella, “Design-
code traceability for object-oriented systems,” Ann. Softw.
Eng., vol. 9, pp. 35–58.
[11] S. Chaki, A. Diaz-Pace, D. Garlan, A. Gurfinkel, and I.
Ozkaya, “Towards engineered architecture evolution,” in
Proceedings - International Conference on Software
Engineering, 2009, pp. 1–6.
[12] M. V. Mäntylä and C. Lassenius, “Subjective Evaluation of
Software Evolvability Using Code Smells: An Empirical
Study,” Empir. Softw. Eng., vol. 11, no. 395–431, 2006.
[13] Microsoft, Microsoft Application Architecture Guide, 2nd
editio. 2009, p. 560.
[14] P. N. Robillard, P. Kruchten, and P. D’Astous, Software
Engineering Process with the UPEDU. Boston, MA:
Addison-Wesley, 2003.
[15] E. Germain and P. N. Robillard, “What cognitive activities
are performed in student projects?,” in Proceedings 16th
Conference on Software Engineering Education and
Training, pp. 224 – 31.
[16] E. Germain and P. N. Robillard, “Towards software process
patterns: An empirical analysis of the behavior of student
teams,” Inf. Softw. Technol., vol. 50, no. 11, pp. 1088–1097,
2008.
[17] P. Kruchten, The Rational Unified Process: An Introduction,
2nd ed. Reading, Massachusetts: Addison-Wesley, 2000.
[18] K. Dhambri, H. Sahraoui, and P. Poulin, “Visual detection of
design anomalies,” in Proceedings of the European
Conference on Software Maintenance and Reengineering,
CSMR, 2008, pp. 279–283.
[19] Y. Zhou, B. Xu, and H. Leung, “On the ability of complexity
metrics to predict fault-prone classes in object-oriented
systems,” J. Syst. Softw., vol. 83, no. 4, pp. 660–674, 2010.
[20] P. N. Robillard, “Opportunistic problem solving in software
engineering,” IEEE Softw., vol. 22, no. 6, pp. 60–67, 2005.
[21] M. A. Babar and I. Gorton, “Software architecture review:
the state of practice,” Comput., vol. 42, no. 7, pp. 26–32,
2009.
[22] J. Carver, L. Jaccheri, S. Morasca, and F. Shull, “Issues in
using students in empirical studies in software engineering
education,” in Software Metrics Symposium, 2003.
Proceedings. Ninth International, 2003, pp. 239–249.
[23] M. Höst, B. Regnell, and C. Wohlin, “Using Students as
Subjects - A Comparative Study ofStudents and Professionals
in Lead-Time Impact Assessment,” Empir. Softw. Engg., vol.
5, no. 3, pp. 201–214, 2000.
[24] A. A. Porter, L. G. Votta Jr., and V. R. Basili, “Comparing
detection methods for software requirements inspections: a
replicated experiment,” IEEE Trans. Softw. Eng., vol. 21, no.
6, pp. 563–575, 1995.
[25] A. Porter and L. Votta, “Comparing detection methods for
software requirements inspections: A replication using
professional subjects,” Empir. Softw. Eng., vol. 3, no. 4, pp.
355–379, 1998.