Softwaretechnik / Software Engineering (Lecture)

News

• 2017-03-27: according to the HisInOne system, the exam re-sit is on 29. March 2017, 14:00 c.t. (please be there at 14:00 s.t.), in room 101-00-010/014 (another written exam, 90 min.).
  
• 2016-10-27: The exam in the winter semester will be another written exam; time/date/place will be scheduled by the examination office.
  
• 2016-10-05: Exam Review Date

 The exam review will take place on:

Friday, October 7th at 10:30-12:30 and 13:30-15:30
in Building 052 Room 00-016.

If you have a good reason and cannot make it, please contact Sergio ASAP for an extra appointment, otherwise, the exams will be sent to the examination office towards the end of the month.

• 2016-07-20+21: errata file updated.
  
• 2016-07-12: A new version of Exercise Sheet 6 with an additional bonus task is online.
• 2016-06-30: the first errors have been spotted - see errata file for corrections (it will continuously be updated in the following), see link at the end of the schedule.  Thanks for pointing out the errors!
  
• 2016-06-27: Exercise Sheet 5 will be ready later today (or early tomorrow) - we still need to make sure that it's not too easy to get the 1000 bonus points.
  
• 2016-06-15: For those students who require to take their exams before the official date on September 9th, we can offer personalized appointments for an oral exam. If you require such an appointment, please contact the course organizers directly to set a date. The sooner you do it, the better, otherwise we may not be able to accommodate to your departure dates.
• 2016-05-23: IMPORTANT: Please note the changed rooms for exercise groups 2 and 3 *today only*
• Group 1: Bldg. 101 HS 00-026 (as usual)
• Group 2: Bldg. 078 SR 00-014
• Group 3: Bldg. 101 SR 02-016/18
• 2016-04-18: you may use this  link to enter the ILIAS module directly
• 2016-04-18: more information on exercise sheets in general, and Exercise Sheet 0 in particular, in the ILIAS Forum - please post any questions or comments there.
  
• 2016-04-07: homepage online
  

Formalia

Prerequisites for admission to the final exam, form of the final exam, and everything will be announced in the first lecture.

Admission criteria

Exercise Submission Scheme

The exercise sheets are online early in order to allow you to be aware of the tasks while following the lecture. There will be an early/regular submission scheme following a pattern to be announced.  Please submit your solutions via ILIAS (log in with RZ account, not TF Pool account).

Note: The exercises will be rated on two scales: admission points (given your knowledge before the tutorial, how sensible is your proposal; "good will rating", "upper bound") and exam points (given the additional knowledge from the comments on your proposal and the tutorial, how many points would your proposal at least be worth in a written exam; "evil rating", "lower bound").

Exam

There will be a written exam:

• Date & time: Friday, September 9th, 2016 - 9:00 AM.

• 90 min. starting at 9:00 AM c.t.
• Room: Building 101, Rooms 00-026 and 00-036.
• Permitted in the exam: one sheet of A4 paper, with prepared notes (printed, handwritten, painted, ...) on all sides.
  
  

Exam Re-Sit (Klausurwiederholung)

Another written exam:

• Wednesday, March 29th, 2017

• 90 min., starting at 14:00 c.t. (please be there at 14:00 s.t.)

• Room: Building 101, Room 00-010/014.

• Permitted exam aids: same as with regular exam (see above).

Resources

Slides, Exercises, and Recordings

Note: the following plan is tentative, that is, the assignment of topics to dates may be subject to mild changes.  The assignment of form (lecture or tutorial) to dates is fixed.  We will try to provide slides before the lecture.

• Mo, 18.4.: VL 01 "Introduction" - Exercise Sheet 0 online (submit via ILIAS, more information in the ILIAS forum)
  Definitions of Software Engineering etc.; course content overview; formalia.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (93 min.))
  
• Do, 21.4.: VL 02 "Software Metrics" - Exercise Sheet 1 online, additional file (submit via ILIAS)
  Software metrics; properties of useful metrics; kinds of scales; examples: LOC and McCabe. 
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (89 min.))
• Mo, 25.4.: VL 03 "Cost Estimation"
  Subjective metrics, Goal-Question-Metric approach; Cost and Deadlines, Expert and Algorithmic Cost Estimation.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (92 min.))
• Do, 28.4.: Tutorial 1
• Mo,  2.5.: VL 04 "Software Project Management" - Exercise Sheet 2 online (submit via ILIAS)
  Development Project; Activities, Roles, Artefacts; From Processes to Procedure and Process Modes.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (93:30 min.))
  
