Software Engineering Spring 2004

0. News

Exams results are available on http://user.it.uu.se/~hessel/pvt04.
The latest bonus status will be available on http://user.it.uu.se/~hessel/pvt04.
If your MP2 group misses the internal deadline (significantly - i.e. such that your deadline for 2C is in danger), then let me know.
Assignment 2B has been corrected, pick it up from Anders Hessel.
The lecture on 25/2 gave a short introduction on XML. Links are included with Assignment 2.

1. Teaching staff

	Name	E-mail	Room	Phone	Mailbox (4th floor, building 1)
Lecturer	Roland Bol	Roland.Bol@it.uu.se	1356	018-471 7606	28
Assistant	Anders Hessel	Anders.Hessel@it.uu.se	1436	018-471 6201	2

2. Course start

2.1 What course?

This course actually consists of two courses taking the same lectures. These courses are

Code	Swedish name	Points	Programmes
2AD064	Programvaruteknik DV1	4	DVP
2AD517	Programvaruteknik MN1	5	NVP/free/exchange

The English name of the courses is "Software Engineering". Make sure that you know to which course you are accepted upon registration. Exchange students will be registered on the 5 point (7.5 ECTS credit) course. The difference between the courses is Assignment 4 below.

2.2. Registration

Students who have been accepted (antagen) to the course and exchange students will be registered at the first lecture.

2.3. Language

The course will be given in English. Assignments may be handed in in English or Swedish.

2.4. Literature

The main course book is Software Engineering, 6th edition, by Ian Sommerville.

Buy the book now and start reading in time!

3. Schedule

The schedule consists of lectures (L), guest lectures (G) and exams (E).

3.1. Course lay-out and speed

The course is taught in close cooperation with another course: Methods of Programming 2. In short, Software Engineering will be responsible for requirements engineering and quality assurance through code review, (sub)system level test planning and testing. Methods of Programming 2 will be responsible for implementation, readable code, debugging, module testing and documentation.

The SE assignments are done in pairs. MP assignments are made in groups of three. Two SE teams work together with one MP team. Because of the combination of the courses, it is extremely important that you keep the deadlines. Making a plan and following it is an important part of what Software Engineering is about.

1/4th of the course belongs to period 3 (in average you should spend 5 hours per week on it).
3/4th of the course belongs to period 4 (in average you should spend 12-15 hours per week on it).
The same holds for Methods of Programming 2.

A combined overview schedule for both courses, showing their integration, is here.

3.2. Lectures

The purpose of the lectures is to summarize, clarify and complement the literature, and to highlight the important points. They follow the book rather closely, though not exactly in the same order. The detailed schedule below lists the chapters in the book that are related to each lecture. Attendence is of course recommended, but not obligatory.

Some lectures are joint lectures with Methods of Programming 2. There are also a few guest lectures. The guests come from the university and industry. The topics are current research and industrial practices in software engineering. The purpose is to put the course material in a wider perspective, and to complement the views of the lecturer with others' views.

3.3. Time and place

All lectures etc. start at 15 minutes past the hour. The exams start on the hour.
(L = lecture, JL = joint lecture with Methods of Programming 2, G = guest lecture, S = seminar, E = Exam)

