Home
Education Page
Description
Schedule
Slides
Assignments
Projects
Reviews
Literature

Center
Master Program

Center

Page

Web

Wiki

Log In or Register

Paper Reviews

Swe03
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 the paper within software engineering (150 words)
  • summarizes the paper (350 words)
  • summarizes the lecture (350 words)
  • discusses the relation between the paper and the lecture (150 words)

Positioning the paper should be done with respect to the relevant chapter in the Guide to the Software Engineering Body of Knowledge as cited below.

Format

  • Write the review in english
  • Use your own words! Copy and paste is plagiarism
  • Format the review in ASCII
    • lines should be no wider than 80 characters
    • use blank lines to separate paragraphs
    • use -----+++ title to indicate headings
    • no other markup should be necessary
    • submissions in other formats will not be considered

  • Don't forget to include your name and student number.

Workcycle

  1. Monday: attend lecture, get paper via website
  2. Whole week: read paper and write review
  3. Next Monday: 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. This corresponds to numeric grades 4 - 0. The final grade for reviews is the sum of the grades divided by 4n times 10. 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 Monday following the week in which a paper should before 12:00. It should be handed in using the submit system. The deadline is hard; it is not possible to submit reviews after the deadline.

Papers

Requirements engineering (week 36)

  • Note: since the lecture was about the whole software lifecycle, summarize Chapter 2 of the SWEBOK instead of the lecture and place the paper in the context of the general RE picture.

Version management (week 37)

Software process (week 38)

  • The assignment for this week is a little different: Write a 1000 word overview of extreme programming process model, outlining its main ingredients, and indicating what makes it different to other models. The Extreme Programming Roadmap is a good entry point to the numerous sources on XP.

Software testing (week 39)

  • Adam Porter, Harvey Siy, and Lawrence Votta. A Review of Software Inspections In Marvin Zelkowitz, editor, Software Process, volume 42 of Advances in Computers. Academic Press, 1996.

Software reuse (week 41)

  • Charles Krueger. SoftwareReuse in ACM Computing Surveys, June 1992, pages 131-183.

Software metrics (week 42)

Software maintenance (week 43)

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

Software logistics (week 44) (bonus)

This review is optional. If you failed a previous review you can improve your score by making this one. Indicate in the review which review you want to replace.