Software Engineering Autumn 2002

No silver bullet!

0. News

The August exam is cancelled, since no-one signed up for it.
Late assignments 1 and 2 should be sent to Annika, preferably by email.
Assignment 3: put it in my mailbox or send it by email.
The first exam. Results are accessible from computers in the IT-dept.
Two more links to old exams added.
Points for seminar attendance added to the results list.
Corrected assignments and papers (handouts) are available outside my door, room 1356.
Assignment 1 and 2 have been corrected. Results are accessible from computers in the IT-dept.
After the first seminar, the groups list was edited.

1. Teaching staff

	Name	E-mail	Room	Phone	Mailbox (4th floor, building 1)
Lecturer	Roland Bol	rolandb@csd.uu.se	1356	018-471 7606	28
Assistant	Annika Karlsson	anka9310@student.uu.se			46

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.

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. Perhaps a guest lecture might be in Swedish. Assignments may be handed in in English or Swedish.

2.4. Literature

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

A collection of articles complements the book. It is sold at UTH-gård for about SEK 60.

Buy the book and articles now and start reading in time! You are supposed to read the relevant book chapters before the seminar covering them. Otherwise your participation in the seminar will suffer.

3. Schedule

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

3.1. Lectures

The purpose of the lectures is to summarize, clarify and complement the literature, and to highlight the important points. They follow the book and articles 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.

3.2. 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. Attendence is in principle obligatory (see also grading).

3.3. Seminars

Seminars are held in two sessions (Sa, Sb) of around 30 students.

For the seminars, the students are divided in groups of 5 or 6. Check the group list to see what group you are in. Remember to check whether your group is in the "Sa" or "Sb" half-classes.

At the first seminar each group chooses a particular system (for example an ATM (bankomat)). At each seminar, the group discusses how the theory would apply to their system (what are the requirements on an ATM, how reliable should it be, how can it be tested, etc.). This discussion takes 60-70 minutes. Then one representative of each group presents the conclusions (5-10 minutes per group). Since the groups have chosen different systems, there is not too much repetition. All systems have different aspects that are important, and it becomes clear that there is no "universal truth".

To benefit from the seminars, it is important that you have read the relevant chapters of the book, and participate actively. Below you find the precise questions for each seminar. Attendence is in principle obligatory (see also grading).

3.4. Time and place

All lectures, seminars etc. start at 15 minutes past the hour. The exams start on the hour. All lectures are in room 1311. All seminars are in room 1145.

Type	Day	Time	Subject	Chapters	Important sections
week 44
L	28/10	10-12	Introduction; products; software lifecycle	1 - 3	1.1, 2.1, 2.4, 3.1.1, 3.1.2, 3.1.3, 3.2.2
L	29/10	15-17	Requirements, Requirements Engineering	2.5, 3.3, 5, 6.1, 6.2	2.5, 3.3, 5-in, 5.1, 5.2, 5.3-in 6-in, 6.2
week 45
L	4/11	10-12	Roland Bol: Requirements management in Telecommunication, the ARENA project.		6.4
L	4/11	10-12	Models and Prototypes	6.3, 7, 8	7.2, 7.3, 7.4, 8-in, 8.1
Sa	5/11	13-15	Requirements engineering
Sb	5/11	15-17	Requirements engineering
L	7/11	8-10	Design, Reuse	3.4, 10, 11, 14	3.4-in, 10-in, 10.1, 10.2, 11-in, 11.2, 14-in, 14.1
L	8/11	13-15	Safety Critical Systems	16 - 18	16-in, 16.3, 17-in, 17.1, 17.2, 18.1
week 46
Sa	11/11	10-12	Design
Sb	11/11	8-10	Design
L	12/11	Deadline 15-17	Lars-Henrik Eriksson: Industrial Applications of Formal Methods
L	12/11	Deadline 15-17	Formal specification	9	9-in, 9-1
Sa	15/11	8-10	Safety and Reliability
Sb	15/11	10-12	Safety and Reliability
week 47
L	18/11	10-12	Validation and Verification	3.5, 19 - 21	3.5, 19-in, 19.2, 19.4, 20.2, 20.4, 21.1, 21.3
G	19/11	15-17	Krister Ström, Enea Data: Testing. Pay now - or pay later. Slides from 2000.
Sa	20/11	15-17	Validation and Verification
Sb	20/11	13-15	Validation and Verification
week 48
L	25/11	Deadline 10-12	Bengt Jonsson (ASTEC): Defect Testing	20.1, handouts	handouts
L	26/11	15-17	Bengt Jonsson (ASTEC): Defect Testing	20.1, handouts	handouts
A	26/11	15-17	Meeting for assignment 3
L	27/11	8-10	Maintenance, Evolution	26 - 29	26-in, 26.1, 26.3-in, 27-in, 27.2, 28-in, 28.2, 28.5, 29-in, 29.2, 29.5
G	29/11	13-15	Ola Jirlow (Prevas): Planning, Management, Quality
week 49
L	2/12	Deadline 10-12	Planning, Management	4, 22 - 23	4 (all), 22.2.4, 22.3.1, 23-in, 23.1, 23.2
L	3/12	15-17	Quality	24, 25	24-in, 24.1-in, 24.1.2, 24.4-in, 25-in, 25.4, 25.5
Sa	4/12	13-15	Maintenance; Change, Reuse; Re-engineering; Planning, Quality
Sb	4/12	15-17
week 50
Sa	9/12	10-12	Planning, Management (A War Story) The story will be handed out in episodes. After each one, the question is: what would you do? (No relation to the chosen systems)
Sb	9/12	8-10
L	10/12	13-15	Questions, old exams
E	11/12	9-14	Exam Postscriptum hall 2
	20/12	Deadline	Assignment 3 (NVP/free/exchange students only)
