Section: MSc in Computer Science
Section: MSc in Computer Science
Section: MSc in Computer Science
Section: MSc in Computer Science
Section: MSc in Computer Science
Section: MSc in Computer Science
Section: MSc in Computer Science
Section: MSc in Computer Science

1 Articles that will be part of the body from which an article for presentation will be randomly assigned for each student


  1. Osterweil, L., (1987) Software processes are software too. Proceedings of the 9th International Conference on Software Engineering, March, Monterey, California, U.S.A., pp.2-13. 

  1. P. Naur. Programming as Theory Building In: P. Naur, Computing a Human Activity, ACM Press 1992. or: A. Cockburn. Agile Software Development. Pearson Education 2002. 

  1. Fitzgerald, Brian, and Klaas-Jan Stol. "Continuous software engineering: A roadmap and agenda." Journal of Systems and Software 123 (2017): 176-189. 

  1. Glass, Robert L. "The software-research crisis." IEEE Software 11.6 (1994): 42-47. 

  1. Dittrich, Yvonne. "Software engineering beyond the project–Sustaining software ecosystems." Information and Software Technology 56, no. 11 (2014): 1436-1456. 

  1. Ardito, C., Buono, P., Costabile, M. F., Lanzilotti, R., & Piccinno, A. (2012). End users as co-designers of their own tools and products. Journal of Visual Languages & Computing, 23(2), 78-90. 

  1. Parnas, David Lorge. "Software aging." Proceedings of 16th International Conference on Software Engineering. IEEE, 1994. 

  1. Bird, C., Nagappan, N., Murphy, B., Gall, H., & Devanbu, P. (2011, September). Don't touch my code!: examining the effects of ownership on software quality. In Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering (pp. 4-14). ACM. 

  1. Haley, C., Laney, R., Moffett, J., & Nuseibeh, B. (2008). Security requirements engineering: A framework for representation and analysis. IEEE Transactions on Software Engineering, 34(1), 133-153.http://mcs.open.ac.uk/ban25/papers/tse07-halay.et.al.pdf 

  1. Paja, E., Dalpiaz, F., & Giorgini, P. (2015). Modelling and reasoning about security requirements in socio-technical systems. Data & Knowledge Engineering, 98, 123-143. 

  1. Herbsleb, J.D., 2007. Global software engineering: The future of socio-technical coordination. In Future of Software Engineering (FOSE'07) (pp. 188-198). IEEE.    

  1. Shihab, E., Bird, C. and Zimmermann, T., 2012. The effect of branching strategies on software quality. In Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement (pp. 301-310).   

  1. Sutherland, Jeff, Carsten Ruseng Jakobsen, and Kent Johnson. "Scrum and CMMI level 5: The magic potion for code warriors." Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008). IEEE, 2008. 

  1. Dittrich, Yvonne et al. "Exploring the Evolution of Software Practices." Proceedings of the FSE/ESEC 2020. 

  1. Dittrich, Yvonne. "What does it mean to use a method? Towards a practice theory for software engineering." Information and Software Technology 70 (2016): 220-231. 

 

General course syllabus beyond the articles above

  1. Hohl, P., Klünder, J., Bennekum, A.,  Lockard, R., Gifford, J., Münch, J., Stupperich, M., Schneider, C.. (2018) Back to the Future: Origins and Directions of the "Agile Manifesto" - Views of the Originators. Journal of Software Engineering Research and Development, 6:15
  1. Lous, Pernille, et al. "From Scrum to Agile: a journey to tackle the challenges of distributed development in an Agile team." Proceedings of the 2018 International Conference on Software and System Process. ACM, 2018. 

  1. Guckenheimer, Sam. "Our journey to cloud cadence lessons learned at Microsoft developer division." Technical Report (2016) 

  1. Christensen, H. B., Hansen, K. M., Kyng, M., & Manikas, K. (2014). Analysis and design of software ecosystem architectures–Towards the 4S telemedicine ecosystem. Information and Software Technology, 56(11), 1476-1492.  

  1. Bolmsten, J., & Dittrich, Y. (2011, June). Infrastructuring when you don’t–end-user development and organizational infrastructure. In International symposium on end user development (pp. 139-154). Springer, Berlin, Heidelberg. 

  1. Dittrich, Y., Bolmsten, J., & Eriksson, J. (2017). End user development and infrastructuring–sustaining organizational innovation capabilities. In New perspectives in end-user development (pp. 165-206). Springer, Cham. 

  1. Unphon, H., & Dittrich, Y. (2010). Software architecture awareness in long-term software product evolution. Journal of Systems and Software, 83(11), 2211-2226. 

  1. C. R. de Souza, S. Quirk, E. Trainer, and D. F. Redmiles. 2007. Supporting collaborative software development through the visualization of socio-technical dependencies. In Proceedings of the 2007 international ACM conference on Supporting group work (GROUP '07). ACM, New York, NY, USA, 147-156. 

  1. Nagappan, N., Murphy, B., & Basili, V. (2008, May). The influence of organizational structure on software quality. In 2008 ACM/IEEE 30th International Conference on Software Engineering (pp. 521-530). IEEE. 

  1. Phillips, S., Sillito, J., & Walker, R. (2011, May). Branching and merging: an investigation into current version control practices. In Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering (pp. 9-15). ACM. 

  1. Daniel Ratiu et. al.,  Using History Information to Improve Design Flaws Detection. CSMR 2004 

  1. Begel, A, Y. Khoo, T. Zimmermann. "Codebook: discovering and exploiting relationships in software repositories". Proceedings of the 32Nd ACM/IEEE International Conference on Software Engineering. ICSE 2010 

  1. Sadowski et al., "Lessons from Building Static Analysis Tools at Google", ICSE 2018 

  1. Shostack, A. (2008). Experiences Threat Modeling at Microsoft. MODSEC@ MoDELS, 2008. 

  1. Firesmith, D. G. (2003). Security use cases. Journal of Object Technology 2(3), 53-64. 

  1. Giorgini, P., F. Massacci, J. Mylopoulos, and N. Zannone (2005). Modelling security requirements through ownership, permission and delegation. In Proceedings of the 13th IEEE International Conference on Requirements Engineering (RE), pp. 167-176. 

  1. McDermott, J., and C. Fox (1999). Using abuse case models for security requirements analysis. In Proceedings of the 15th Annual Computer Security Applications Conference (ACSAC), pp. 55-64. 

  1. Noll, J., Beecham, S. and Richardson, I., 2011. Global software development and collaboration: barriers and solutions. ACM inroads, 1(3), pp.66-78.  

  1. Cataldo, M., Mockus, A., Roberts, J.A. and Herbsleb, J.D., 2009. Software dependencies, work dependencies, and their impact on failures. IEEE Transactions on Software Engineering, 35(6), pp.864-878.  

  1. Iversen, Jakob, Peter Axel Nielsen, and Jacob Norbjerg. "Situated assessment of problems in software development." ACM SIGMIS Database: the DATABASE for Advances in Information Systems 30.2 (1999): 66-81.  

  1. Klünder, Jil, et al. "Catching up with method and process practice: An industry-informed baseline for researchers." Proceedings of the 41st International Conference on Software Engineering: Software Engineering in Practice. IEEE Press, 2019. 


3 All material, slides, videos and lecture notes published for the course on Learnit

Section: MSc in Computer Science
Section: MSc in Computer Science
Section: MSc in Computer Science