• Do,  5.5.: public holiday (ascension day)
• Mo, 9.5.: VL 05 "Procedure and Process Models"
  Waterfall and Spiral; Prototype-based; Evolutionary, Incremental, Iterative; V-Model XT; Agile Processes; process metrics CMM(I) and SPICE.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (93:37 min.))
• Do, 12.5.: VL 06 "Requirements Engineering"
  Requirements Engineering basics: the RE problem, the software peoples' view on requirements; quality criteria for requirements and their (natural language) documentation
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (93:30 min.))
• Mo, 16.5.: whitsun break
• Do, 19.5.: whitsun break
• Mo, 23.5.: Tutorial 2
  
• Do, 26.5.: public holiday (corpus christi)
• Mo, 30.5.: VL 07 "Formal Methods for Requirements Engineering" - Exercise Sheet 3 online (submit via ILIAS)
  One example of a formal notation for requirements: decision tables (DT); formal definitions for completeness, consistency, determinism, etc.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (83:37 min.))
• Do,  2.6.: VL 08 "Use Cases and Scenarios"
  Scenarios and Anti-Scenarios for requirements analysis; notations User Story, Use Case, Use Case Diagram, first half of Sequence Diagrams (abstract syntax, TBAs, cuts and firedsets).
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (90:55 min.))
• Mo,  6.6.: VL 09 "Live Sequence Charts"
  Second half of the 'Sequence Diagram' story (TBA construction); Requirements-Engineering wrap-up.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (96:17 min.))
  
• Do, 9.6.: Tutorial 3
  
• Mo, 13.6.: VL 10 "Requirements Engineering Wrapup" - Exercise Sheet 4 online (submit via ILIAS)
  Pre-charts cont''d; Software and Software Specification, formally; LSCs and software; Requirements Engineering wrap-up.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (92:15 min.))
• Do, 16.6.: VL 11 "Architecture & Design"
  Modularisation, information hiding, data encapsulation etc.; Views and viewpoints; UML  outlook
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (91:30 min.), module_example.tgz)
• Mo, 20.6.: VL 12 "Structural Software Modelling"
  Class Diagrams; Object Diagrams; Proto-OCL
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (92:47 min.))
• Do, 23.6.: Tutorial 4
  
• Mo, 27.6.: VL 13 "Behavioural Software Modelling" - Exercise Sheet 5 online (download additional materials and submit via ILIAS)
  Communicating Finite Automata; Uppaal Demo; Uppaal Query Language
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (89:37 min. (but 2 min. extra break)),
  Vending Machine model (vm.xml, vm.q) from the demo)
• Do, 30.6.: VL 14 "UML State-Machines"
  CFA "at work" continued; implementing CFA; an outlook on UML Statemachines.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (93:55 min.))
• Mo,  4.7.: VL 15 "Architecture  and Design Patterns"
  Architectural patterns (layers, pipeline, MVC); Design Patterns; Testing basics.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (92:00 min.))
• Do,  7.7.: Tutorial 5
  
• Mo, 11.7.: VL 16 "Software Quality Assurance: Testing" - Exercise Sheet 6 online (additional material) (old version) (submit via ILIAS) - Note: the new version contains an extra 10-Bonus-Points task.
  Testing (concepts, coverage measures, etc.); Model-based Testing.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (92:26 min.))
• Do, 14.7.: VL 17 "Software Verification"
  Vocabulary (software quality assurance in a broader scope); Notions of correctness; Formal verification of software: the Hoare calculus; Software Model-Checking, VCC Demo.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (93:20 min.))
• Mo, 18.7.: VL 18 "Runtime Verification, Software Review - Wrapup"
  Run-time Verification; Code Review; Discussion: quality assurance approaches compared; Dependability.  Wrap-Up.
  (Slides (with annotations), 2-up, 6-up, Recording: ILIAS-Download, ILIAS-Stream (92:28 min.))
• Do, 21. 7.: Tutorial 6 + (not really) VL 19 "Wrapup & Questions"
  Tutorial 6 (plenary, in the lecture hall) - and a little time for questions, consider the ILIAS forums for all remaining questions.
  (No slides, no recording.)
• Errata for the course slides.

Links & Literature