E	16/4		Exam
E	11/8	The August exam is cancelled, since no-one signed up for it.

"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:

the collection of articles.
handouts by Bengt Jonsson

3.5. Seminar contents.

S1 Requirements Engineering

Decide on a system

You are not required to build the system - be bold, inventive and ambitious
Make sure that the system is nontrivial - building it should be a big project
Choose a system in an area where you have domain knowledge. If you want to work with an Air Traffic Control system, do you really know how Air Traffic Control works?

Requirements collection

Who are the stakeholders, and what are their requirements? (don't think of the users only)
Can you categorise the requirements?

Functional
Non-functional product
Non-functional process

Missed a category? Think again!

S2 Design and Reuse

Present an architectural design.

physical distribution (hardware, components)
logical separation (sub-systems)
control model(s)

Suppose you have a library of reusable components

How would the design process differ?
How much of the system can be built by reusing components?
How would you contribute to the component library?

S3 Safety and Reliability

Safety

What hazards does the system pose?
What are the safety requirements?
What are the possible causes of hazards?
How are the requirements enforced?

Reliability

What are the reliability requirements?

How can these requirements be met? (Design, implementation)

S4 Validation and Verification

Are the requirements in the specification testable? (This includes the reliability requirements.)
If so: how?
If not: how else can they be verified? Inspections? Formal methods?
What more should be done to validate the system?

S5 Maintenance, Change, Reuse, Management, Planning, Quality

Not all of these questions are relevant to all systems. And there are too many questions anyway. So select some and concentrate on those.

Maintenance, Change

the introduction of the Euro?
use in a foreign country?
use by the military?

Reuse

Management, Planning

Can you propose a time plan for constructing your product?
What would be the estimated cost?
How would you determine the price?

Management, Quality

Creating reusable components
People and company careers
Quality improvement

S6 A War Story

Part one of the story will have been distributed. Make sure that you have read it, and bring it!

Apart from the questions at the end of part one, 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, assignments and seminar/guest lecture attendance. That is, the exam will not be given a grade by itself.

Item	hours	grade points
Exam and reading time	60	50
Seminars/guest lectures	40	10
Assignment 1	30	20
Assignment 2	30	20
Assignment 3 only NVP/free/exchange students	40	20
Required for G DVP		58 of 100
Required for VG DVP		75 of 100
Required for G NVP/free/exchange		70 of 120
Required for VG NVP/free/exchange		90 of 120

The limits for G/VG are estimates and can be adjusted slightly.

4.2 Assignments

Assignment 1. Start: 5/11. Deadline 25/11 at 10:15.
Assignment 2. Start: 29/10. Deadline part 1: 12/11 at 15:15, part 2: 2/12 at 10:15.
Assignment 3. Start: no later than 26/11. Deadline 20/12 at 12:00. Note the planning meeting on 26/11, at the end of the lecture.

Completed assignments should be put into Annika's mailbox (floor 4, number 46) 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 Roland is in his office (1356).

4.3 Grading

Seminars and guest lectures These points are essentially free, provided that you attend the lecture/seminar and that you say something intelligent in the seminar now and then. (No, talking in your sleep doesn't count.) You must represent your group at least once.

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), Bengt Jonsson's handouts and the articles (as listed on the index sheet).

4.4 Some sample exams

98/05. Sketchy answer sheet.
98/06. Sketchy answer sheet. In Swedish.
99/05. Sketchy answer sheet. In Swedish.
00/05. Sketchy answer sheet.
00/06.
00/08.
00/12. Sketchy answer sheet.
01/01.
01/12.
02/01.
02/05.
02/08.

rolandb@csd.uu.se

Roland Bol