Type	Day	Time	Room	Subject	Chapters	Important sections
week 4
JL	19/1	10	1211	Introduction; schedule, assignments, waterfall- and V-model, good code	1, 3.1.1, 3.3-3.7	3.1.1, 3.5
L	20/1	8	1211	Requirements, Requirements Engineering	2.5, 3.3, 5, 6	2.5, 3.3, 5-in, 5.1, 5.2, 5.3-in 6-in, 6.2, 6.4
JL	22/1	13	1211	LHE: Standards for code and documentation	24.1, 24.3, 18.1, 18.2, 29	24.1, 24.3, 29-in, 29.5
week 5
L	26/1	13	1145	Project Planning, Quality Assurance	4 (not 4.4), 24	4, 24.4
JL	28/1	13	1211	Validation and Verification (V&V)	3.5, 6.3, 19 - 21	3.5, 6.3, 19-in, 19.2, 20.2, 20.4, 21.1, 21.3
week 6-7: assignment 1: requirements specification
week 7
JG	11/2	15	1211	Bengt Jonsson: Defect Testing	20.1, handouts	handouts
week 8
JL	16/2	13	1211	LHE: Ray tracing	necessary domain knowledge
L	20/2	13	1211	Iterative processes. Models and Prototypes	3.1, 3.2 7, 8	3.1.2, 3.2.1 7.2, 7.3, 7.4, 8-in, 8.1, 8.2.3
week 9: assignment 2A: v&v planning
L	25/2	13	1311	Design, Reuse add: short XML intro	3.4, 10, 11, 14	3.4-in, 10-in, 10.1, 10.2, 11-in, 11.2, 14-in, 14.1
week 10-11: assignment 2B: v&v specification
week 13-14: assignment 2C: v&v results
week 15-16: assignment 3AB: v&v planning and specification
week 17
L	19/4	10	1145	Dependable Systems	16 - 18	16-in, 16.3, 17-in, 17.1, 17.2, 18.1
G/L	20/4	10	1211	Lars-Henrik Eriksson: Industrial Applications of Formal Methods
G/L	20/4	10	1211	Formal specification	9	9-in, 9-1
L	23/4	8	1211	Software Cost, Maintenance, Evolution	23, 26 - 28, 29.2	23-in, 23.1, 23.2, 26-in, 26.1, 26.3-in, 27-in, 27.2, 28-in, 28.2, 28.5, 29.2
week 18-19: assignment 3C: v&v results
week 20
L	10/5	13	1311	Management, Process Improvement Course summary	4.4, 22, 25	4.4, 22.2.4, 25-in, 25.4, 25.5
S	11/5	10	1211	Case study (A War Story)
G	13/5	10	1211	Guest lecture: Ola Jirlow (Prevas): Planning, Management, Quality
week 21
L	17/5	10	1211	Questions, old exams
E	25/5	8.00	5...	Exam Polacksbacken bldg. 5, 8.00-13.00
E	17/8	8.00	5...	Exam Polacksbacken bldg. 5, 8.00-13.00
E	15/1			Exam

"x-in." means the introduction to Chapter/Section x, before Section x.1 starts.

Chapters 12, 13, 15 are not covered at all in this course.

Other material that is included:

handouts by Bengt Jonsson (available outside my room 1356)

3.4 Seminar: A War Story (Case Study)

Part one of the story will be distributed on Monday May 10. Make sure that you have read it (*), and bring it!
The rest of the story will be handed out in episodes.

Apart from the questions at the end of each part, consider:

What additional information would you want to have?
What are the risks? Separate high risks from lesser risks.
What would you do next?

(*) Clarification: your whole group is joining this project: 20 programmers, 2 first-level managers, a secretary and a typist.

4. Assignments, exams, grades

4.1 Overview of estimated time spent, and grading

The grade will be determined by the total points score from the exam and the assignments. That is, the exam will not be given a grade by itself.

Item	hours	grade points
Exam and reading time	60	50
Assignment 1	10	10
Assignment 2AB	15	8
Assignment 2C	30	12
Assignment 3AB	15	8
Assignment 3C	30	12
Assignment 4 only students taking 2AD517 (5p)	30	20
Required for G. 2AD064 (4p)		50 of 100
Required for VG. 2AD064 (4p)		70 of 100
Required for G. 2AD517 (5p)		62 of 120
Required for VG. 2AD517 (5p)		85 of 120

The limits for G/VG are estimates and can be adjusted - it is the first time the course is taught in this way.

4.2 Assignments

Assignment 1. Start: 24/1. Deadline 13/2 at 15:00.
Assignment 2.

Part A. Start 16/2. Deadline 25/2 at 13:00.
Part B. Start 20/2. Deadline 15/3 at 10:00.
Part C. Start 22/3. Deadline 2/4 at 15:00

Assignment 3.

Part AB. Start 2/4. Deadline 19/4 at 10:00.
Part C. Start 26/4. Deadline 10/5 at 13:00.

Assignment 4. Only students taking 2AD517 (5p) Start as soon as you like. Deadline 17/5 at 10:00.

Completed assignments should be put into Anders's mailbox (floor 4, number 2) before the deadline, or handed in at the beginning of the lecture. Graded assignments will be returned on the shelf outside room 1346. If you have questions, you can send e-mail or see if Anders is in his office (1436).

4.3 Grading

Assignments Details follow with the assignments.
Exam The exam counts for 50 points. The weight of each question will be on the exam. The exam covers the book (except the chapters listed above), and Bengt Jonsson's handouts .

4.4 Some sample exams (some cover additional material)

rolandb@csd.uu.se

Roland Bol