Paper Reviews

Experience is a good way to understand the issues involved in software engineering. However, to better tackle the problems you encounter, you should get an overview of software engineering theory as well. In this course you are expected to read one paper each week and hand in a review of the paper which expresses your understanding of the paper, as well as its position in the field of software engineering. Furthermore, you are expected to summarize the lecture of that week and discuss its relation to the paper.

Reviews

Structure

For each of the papers below, write a review of 1000 words which

• positions paper and lecture within software engineering
• summarizes the paper
• summarizes the lecture
• discusses their relation to the relevant laws and principles of software engineering as described in the Handbook of Software and Systems Engineering

Format

• Write the review in english
• Use your own words! Copy and paste is plagiarism
• Format the review in twiki markup
• The review should be placed in your personal wiki web at the ST IntraWiki

Workcycle

1. Attend lecture, get paper via website
2. Whole week: read paper, read book, and write review
3. Next Tuesday: deadline for review
4. Goto 1

You are responsible for keeping the schedule.

Grading

Reviews will be graded with a grade in the range A - D, F. These correspond to numeric grades in the range 1-10 as follows:

Grade	Numeric	Interpretation
A	10	Excellent
B	8	Good
C	6	Pass
D	4	Insufficient
F	1	Fail

The final grade for reviews is the average of the grades for the individual reviews. Note that all reviews should be handed in.

Grades are determined based on the following points

• Adequate summary of paper and lecture
• Good understanding of position in software engineering
• Quality of writing (grammar, vocabulary, structure)

Submission

Reviews are due on the Tuesday following the week in which a paper should be read before 13:00. It should be submitted by placing it on your personal wiki web at the IntraWiki. For each day that a review is late a point is subtracted from your grade.

Papers

(Note that some of the papers are available from the ACM digital library; these papers can be downloaded from a computer at the University or via VPN.)

Requirements engineering (week 37)

• B. Regnell, K. Kimbler, and A. Wesslen, "Improving the Use Case Driven Approach to Requirements Engineering", Proc. RE'95 - 2nd Int. Symp. on Requirements Engineering, York, IEEE, 1995, 40-47.

Software Configuration Management (week 38)

• Walter Tichy. Software Configuration Management Overview.

Software reuse (week 39)

• William Frakes and Carol Terry. Software reuse: metrics and models. ACM Computing Surveys 28 (2), 415 - 435, June 1996.

Software testing (week 40)

• Sebastian Elbaum, Srikanth Karre , Gregg Rothermel. Improving web application testing with user session data. In Proceedings of the 25th international conference on Software engineering (ICSE'03). pp 49-59. Portland, Oregon, 2003.

Software metrics (week 41)

• Serge Demeyer, Stéphane Ducasse, Oscar Nierstrasz. Finding refactorings via change metrics. In Proceedings of the 15th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications. pages 166 - 177. Minneapolis, Minnesota, United States. ACM 2000.

Component Based Software Engineering (week 42)

• Clemens Szyperski. Component Technology - What, Where, and How? 25th International Conference on Software Engineering. Portland, Oregon, May 03 - 10, 2003.

Software Product Lines (week 43)

• Rob van Ommering and Frank van der Linden and Jeff Kramer and Jeff Magee. The Koala Component Model for Consumer Electronics. IEEE Software Computer, 33(3), pp. 78-85, March 2000.

Software evolution (week 44)

• David Lorge Parnas. Software aging. In Proceedings of the 16th international conference on Software Engineering (ICSE'94). pp 279 - 287. Sorrento, Italy, 1994