SE Autumn 2010

Software Engineering Autumn 2010

Table of contents:

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

0. News

  • 101216 The exam is corrected. Here are the questions with a checklist what should be in the answers.
    The administrative process will take some time due to the anonymous exams. I expect that you can pick up your exams from the room opposite the IT-office on Wednesday Dec. 22. I'll be away on vacation, so questions will have to wait until January 10.
  • 101116 Some administrative instructions for the assignment added, further update of reading instructions.
  • 101103 Working on the reading instructions for the 9th edition. I'll stay ahead now. The assignment has now a link to Sommerville's suggested reading.
  • 101028 - The exam is moved to December 10 (some students plan to leave on or before Dec 17).
    To give time for the exam, the deadline for the assignment is moved to January 6.
  • 101027 - Conversion table for Chapers in the 9th edition of the book (below the schedule). More detailed instructions will follow.
  • 101027 - The session on Dec 7 is moved to a larger room (2446)
  • All guest lectures confirmed.
  • Printer-friendly version of this page.

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 

2. Course start

2.1 What course? 

Code  Swedish name  Credits English name
 1DL250 Programvaruteknik  5  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 9th edition is out! It is better than the 7th/8th edition.
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 4 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.

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 (9th)
 Important
sections (9th)
 Chapters
 (7/8th)
Important sections (7/8th)
week 43
L 26/10
8
 1211
 Introduction: schedule, assignment, etc.
Software processes
 1.1, 1.2, 2.1, 2.2.3, 2.3.2, 2.3.3
2.1.1, 2.1.2, 2.2.3
 1, 4.1, 4.2, 4.3.3,

4.1.1, 4.2.1, 4.3.3
L 29/10
13
 1111
 		Requirements, Buy and/or build?, Requirements Engineering  2.2.1, 4, 10.3
 2.2.1, 4-in, 4.1, 4.2, 4.3-in, 4.3.1,
10.3, 4.5, 4.7
 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 44
L 1/11
 13
 1311
 Models and Prototypes, Agile&Lean
 2.3.1, 5
 2.3.1, 5.2, 5.4
 4.1.2, 8, 17
 4.1.2, 8.2, 8.3, 8.4.3, 17-in, 17.4
L
 5/11
 8
 1311
 Design, Reuse 2.1.3, 2.2.2, 6, 18, 16, 17
 2.1.3, 2.2.2, 6-in, 6.3, 18-in, 18.2, 18.3.2, 18.3.3, 16-in, 17.2
 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
week 45
G
 9/11
 10
 1311
 Mikael Lundgren (Citerus)
Agile and Scrum
 3
 3.1, 3.4
 17.1, 17.2
 17.1 (+new material)
L 10/11
 10
 1311
 Validation and Verification: inspections and testing
 2.2.3, 4.6, 24.3, 8, 15.2
 2.2.3, 4.6, 24.3, 8-in, 8.1.4, 8.2, 8.3.1, 15.2
 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 46



L
 15/11
 13
 1211
 Dependable Systems

 10-in, 10.1, 10.5.1, 11, 12, 13
 10.5.1, 11-in, 11.1, 11.3, 12-in, 12.1, 12.2, 12.3, 13.2, 13.4
 3, 9, 20 3-in, 3.2, 3.4, 9 (except 9.3), 20-in, 20.1, 20.2.2, 20.4
G
 18/11
 13
 1311
 Lars-Henrik Eriksson (UU, Nya Industrilogik):
Industrial Applications of Formal Methods
12.5, 15.1, 15.4, 15.5-in
 15.1, slides 10, 22.4-in, 24.2, 24.4  10.1, slides
week 47
G
 22/11
 13
 1211
 Jonas Billing (Accenture)
 22
 22.3
 25
 25.3
L
 24/11
 8
 1311
 Defect Testing
mid-course evaluation (see below)		 8
 summary,
8.1.1-8.1.3
 23 23.3.2-23.3.4, summary
G
 26/11
 13
 1311
 Håkan Engvall (Imentum)
Development of secure systems
 11.4, 12.4, 14, 15.3
(2.4)
 11.4, 14.1, 14.2.3, slides
 3.5, 9.3, 24.3, 30 (4.4)
 3.5, 30.2, 30.3.3, slides
week 48
L
 30/11
 13
 1311
 Maintenance, Evolution,
Legacy systems, Config. management
 9, 25
 9.3-in, 9.3.2, 9.4, 25.3, slide
 21, 2.4, 29

 21.2-in, 2.4, 21.3.1, 21.4, 29.4, slide
L
 1/12
 13
 1311
 Project Planning,
Software Cost,
Management
 22, 23
 22-in, 22.1,  23.2, 23.3,
23.5-in, 23.5.1
22.3
 5
26
25
 5.2-5.4,
26-in, 26.2, 26.3-in,
25.3
week 49
L
 6/12
 13
 1211
 Quality Assurance
Process Improvement
Combined processes
 24
26
Cleanroom, 2.4, 3.3
 24-in, 24.1, 24.4
26-in, 26.4, 26.5
Cleanroom, 2.4, 3.3
 27
28
22.4.1, 4.4, 17.2
 27-in, 27.1, 27.5,
28-in, 28.5, 28.6
22.4.1, 4.4, 17.2
S
 7/12
 13-16
 2446
 Case study (A War Story) In English (Master, ...)



8/12
 13-16
 1245
 Case study (A War Story) In Swedish (IT, STS, ...)



L
 9/12
 8
 1311
 Questions, old exams



Exams
E 10/12 8-13
 5
 Exam Polacksbacken exam hall


details to be announced
E
 March 16
 tba
 tba
 Exam
E
 June

Exam

The mid-course evaluation, is an evaluation of the course (right speed, interesting?) - it is not a test!

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

Chapters (see also Sommerville's web page)

7/8th edition
 1
 2
 3
 4
 5
 6
 7
 8
 9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
9th edition
 1
 ~10
 11
 2
 22
 4 5
 12
 27
 6
 18
 6.4
 5, 7
 20
 29
 ~3
 16
 17
 13
 9
 15, 24.3
 8
 15
 22.2,22.3
 23
 24
 26
 25
 14
 19
 21

Chapters 14, 15, 16 (8th ed.) are not covered at all in this course.
Chapters 30, 31, 32 (8th ed.) are not covered at all in this course - except for the guest lecture on security.

3.4.1 Guest lectures

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
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 will be represented by Jonas Billing. Jonas Billing is a Senior Executive and the Country Lead for SI&T - Solutions in Sweden.
One of the key successes of Accenture is their offshoring model. For more information about Accenture visit: http://backstage.accenture.com/

Imentum, represented by Håkan Engvall, are experts on the development of secure systems.
This guest lecture is new in the course - thanks to  STS for the contact.

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 December 1. 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. Assignment, exams, grades

4.1 Assignment

This assignment is done individually.

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 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.
    Sommerville's suggested reading
  • When you have selected the article, send me by email title, journal, and (preferably) a link. This should be done no later than November 18.
  • Write a report on the article. The report must summarize the material (in no more than 2 pages), and then also include your own judgement and ideas. What are the authors main points? Do you agree?
  • Deadline: January 6. Hand in the summary through Studentportalen. I have also activated the progress function for the two steps of the assignment.

4.2 Exam and Grading

  • Assignment is graded pass/fail(=redo)
  • 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
  3
 4
 5
exam
60
 33
39
 45

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@it.uu.se

Roland Bol












































































Show printer-friendly page | Copyright © 2025 Uppsala University, Department of Information Technology.
Last updated 16 Dec 2010. Responsible: Roland Bol. Web: Contact.