• Software Engineering Textbooks
  • Ludewig, J. and Lichter, H. (2013). Software Engineering. dpunkt.verlag, 3. edition.
    Main inspiration for the lecture; unfortunately only available in German.
    
  • Sommerville, I. (2010). Software Engineering. Pearson, 9. edition.
    The international "classic", also available in German.
  • Balzert, H. (2009). Lehrbuch der Softwaretechnik: Basiskonzepte und Requirements Engineering. Springer Spektrum, 3. edition.
    The german "classic", part 1.  Available as e-Book via UB.
    
  • Balzert, H. (2010). Lehrbuch der Softwaretechnik: Entwurf, Implementierung, Installation und Betrieb. Springer Spektrum, 3. edition.
    The german "classic", part 2. Avaliable as e-Book via UB.
    
  • Bjørner, D. (2006). Software Engineering 1 - Abstraction and Modelling. Springer.
    One of the few formal methods textbooks, part 1.
  • Bjørner, D. (2006). Software Engineering 2 - Specification of Systems and Languages. Springer.
    One of the few formal methods textbooks, part 2.
  • Bjørner, D. (2006). Software Engineering 3 - Domains, Requirements, and Software Design. Springer.
    One of the few formal methods textbooks, part 3.
• Introduction
  • Bauer, F. L. (1971). Software Engineering. In: IFIP Congress (1), pages 530-538.
    Historic (type-writer typed) lecture notes by F. L. Bauer, one of the software engineering pioneers who is said to have brought up to the term 'software engineering' on the NATO Science Committee meeting in Garmisch, 1968, in response to the 'software crisis'.
    
  • Bjørner, D. and Havelund, K. (2014). 40 years of formal methods. . Presentation slides, UNSW, Sydney, 19. May 2014.
    A brief introduction of the term "formal methods", its historical and present obstacles and hindrances, and an outlook.
  • Buschermöhle, R. et al. (2006). success - Erfolgs- und Misserfolgsfaktoren bei der Durchführung von Hard- und Softwareentwicklungsprojekten in Deutschland. Version 1.1.
    A wealth of empirical data with a thorough evaluation wrt. a set of hypothesis on correlations of factors in software engineering.
    
  • Jones, C. B. et al., editors (2011). Dependable and Historic Computing - Essays Dedicated to Brian Randell on the Occasion of His 75th Birthday, volume 6875 of LNCS, Springer.
    Timeless insights on software engineering from the early days, including an article by software engineering pioneer D. L. Parnas and the dinner talk by H. Kopetz. Available as e-Book via UB.
    
  • Most ISO/IEEE/etc. standards are unfortunately not freely available.
  • Lamport, L. (2015). Who Builds a House without Drawing Blueprints?. CACM; 58(4): 38-41.
    A somewhat polemic essay arguing for better planning in software engineering by 2013 ACM Turing Award winner (and LaTeX author) Leslie Lamport; not so far off from our approach to the software engineering lecture...
    
• Project Management, Process Models, Metrics
  • Brooks, F. P. (1996). The Mythical Man-Month - Essays on Software Engineering, Anniversary Edition. Addison-Wesley.
    Some say "if you want to read only one book on the management of software development projects, let it be this" (without being the author or otherwise sponsored by the publisher).
    
  • Douglass, B. P. (1999). Doing Hard Time, Addison-Wesley.
    Spiral-shaped development process using formal modelling and analysis especially for (safety) critical, reactive, timed systems.
  • Wheeler, D. A. (2006). The Linux Kernel: It’s Worth More!
    A COCOMO estimation of effort for the Linux kernel 2.6.  Article includes a link to the used tool SLOCCount.
    
  • Karn, J. S., & Cowling, A. J. (2005). A Study into the Effect of Disruptions on the Performance of Software Engineering Teams. In the Proceedings of the 4th International Symposium on Empirical Software Engineering, (ISESE 2005).
  • Behfar, K. J., Peterson, R. S., Mannix, E. A., Trochim,  W.M. (2008). The critical role of conflict resolution in teams: a close look at the links between conflict type, conflict management strategies, and team outcomes. J Appl Psychol.; 93(1):170-88. doi: 10.1037/0021-9010.93.1.170.
    
  • V-Modell XT Authors (2006). V-Modell XT, Version 1.4.
    The V-Modell XT reference document (in German); an English document for V-Modell XT, version 1.3, is available on the same homepage. A tool to support tailoring is available here.
  • CMMI Product Team (2010). CMMI for Development, Version 1.3.
    Definition of the CMMI-DEV process metrics.  An introdution to thlecture-20150710-1.pdfe appraisal procedure is available here.
    
