SE Spring 2010

Software Engineering Spring 2010

Table of contents:

0. News
1. Teaching staff
2. Course start
3. Schedule
4. Assignments, exams, grades

0. News

  • The questions to the first exam.
  • 10-03-12 Slides from Accenture/Avanade are in the File area of the Student Portal.
  • 10-03-12 The material on Agile methods has now come in. See the link in the schedule.
  • 10-02-02.Due to a confusion between me and the guests, the guest lecture that was scheduled today will instead be held tomorrow (3/3) at 10-12. (Presumably still in room 1245).
  • 10-03-01. Small update on Accenture's guest lecture.
  • 10-02-12. The schedule for the remaining guest lectures is now confirmed.
  • Printer-friendly version of this page.

1. Teaching staff

Name  E-mail  Room  Phone  Mailbox
(4th floor, building 1) 
Lecturer  Roland Bol 1356  018-471 7606  28 

2. Course start

2.1 What course? 

Code  Swedish name  Credits English name
 1DL250 Programvaruteknik  Software Engineering

2.2. Registration

Students who have been accepted (antagen) to the course and exchange students will be registered at the first lecture. It is also possible to register through Studentportalen.

2.3. Language

The course will be given in English. 

2.4. Literature

The main course book is Software Engineering, 7th or 8th edition, by Ian Sommerville.
(These editions are identical, except that the 8th edition includes some new chapters - these chapters are however not treated in the course.)
The 6th edition can also be used (check from the 7/8th ed. sections: 4.4, 12.4, 13, 17, 19, 24.4, 28.6) Reading instructions for the 6th edition.

Buy the book now and start reading in time!

2.5. Links

  • I have been asked in course evaluations to provide a real-life example of a requirements specification. I found the following specification ; notes
    • It's 151 pages - browse it, don't waste paper on it
    • It does not exactly follow our template - there are many such templates around
    • The source is OPF.
    • I'm not sure that it's actually real-life (in the sence that it was meant to be implemented), but it could be.
    • You're not supposed to write 151 pages in such detail for assignment.

3. Schedule

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

3.1. Lectures and ...

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.  
There are 3 guest lectures and a seminar (schedule still subject to change!). 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.
On February 5, there is a session at the library about finding literature. This is relevant for the assignment.

3.4. Time and place

All lectures etc. start at 15 minutes past the hour. The exams start on the hour.
(L = lecture, G = guest lecture, S = seminar, E = Exam)
Type  Day  Time  Room Subject  Chapters (7/8th)
Important sections (7/8th)
week 3
L 19/1  8
Introduction: schedule, assignment, etc.
Software processes
1, 4.1, 4.2, 4.3.3,

4.1.1, 4.2.1, 4.3.3

L 21/1  10
Requirements, Buy and/or build?, Requirements Engineering  4.3.1, 6, 2.3.1, 7
4.3.1, 6-in, 6.1, 6.2, 6.3-in, 6.5, 2.3.1, 7.2, 7.4
week 4
L 26/1
Models and Prototypes, Agile&Lean
4.1.2, 8, 17
4.1.2, 8.2, 8.3, 8.4.3, 17-in, 17.4
Design, Reuse
4.3.2, 11, 12, 13, 18, 19
4.3.2, 11-in, 11.2, 11.4, 12-in, 12.2, 18-in, 19.2
L 29/1
Validation and Verification: inspections and testing
4.3.3, 7.3, 22, 23, 24.1-in
4.3.3, 7.3, 22-in, 22.2, 23-in, 23.1, 23.3.1, 23.4, 24.1-in
week 5

Dependable Systems
3, 9, 20, 24
3-in, 3.2, 3.4, 9 (except 9.3), 20-in, 20.1, 20.2.2, 20.4
Guest lecture Lars-Henrik Eriksson: Industrial Applications of Formal Methods 
10, 22.4-in
10-in, 10.1, slides

The Ångström Library, room 11240 (Floor 1 in house 1, between house 6 and 8 in The Ångström Laboratory). Invitation. See also Assignment,  below

week 6
L 8/2  8
1245 Defect Testing 
23.3.2-23.3.4, summary
mid-course evaluation (see below)
Maintenance, Evolution,
Legacy systems, Config. management

21, 29

2.4, 21.4
Project Planning,
Software Cost,
26-in, 26.2, 26.3-in,
25.3.4, 25.3.5
week 7
Quality Assurance
Process Improvement
Combined processes
22.4.1, 4.4, 17.2
27-in, 27.1, 27.5,
28-in, 28.2, 28.5, 28.6
22.4.1, 4.4, 17.2
Case study (A War Story)

