1. Tutorial 2, Q1
State the five scales used in measurement and describe the most important aspects which distinguish them. For each of the following statements, explain whether or not it is meaningful and if the statement is meaningless say whether there is a “quick fix" which could make the statement more meaningful.
(a) 100C is the boiling point of water. (b) Today is twice as hot as yesterday. (c) The FT index fell 325 points today. (d) The program is 50 lines of code long. (e) The program took 3 months to write. (f) The testing on this project took twice as long as the programming. (g) The cost of maintaining program B is twice that of maintaining program A. (h) Program A is more complex than program B.
Here is your first tutorial. You will need to print this out (or bring it on your laptop, if you are fortunate enough to have a laptop). As with all tutorial questions (aka workshop exercises), the questions start off easy and get progressively harder. If you can manage the first one or two questions on each exercise by the end of the course, then you should have little difficultly passing the exam.

2. Tutorial 2 Q2
Give five criticisms of lines of code as a software measurement of size. That is, give five examples of parts of code which may (or may not) be counted as a line of code.

3. Tutorial 2, Q3 Give the CFG for the following program schematic.
Calculate the number of nodes and number of edges for it by working though the hierarchical definitions given IF(...)THEN x:=1 ELSE x:=2 FI ; y:=50 ; IF (...) THEN z:=1 ELSE DO WHILE (...) z:=z+1 OD FI ; y:=0

4. References
Norman Fenton: “Software Metrics: A rigorous and practical approach” (2nd Ed) N.E. Fenton and S.L. Pfleeger, Thompson Computer press, 1997.
Martin Shepperd: Foundations of Software Measurement, Prentice-Hall, 1995.
These are both excellent textbooks and each covers all the material on measurement needed for this course (and much more).