Software Engineering - Assignments

Lessons and Assignments

Text in italics means that the material is not finalized.

1

Introduction, report writing

Slides: small large

assignment 1

 

2

Requirements (use case modeling)

Slides: small large

assignment 2

 

3

Requirements (modeling scenarios)

Slides: small large

assignment 3

 

4

High level design (types and interfaces)

Slides: small large

assignment 4

 

5

Design

Slides: small large

assignment 5

 

6

Detailed design (internal class)

Slides: small large

assignment 6

 

7

Testing, configuration management

Slides: small large

assignment 7

 

8

Project preparation

 

assignment 8

 

News

Assistants

Name

Moment

Email

Room

Rikard Land

Lessons, Assignments, Project supervisor

rikard.land@mdh.se

U3-137

Johan Fredriksson

Assignments, Project supervisor

johan.fredriksson@mdh.se

U3-140

Johan Andersson

Assignments

johan.x.andersson@mdh.se

U3-043

Frank Lüders

Assignments, Project supervisor

frank.luders@mdh.se

U3-139

The lessons will be held by Rikard. Each assignment will be corrected by one of us, according to the table in the next section.

Instructions

All assignments should be solved 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 Rikard (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 assignments are reported by sending an email before deadline (see table below) to the lab assistant responsible for correcting the assignment (different for each assignment, see below). The subject of your email must be: cd5360-aX-Y. Attach the file(s) containing your solution. All files must be named se-aX-Y.xxx where X is the number of the assignment and Y is your group code. When handing in completion use subject cd5360-aX-Y-kN and name your files se-aX-Y-kN.xxx 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, which the assistants have installed: Telelogic Tau. (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 Tau. 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 assignments. Modeling in a UML tool is more than using a drawing program.

Assignment No.

Lab date

Deadline

Returned

Completion

Assistant (to ask questions

and send solution to)

1

27 Jan

31 Jan

3 Feb

10 Feb

Johan Andersson

2

3 Feb

7 Feb

10 Feb

17 Feb

Rikard

3

10 Feb

14 Feb

17 Feb

24 Feb

Frank

4

17 Feb

21 Feb

24 Feb

3 March

Johan Andersson

5

24 Feb

28 Feb

3 March

10 March

Frank

6

3 March

7 March

10 March

17 March

Johan Fredriksson

7

10 March

14 March

17 March

 

Johan Fredriksson

8

17 March

17 March

17 March

 

Rikard

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

Software and other resources

Poseidon for UML home page. Here you can download Poseidon for UML (an alternative UML tool). The "Community Edition" is a free version with some restrictions (for example, no print functionality).

Argo UML home page. Here you can download ArgoUML (an alternative UML tool), find documentation, FAQ, and more.

Download a free student edition of Rational Rose (an alternative UML tool, this version is now relatively old). This version has some restrictions on the number of classes, states, etc. that can be included in the model.

Here is an introduction to UML.

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

UML home page

An Introduction to Software Architecture by Garlan and Shaw.

Results

Results are found on the results page.

Concerning cheating

Make sure you understand what is allowed and not allowed in this course. Have a look in the presentation material for lesson 1.

Hints and FAQ

 


Rikard Land, Frank Lüders, last update: 2004-03-16