Software Engineering

This course is an introduction to software engineering and object-oriented software design. At the core of the lecture is the notion of software quality and the methods to achieve and maintain it in environments of "multi-person construction of multi-version software" [Parnas].

Based on their pre-existing knowledge of an object-oriented programming language, students are familiarized with software architectures, design patterns and frameworks, software components and middleware, UML-based modelling, and validation by testing. Further, the course addresses the more organisational topics of project management and version control. Practical work underpins this by looking at suitable tools.

The course is recommended to all students on whose software skills people will depend one day.

News

• don't forget to subscribe to the course mailing list:

Course material

Course material

• Ian Sommerville: Software Engineering, 10th edition, 2021
• Roger Pressman, Bruce Maxim: Software Engineering - A Practitioner's Approach, 2015 (to a lesser extent)

Also, the World Quality Report (local copy) is relevant, specifically the chapters pp 14, 28, 36.

Finally, the short story pragma SUPPRESS is required reading; make sure you have not only read, but understood it.

Course slides

• Introduction: to course & project
• The software lifecycle: [ Socio-Technical Systems | Software Lifecycle | Requirements Engineering | UML | Design Patterns | Compiling and Linking | Defensive Programming | Configuration Management | Testing | Maintenance | Documentation ]
• User Interfaces: [ GUI Foundations | UI Design ]
• Project and process management: [ Project and Process Management | CMMI ]
• Finally: [ Wrap-up ]

Software Engineering Project

In a guided project over the course of the semester some non-trivial software tool will be developed. See the 2024 project intro slides and the resp. teaching slots.

Methodology:

Over the semester, students will develop some larger piece of software. The main objective is to learn group work and gain practical experience with critical software engineering methods and tools. Grading criteria are introduced and discussed upfront in class.

Project phases:

1. Requirements analysis and design. In the first phase, students team up on their own in groups of 3 - 5. They analyse the requirements presented, document them, and establish a specification. Each team receives a grade for its specification. Among the specifications submitted one is chosen which will act as the common basis for the implementation phase following next.
2. Component development using extreme programming. Over several 2-week phases ("sprints"), students will perform Extreme Programming cycles in order to develop components identified by the overall system design. Students work in teams of two in each sprint (Pair Programming). After each sprint, teams and code bases change randomly but ensuring that no team and codebase match more than once. The progress produced in each sprint, as submitted to the repository, will be graded.

Exams

Sample exams: [ midterm | final ]

Links

general

What every computer science major should know [ local copy ]

RFC 1925 containing some wisdoms applicable not only to networking. Check it out!

UML

As for tutorials, the maintainer of the standard, OMG, offers a list of UML tutorials. Further, many more good tutorials are available on the Web, for example Borland's tutorial, Sparx Systems' tutorial with a particular part on Database Modeling in UML, and UML material collected by the ISO TC211 expert..
Meantime there is also a host of UML tools available - such as Rational Rose and Enterprise Architect (EA) by Sparx Systems, or Omondo's free UML extension to Eclipse - collected in lists like this one.

Programming

How to write unmaintainable code

Software Calculus - The Missing Abstraction.

Make and svn

• svn book
• make tutorial

Beautifiers

• Artistic Style (C, C++, C#, Java)
• BCPP (C; C++)
• DMS Software Reengineering Toolkit (many languages)
• VanCBJ (C++, C, Java and Oracle Pro-C; Borland, but not MS VC)

Testing and Debugging

The following list of tools is intended to give a first overview; no tool is particularly endorsed, and missing one doesn't mean any discouragement either.

• links:
  [ www.testingfaqs.org | Software Quality Testing Engineering Magazine | Free Debugging Tools, Program Checkers, Bug Trackers ]
• Unit Test Tools: [ AdaTEST | AQtest | Aunit | C++Test | Cantata | Check | COMPUTE | CppUnit | csUnit | CTA++ | CTB | cUnit | CUT | dotunit | EasyMock | GrandTestAuto | HarnessIt | HtmlUnit | HttpUnit | JavaScript | JsUnit | JsUnit | JTestCase | JUnit | JUnitEE | JUnitX | LingoUnit | MinUnit | Mock Creator | Mock Objects | MockMaker | Mockry | NUnit | ObjcUnit | OCUnit | OTF - An | PalmUnit | PBUnit | PerlUnit | phpAsserUnit | PhpUnit | PyUnit | QtUnit | Ruby/Mock | SUnit | TagUnit | TBGEN | TBrun | Test Mentor - Java Edition | unit++ | vbUnit3 Basic | vbUnit3 Basic | VectorCAST | XMLUnit | XSLTunit ]
• Coverage Analysis Tools: [ gcov | Bullseye Coverage | Cantata++ | CodeTEST | LOGISCOPE | Panorama C/C++ | Rational PureCoverage | TCAT C/C++ | GCT ]
• Memory Leaks Detection: [ Valgrind | Purify ]

Project Management

• An XP team room
• There is a host of tools; The V-Modell site offers the open-source tool V-Modell-XT-Projektassistent assisting from initial project proposal to final report.