Form 3.1: Due by November 2 at midnight.

Email to Baris Aydinlioglu (vb43520@umd5.umd.edu).

Name:

Document reviewed:

Reading Techniques Used (1-2), (3-4) or (5-7):

List the faults you discovered below, specifying the page number and the area in which each is found. Use the following codes for describing the fault area:

DE Class Design

DI Class Diagram

SEQ Sequence Diagram

STA State Diagram

Use the following codes for describing the fault class:

A Ambiguity

E Extraneous Information

IF Incorrect Fact

II Inconsistent Information

O Omission

M Miscellaneous Defect

Also rate the severity of the fault by assigning a rating for "importance" and "probability of causing an error" based on the following scales:

Importance:

0. not important, developer should easily see the problem
1. problem, if a failure occurs it should be easy to find and fix (e.g. change to 1 module)
2. important, if a failure occurs, it could be hard to find and fix (e.g. change to several modules)
3. very important, if a failure occurs, it could cause a re-implementation

0. will not cause fault or failure, will be caught by developer
1. could cause a failure but will most likely be caught by developer
2. would cause a failure

An example is provided. Take as much space as you need, and separate each fault with a blank line. Remember to keep a copy of this information for yourself!

When done, skip down to the end and answer the questions there.

Fault # Page # Area Importance Prob. Class Desc.

------ ------ ------ ---------- ----- ----- -----

0 2 DI 1 2 A Since this isn’t a real fault we’ll assign it a number of 0. Number your faults starting from 1, of course. This fault should describe some ambiguous information found in the class diagrams on page 2 of the design (If you cannot specify the area - for example, some faults may affect multiple sections of the document - leave this field blank.) This fault has a high probability of causing a failure (prob = 2) but is not too important because it should be easy to find and fix (importance = 1). In the description you need to explain exactly what the fault is so that it could be corrected.

Please answer the following questions. Your answers will be used to help us better understand the process, and will not impact the grading of this assignment:

1. How much time did you take to find faults (report just the time spent on looking for faults, not including interruptions, breaks, or other non-related activities)?
2. What percentage of the faults in the document do you think you found?
3. How closely did you follow the review techniques that were prescribed?

1. Very closely
2. Somewhat closely
3. Not closely at all

1. Do you have any comments on your opinion on the effectiveness of the review techniques? How difficult were the techniques to use and apply?

 




2. How adequate was the level of training you received in these techniques?

1. Too much training was given in class
2. The correct amount of training was given in class
3. Not enough training was given in class

1. Was it harder or easier to find faults in the design as opposed to the requirements? Why?
   
   
   
   
2. Was the taxonomy of design faults that you were given for this assignment useful (by taxonomy, we mean the class of the fault, i.e. "ambiguous," "incorrect fact," etc.). Why? Was it clear which class your faults belonged to?