Software Engineering

Software engineering is a discipline which deals with building large software systems. There are several approaches to organize such a software development and which software artefacts are created during different phases. As the software systems penetrate more and more different areas of life and complex software development costs and costs of products delivered as a result of such software development are one of the major investments of every organization. It is therefore important to learn different approaches to software development organization.

The main goal of this course is to facilitate basic understandings of:

• The main phases in software development
• Significant approaches to organize the phases
• Planning and management of the phassis
• Influence of the software process organization on the company processes

Lecturer

Literature

Main:

• Craig Larman: Agile and Iterative Development; A Manager's Guide. Addison-Wesley 2003, ISBN 0-13-111155-8.

Mandatory Literature:

• Aaen, I., Arent, J., Mathiassen, L., & Ngwenyama, O. (2001). "A Conceptual MAP of Software Process Improvement." Scandinavian Journal of Information Systems, 13, 123-146.
• Aaen, I. (2003). "Software Process Improvement: Blueprints versus Recipes." IEEE Software, 20(5), 86-93.
• Ambler, S. W. (2003). "Agile model driven development is good enough." IEEE Software, 20(5), 71-73.
• Boehm, B. W. (1991). "Software Risk Management: Principles and Practices." IEEE Software, 8(1), 32-41.
• Boehm, B., & Turner, R. (2003). "Using risk to balance agile and plan-driven methods." Computer, 36(6), 57-66.
• Butler, Tom. 2000. Transforming information systems development through computer-aided systems engineering (CASE): lessons from practice. Information Systems Journal 10, no. 3: 167-193.
• CMMI Product Team (2002). CMMI for Software Engineering, Version 1.1, Staged Representation (CMMI-SW, V1.1, Staged). Pittsburgh, PA, Software Engineering Institute.
• Fowler, M. (2003). "Design - Who needs an architect?" IEEE Software, 20(5), 11-13.
• Glass, R. L. (2004). Some Heresy Regarding Software Engineering. IEEE Software, 21(4), 104-103.
• Martha M. Gray: Applicability of Metrology to Information Technology. Journal of Research of the National Institute of Standards and Technology 104, 567 (1999).
• William G. Griswold, David Notkin: Computer-aided vs. manual program restructuring. ACM SIGSOFT Software Engineering Notes archive Volume 17 , Issue 1 (January 1992).
• Harrison, W. (2003). Is software engineering as we know it over the hill? IEEE Software, 20(3), 5-7.
• Layman, Lucas, Laurie Williams, and Lynn Cunningham. 2004. Motivations and measurements in an agile case study. QUTE-SWAP '04: Proceedings of the 2004 workshop on Quantitative techniques for software agile process, 14-24.
• Mellor, S. J., Clark, A. N., & Futagami, T. (2003). "Model-driven development - Guest editor's introduction." IEEE Software, 20(5), 14-18.
• Nerur, Sridhar, RadhaKanta Mahapatra, and George Mangalaraj. 2005. Challenges of migrating to agile methodologies. Communications of the. ACM 48, no. 5: 72-78, doi = {doi.acm.org/10.1145/1060710.1060712}.
• Nuseibeh, Bashar, and Steve Easterbrook. 2000. Requirements engineering: a roadmap. ICSE '00: Proceedings of the Conference on The Future of Software Engineering, 35-46.
• Osterweil, L. 1987. Software processes are software too. In Proceedings of the 9th international Conference on Software Engineering (Monterey, California, United States). International Conference on Software Engineering. IEEE Computer Society Press, Los Alamitos, CA, 2-13.
• Osterweil, L. J. 1997. Software processes are software too, revisited: an invited talk on the most influential paper of ICSE 9. In Proceedings of the 19th international Conference on Software Engineering (Boston, Massachusetts, United States, May 17 - 23, 1997). ICSE '97. ACM Press, New York, NY, 540-548. DOI= http://doi.acm.org/10.1145/253228.253440
• D. Parnas and P. Clements. "A Rational Design Process: How and Why to Fake It," IEEE Transactions on Software Engineering, vol. 19, no. 2, pp. 251-- 257, February 1993.
• working paper, 2000
• Riemenschneider, C.K., B.C. Hardgrave, and F.D. Davis. 2002. Explaining software developer acceptance of methodologies: a comparison of five theoretical models. IEEE Transactions on Software Engineering 28, 1135-1145.
• Sauvé, Jacques Philippe, Osório Lopes Abath Neto, and Walfredo Cirne. 2006. EasyAccept: a tool to easily create, run and drive development with automated acceptance tests. AST '06: Proceedings of the 2006 international workshop on Automation of software test, 111-117.
• Talby, D., A. Keren, O. Hazzan, and Y. Dubinsky. 2006. Agile software testing in a large-scale project. IEEE Software 23, 30-37.
• TU Berlin: Survey of Refactoring. Reports on a survey of 91 people, mostly programmers. Almost all respondents report that refactoring support is important to choosing an IDE, but only 1/4 report that they refactor more using IDEs.
• Uhl, A. (2003). "Model driven arcitecture is ready for prime time." IEEE Software, 20(5), 70, 72.
• Voas, J. (1999). Software quality's eight greatest myths. IEEE Software, 16(5), 118-120.
• Whittaker, J.A. 2000. What is software testing? And why is it so hard? IEEE Software, 17 E, 70-79.
• Luke Wroblewski: Design Patterns: Introduction.
• Zelkowitz, M. V. (1978). "Perspectives on Software Engineering." ACM Computing Surveys 10(2): 197-216.

Book related Links

Exam

Exam will be a regular oral exam with a final grade according to a regular scale. Each course participant will be examined individually for 17 minutes. You will pick up a question from the following list. Prepare a presentation for which can last from 8-12 minutes. You will be allowed to bring your notes. After the presentation examiner as well as censor can ask further questions related to the course. The main criteria for the evaluation are:

• demonstrate an overview of the topic seen from both paradigms,
• be concrete and specific w.r.t. selected methods, tools or similar relevant to the topic, and
• compare the two paradigms and discuss pros and cons relevant to the topic.

Schedule (Lectures): D2-106