Assignment 2

Software Engineering Spring 2005


Slides from lecture can be found here

Part A - test specification

Based on your own requirements document, you must prepare test cases. For each test case, you must give
Make sure that all requirements that apply to the simple ray tracer are tested!
Plan ahead for running a serious number of tests in an efficient way.

Read an XML presentationPDF-dokument (OH in Swedish) or a short introductionExtern länk to XML (in English). Or search the web for an XML tutorial. The DTD for the ray tracer files is at Example test files in xml- and ppm-format can be found at Use the program xview to view ppm-files.

To create or edit XML-files you may use the XML-editor xmlproExtern länk . Run it by the command /it/kurs/pm2/vt04/xmlpro. DocumentationPDF-dokument is available in pdf-format. Before you can run xmlpro you must copy the license file /it/kurs/pm2/vt04/xmlpro2.01/xmlpro.prp to the directory that is your working directory when you run xmlpro.


The Methods of Programming course students are now working on their assignment 2 - the simple ray tracer. You have to agree with them on internal deadlines that allow you and them to make the external (i.e. the teachers') deadlines. Specifically, you have to agree on dates

Part B - test report

Run the test cases that you planned to run according to part A (after comments of Anders Hessel) and documents the results in an appropriate way (e.g. an overview table with test run identifier, pass/fail, comment and then the individual test runs).

Part C - code review 

  1. Preparation: before the inspection you need:
  2. Overview meeting: the programmers present their code.
  3. Individual preparation: the SE students go through the code, identify potential errors and problems, and write them down on the protocol form.
  4. Inspection meeting: (for roles see Sommerville Figure 22.5 (6th ed.: 19.5) - the MP students can alternate between the roles of author and reader, the SE students between inspector and moderator/scribe). At this meeting, the protocol is updated: is there an error? severity?
The code review, together with the code that it refers to, is handed in to the assistant of the Methods of Programming course.