UU | CSD | Datalogi | Research | Education | Addresses | Staff


Software Engineering Spring 2000


Lecturer: Roland Bol, email rolandb@csd.uu.se. Last changed 000810 17:35.

0. News

The third exam has been corrected, and the course is now closed (except that some third assignments are still expected).

The first exam.
The second exam.
The third exam.
The results are in the table. You can pick up the exams at the student office: house 2, room 103. A brief facit of the first exam is available.

Course evaluation:

Short description of Assignment 3 added.

Detailed results of Assignment 1 added.

Links section added. This section should be particularly useful for Assignment 3. Feel free to contribute links.

1. Course start

1.1 What course?

This course actually consists of four(!) courses taking the same lectures. These courses are
codeSwedish name points Programmes
1TT892Programvarumetodik 2F, IT
1DT649Programvarumetodik 3MN, free
2AD064Programvaruteknik DV1 4DVP
2AD517Programvaruteknik MN1 5MN, free
The English name of all 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. MN and free students accepted to the 3 point course can be registered on the 5 point course if they want to.

1.2. Registration

If you want to take the course, but you are not registered (your name is not in the list of groups), then notify the lecturer.

1.3. Language

The course will be given in English. The DV seminars will be in Swedish. Perhaps a guest lecture might be in Swedish. Assignments may be handed in in English or Swedish.

1.4. Literature

The main course book is Software Engineering 5th edition, by Ian Sommerville.
Buy this book now and start reading in time! You are supposed to read the relevant chapters before the seminar covering them. Otherwise your participation in the seminar will suffer.

For the 3, 4, and 5-point courses, a collection of articles complements the book. It is sold at UTH-gård for SEK 35.

2. Schedule

The schedule consists of lectures (L), guest lectures (G), seminars (S) and exams (E). Note that the lines marked XXXX are cancelled.

2.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.

2.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).

2.3. Seminars

Seminars are held in groups of around 30 students. We have scheduled one group for DVP students and one groups for other (mainly F) students.

For the seminars, the students are divided in groups of 5 or 6. 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 20-40 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. Attendence is in principle obligatory (see also grading).

2.4. Time and place

All lectures etc. start at h:15. The exams start at h:00.

Room numbers:

Type Day Time Room Subject Chapters Important sections
week 12
L22/3 81211 Introduction; products; software lifecycle 1, 2 1.1, 1.2.1, 1.3, 1.4, 2-inl.
week 13
L 27/3102005 Requirements, Views and Models 4 - 7 2.2, 2.3.1, 4-inl., 4.1, 4.3, 4.4, 5-inl., 5.1, 6-inl., 6.4, 7 (all but 7.2.2)
G29/3 8 1211 Roland Bol: Requirements management in Telecommunication, the ARENA project.
L Early Validation and Verification 8, 9 8-inl., 8.1, 9 (all but 9.3)
XXXX29/3 10 1212 Requirements engineering
S F30/3 8 2
S DV30/3 15 1113
week 14
L3/4 10 1211 Design, Safety Critical Systems 12, 13, 15, 21 12, 13-inl., 13.1, 13.2, 15.1, 15.2, 21-inl., 21.2
G4/4 10 1211 Mattias Ersson (NTier Solutions): Software Architecture
XXXX4/4 13 3
  • Present an architectural design.
  • What parts are safety critical? What are the safety requirements and how are they enforced?
S DV4/4 13 1211
note swap with AA
S F5/4 8 6002
G5/4 131211 Lars-Henrik Eriksson (Industrilogik): Formal Methods for Safety Critical Systems
week 15
L10/4101211 Static Verification, Testing and Reliability 18, 19, 22, 24 18 (all but 18.4), 19-inl., 19.1 except 19.1.2, 19.2, 22-inl., 22.1, 22.2, 22.3.5, 24.1, 24.4
G11/4 8 2005 Krister Ström (Enea Data): Testing
G12/4 8 1211 Bengt Jonsson (ASTEC): Defect Testing23 23-inl., 23.1, 23.3
S DV13/4 15 1113
  • What are the reliability requirements (quantify!)? How are they measured?
  • Will you apply static verification? How will the system be tested? Relate the tests to requirements.
S F14/4 8 4
XXXX14/4 104
week 16: vacation
week 17
L25/4 81211 Maintenance; Change, Reuse; Re-engineering 20, 32 - 34 20-inl., 20.1, 20.2(until "C++"), 20.3, 20.4-inl., 32 (all but 32.4.1 and 32.5), 33-inl., 33.2, 33.3-inl., 33.3.2, 33.4-inl., 34
L26/4 8 2005 Planning, Management 3, 28, 29 3 (all but 3.4.1), 28.4, 28.5, 29-inl., 29.1, 29.2
S F26/4 10 2002 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)
S DV26/4 15 1246
XXXX27/4 10 4
week 18
L 2/5 82005 Quality 30, 31 30-inl., 30.1, 30.3, 30.5-inl., 31-inl., 31.4, 31.5,
9.4 and 9.5 from "Confessions ..."
G 3/5 8 1211 Ola Jirlow (Prevas): Planning, Management, Quality
week 19
G 9/5 101211 Lars Asplund (UU): Using Ada for large software projects.
L11/5 101211 Questions, old exams
Exams
E15/5 9-14PS1 .
E17/6 9-14PS1
E10/8 9-14PS1

Chapter 10, 11, 14, 16, 17, 24.2, 25, 26, 27, 28.1, 33.3.3, 33.4.1 are not coverd in this course.
"2-inl." means the introduction of Chapter 2, before Section 2.1 starts.

3. Assignments, exams, grades

3.1 Overview of estimated time spent, and grading

Item hours grade points
course (points): 2 3 4 5 2 3 4 5
Reading/exam 6060606040505050
scheduled time
(seminars/guests)
4040404010101010
Assignment 2:
selected articles
- 303030 -202020
Assignment 1:
requirements spec.
- - 3030 - -2020
Assignment 3:
topical study
- - -40 - - -20
SUM 1001301602005080100120
Required for G/3 2845 58 70
Required for 4 36
Required for VG/5 4260 75 90

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

The exam covers the book, except the chapters listed above, the general content of the guest lectures (but no technical details), and issues that come up at the seminars. The exam for the 3, 4, and 5 point course also covers the articles, as listed on the index sheet.

3.2 Assignments

Assignments should be put into my mailbox (floor 4, number 28) before the deadline (below). If you have questions, you can send email or see if I'm in my office (1356).

Deadlines:

3.3 Grading

3.4 Some sample exams

4. Miscellaneous links


Last changed 000810 17:35.
Roland Bol / rolandb@csd.uu.se
This page is http://www.csd.uu.se/~rolandb/PVT-vt00