• Requirements Engineering, Live Sequence Charts
  
• Rupp, Ch., die SOPHISTen (2014). Requirements-Engineering und -Management. Hanser.
  An extensive and comprehensive discussion of all aspects of Requirements Enginering, from formal notations, over quality criteria, recommendations for natural language requirements, to psychological aspects like human perception and conflicts among clients, which may show up during requirements engineering.  The book's content builds on the main author's experience as general manager of SOPHIST GmbH, a company offering Requirements Engineering.  Unfortunately only available in German.
• Damm, W., Harel, D. (2001). LSCs: Breathing Life into Message Sequence Charts. FMSD; 19(1): 45-80, Kluwer Academic Press.
  The original work on Life Sequence Charts.
• Klose, J. (2003): Live Sequence Charts - A Graphical Formalism for the Specification of Communication Behavior. PhD thesis, Carl von Ossietzky Universität Oldenburg.
  The original work on the TBA-semantics of LSCs as used in the lecture.
  
• Typesetting Live Sequence Charts: lsc.sty on CTAN (and included in TeX Live).
  
• Architecture & Design, Modelling
  
• Jacobson, I. (1992). Object-Oriented Software Engineering: A Use CASE Approach. Addison-Wesley.
  By the inventor and early advocate of use cases and use case diagrams, which were later included in UML. 20 years old, odd-looking notation, yet the basic messages remain valid.
• Kastens, U., Kleine Büning, H. (2014). Modellierung - Grundlagen und formale Methoden, Zweite Auflage, Carl Hanser Verlag.
  General Discussion of Modelling, not focusing on UML, but also considering plain set-theory, graphs, Petri nets, and their use for modelling tasks.
• Buschman, F., Beunier, R., Rohnert, H., Sommerlad, P., Stal, M. (1996). Pattern-Oriented Software Architecture, Volume 1, A System of Patterns. Wiley.
  Actually closer to the content of Lecture 14 than the (more famous) standard textbook on design patterns (Gamma et al.) The concrete examples may provoke nostalgic feelings ("this sounds soo early 90s of the last century") but the basic messages still hold.
• UML
  • B. Dobing, J. Parsons: How UML is used, Communications of the ACM, 49(5):109-114, 2006.
    This survey supports the relevance of our choice of diagrams to be considered in the lecture.
  • OMG (2011). Unified Modeling Language: Infrastructure. Version 2.4.1.
    The UML standard, basic concepts.  May take some getting-used-to.
    
  • OMG (2011). Unified Modeling Language: Superstructure. Version 2.4.1.
    Defines all the diagrams using concepts from the infrastructure document.
  • B. Oesterreich: Analyse und Design mit UML 2.1, 8. Auflage, Oldenbourg, 2006.
    Standard introduction into UML notation (only informal semantics).
  • H. Stoerrle: UML 2 fuer Studenten, Pearson Studium Verlag, 2005.
    And another one of the like.
    (avaible as e-book via UB)
  • OMG (2014). Object Constraint Language. Version 2.4.
    Our Proto-OCL semantics is inspired by Appendix A (finally something more formal...).
  • Kleppe, A., Warmer, J. (2004). The Object Constraint Language. 2nd Edition, Addison-Wesley..
    A more palatable presentation of OCL.
• Formal Verification
• Apt, K.R., Olderog, E.-R. (1994). Programmverifikation. Springer-Verlag.
  The formal verification part of Lecture 15 is following the thorough presentation in this (highly recommendable) book.  Also available in English.
  
• (2015) The VCC Manual.
  A draft document to become a manual for VCC.  For the exercises, it should not be necessary to revert to this document too much, the content of the lecture should be sufficient.
  
• Cohen, E., Hillebrand, A., Tobies, S., Moskal, M., Schulte, W. (2015). Verifying C Programs: A VCC Tutorial. Technical Report.
  A tutorial on VCC, distributed with the VCC sources.  Again: for the exercises, you should not need much more than discussed in the lecture.  We're only touching the surface of VCC.
• Miscellaneous
  • O. Laitenberger, C. Atkinson: Generalizing Perspective-based Inspection to handle Object-Oriented Development Artifacts, In: Proc. ICSE '99, 494-503, IEEE CS-Press.
    Reading techniques philosophy.
  • G. H. Travassos, F. Shull, J. Carver, V. R. Basili: Reading Techniques for OO Design Inspections, Technical Report CS-TR-4353, University of Maryland, 2002.
    Concrete reading techniques.