week 8
Assignment, see below
week 9
Guest lecture Accenture - Henrik Boström och Johan Nedin

Guest lecture Mikael Lundgren (Citerus) Introducing Agile methods
Swedish version   English version
17.1 remember to sign up for the exam!
week 10
Questions, old exams

E 17/3 tba

details to be announced

Exam Polacksbacken

"x-in." means the introduction to Chapter/Section x, before Section/subsection x.1 starts.
The mid-course evaluation, is an evaluation of the course (right speed, interesting?) - it is not a test!

Chapters 14, 15, 16 are not covered at all in this course.
Chapters 30, 31, 32 (8th ed.) are not covered at all in this course.

3.4.1 Guest lectures

Formal methods are presented by Lars-Henrik Eriksson, currently a lecturer at UU. Lars-Henrik has industrial experience of the application of formal methods, mostly in railway signalling systems. He works part-time at the company Nya Industrilogik.

Accenture has two presentations
  • Offshoring and how it affects the IT market in Sweden and how Accenture handles this (Henrik Boström)
  • Time estimation for IT projects (Johan Nedin)
For more information about Accenture visit:
Did you know that Accenture was rated to be 'Störst och bäst på IT' by 'Veckans affärer':

Citerus will be represented by Mikael Lundgren. Being a DV alumni, Mikael has worked as a software developer, project manager, Scrum Master and development manager. Today he is a consultant, helping software companies improve their work using Lean and Agile development frameworks. Mikael became a Certified Scrum Trainer in 2006, out of 50 worldwide.

  • What is Citerus, and what do we do? (5 mins)
  •  Lean and Agile - an overview and history
  •  How does Agile Software Development work? Why does it work?
  •  Scrum, the roles in Scrum, why Scrum is different
  •  Scrum projects vs traditional projects
  •  Continuous learning and improvements
Very much welcome!

3.4.2 Seminar: A War Story (Case Study)

This is a case study (story) in 4 parts. We will put ourselves in the position of the project manager ("you"), and discuss "your" options/choices.
Part one of the story will be distributed on February 16. Make sure that you have read it (*), and bring it!
The rest of the story will be handed out in episodes (2-3 pages) during class.

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

  1. What additional information would you want to have?
  2. What are the risks? Separate high risks from lesser risks.
  3. What would you do next?
(*) Clarification of a detail in the text: "your" whole group is joining this project: 20 programmers, 2 first-level managers, a secretary and a typist.

4. Assignments, exams, grades

4.1 Assignments

There are two alternative assignments - meaning that you do only one of them

   4.1.1 Choice 1: Summarize an article in Software engineering

  • Choose a topic in Software Engineering that you would like to know more about.
  • Find an article (suggested 10-15 pages) on this topic. The library visit on Feb. 5 is intended to help you in your search.
    The article can be a paper directed to industry (for example, the longer papers in IEEE Software) or a purely scientific paper (as in IEEE Transactions on Software Engineering).
    Note: these two journals are only examples - there is much more out there. A combination of shorter articles may also be acceptable.
    The article need not be recent: you can also choose a "classic" - IEEE recently listed their "classics" over the last 25 years.
  • When you have selected the article, send me title, journal, and (preferably) a link. This should be done no later than February 16.
  • Write a report on the article. The report must summarize the material, and then also include your own judgement and ideas. What are the authors main points? Do you agree?
  • Deadline: 19/3 at 17:00.

   4.1.2 Choice 2: Participate in the requirements engineering project of the course User-centered Systems Design in week 8 

  • This option is not open to students registered on the UCSD course - obviously!
  • If you want to take this option, let me know no later than February 16.
  • Lectures: Wednesday 24/2, 13-17 and Thursday 25/2, 10-15, room 1111. 
  • The assignment.

4.2 Exam and Grading

  • Assignments are graded pass/fail (maybe with a small bonus possible, must check with UCSD first)
  • Exam The exam has 60 points. The weight of each question will be on the exam. The exam covers the book (except the chapters listed above).
You can receive the grades 3, 4 or 5 on the exam - the course grade is the exam grade.

max points

These boundaries are preliminary and indicative.

Some sample exams

Note that the contents of the course have changed over the years: some questions refer to material that is no longer included, or guest lectures that are no longer given. Some new material is included now, about which there are no questions in older exams. I can comment details in the final lecture.

Roland Bol