Software Engineering – Lessons and Laborations

Text in italics means that the material is not finalized.

1

Intro to version management,

Report writing

 

Laboration assignment 1

2

Requirements (use case modeling)

Slides

Laboration assignment 2

3

Requirements (modeling scenarios)

Slides

Laboration assignment 3

4

High level design (types and interfaces)

Slides

Laboration assignment 4

5

Design

Slides

Laboration assignment 5

6

Detailed design (internal class)

Slides

Laboration assignment 6

7

Version management and testing

Slides

Laboration assignment 7

8

Project preparation

 

Laboration assignment 8


News

Laboration Assistants

Name

Email

Room

Yue Lu

yue.lu@mdh.se

U3-041

Frank Lüders

frank.luders@mdh.se

U3-063

Farhang Nemati

farhang.nemati@mdh.se

U3-041

Aneta Vulgarakis

aneta.vulgarakis@mdh.se

U3-150

Peter Wallin

peter.wallin@mdh.se

U3-043

The lessons will be held by Rikard. Different assistants are responsible for different labs, according to the table below. Please direct your questions to the responsible assistant.

Results

Results are found on the results page.

Instructions

All laborations should be performed in groups of 1 to 2 students (that is, individually or in pairs). Pick someone to work with and report the group formation in an email to Frank (also if you are working alone) with subject cd5360 group formation. Include the names and email addresses of both people (in case you form a pair). When you have reported the group formation you will receive a group code to be used when reporting subsequent labs. With this code you can also see your results on the lab main page.

All laborations are reported by:

The subject of your email must be cd5360-aX-gYY, where X is the number of the laboration and YY is your group number. When handing in a completion, commit new versions of the files to your repository and send another mail to the lab assistants, using subject cd5360-aX-gYY-kN, where N is 1 the first time you hand in a completion, 2 the second etc. If you do not follow these instructions, you risk that your lab will not be corrected in time.

For the UML labs, use the UML tool provided in the lab room, StarUML 5.0, which the IT department has installed. (The links under Software and Other Resources below are not alternative tools for the labs, only as a service and a way for you to orient yourself about other tools that exist in the UML world.) There might even be version problems if you use other versions of the provided tool. Basically, it is your problem if we cannot open the files with a small effort. We are not unreasonable if you for some reason must use some other tool or version, but it is your responsibility to find a solution how we can correct your laborations. Modeling in a UML tool is more than using a drawing program.

Lab No.

Lab date

Deadline

Returned

Completion

Responsible

1

24 Jan

30 Jan

2 Feb

9 Feb

Frank + Peter

2

31 Jan

6 Feb

9 Feb

16 Feb

Aneta + Peter

3

7 Feb

13 Feb

16 Feb

23 Feb

Yue + Farhang

4

14 Feb

20 Feb

23 Feb

2 March

Frank + Aneta

5

21 Feb

27 Feb

2 March

9 March

Aneta + Peter

6

28 Feb

6 March

9 March

16 March

Yue + Farhang

7

7 March

13 March

16 March

30 March

Yue + Frank + Farhang

8

14 March

20 March

First steering

group meeting

 

Steering group

(see project page)

(Note: always check this table for the latest information before sending in your labs. It might happen that dates or assistants change, although we will try to avoid it.)

Resources

Free UML Tools

To avoid misunderstandings: these are tools you may use for your own leisure, not alternatives to be used in the laborations!

StarUML, open source UML tool for Windows, http://staruml.sourceforge.net/en/download.php

Umbrello, UML-modeling tool for KDE (linux) , http://uml.sourceforge.net/index.php

ArgoUML, UML-modeling tool in Java, http://argouml.tigris.org/
Poseidon, UML tool,
http://www.gentleware.com/

Rational Rose, UML modeling tool now owned by IBM. Download a free, old student edition.

 

(Please give suggestions for more tools.)

Texts

Mikael Åkerholm, Ivica Crnković, Goran Mustapić, Mikael Davidsson, Introduction for using UML, Edition 2

UML home page

The book Visual Modeling with Rational Rose and UML by Terry Quatrani.

An Introduction to Software Architecture by Garlan and Shaw.

 

(Please give suggestions for more links.)

Concerning Academic Dishonesty (Cheating)

Make sure you understand what is allowed and not allowed in this course. Read the IDE texts on cheating and have a look in the presentation material for lesson 1. If you are two in a lab group, the students must do the laboration together and both students must be prepared to explain it individually.

Hints and FAQ

 


Rikard Land, Frank Lüders, last update: 2007-03-13