3. One of the main problems when designing external iterators is robustness. Explain one 6.

6. Briefly explain the purpose of the technique known as “fault seeding”.

possible situation in which robustness of the iterator may be challenged. (4 points)

The quality improvement should come from the fact that two pairs of eyes see more than
one, and the copilot should be able to spot errors before the pilot. It might fail to do so if the
personalities of the members do not match, and also if their levels of expertise differ by a
wide margin.
4. List two reasons why small, frequent releases may be beneficial in the process of software 7. Explain briefly why the incremental integration of different units in a software application is
development. (4 points) preferable to the big-bang approach.

5. The hierarchical structure like the one below is not very flexible in view of changes it may 8. Briefly explain what are regression tests.
encounter later in its lifetime. Please show one possible way to achieve that.

1 * 1 * 1 *
operating unit region division sales office

9. List three pieces of information written on a CRC card.

 10. Check the appropriate column to indicate whether the statement is true or false. comp3350 Software Engineering
(1 point for each correct answer.) Term Test 1 held on Wednesday, February 21, 2007
T F statement
The waterfall model is characterized by strict separation of stages (phases) Student
F
and document-driven transition from one stage to the next one. Name
In Extreme Programming, scope is considered the most important of the four
F control variables; success can be achieved by adjusting the scope to fit the
ID
available resources and desired time and quality.
UML sequence diagrams may represent actors and classes, but not Notes: 1. This is a closed book quiz.
individual objects (class instances). 2. All communications between students are considered harmful.
3. Read carefully, if in doubt, raise your hand and the instructor will come to help.
In Extreme Programming, technical decisions are made by both business 4. Read all questions, answer the easiest ones first.
F
and technical people (i.e., customers and developers). 5. Do not explain the concepts unless explicitly asked for, in all cases, answer briefly
and to the point.
In test-driven development, all tests must be written before you start writing
T
the production code.
Short answer True/False TOTAL
In the process of fixing defects, new defects may be introduced; this is known (9 @ 4) (14 @ 1) (max 50)
T
as the ripple effect.

Formal code inspections are designed to identify and correct defective or

T
problematic code.
UML has more than ten different kinds of graphic (i.e., diagramming)
T
notations.
1. List one reason why pair programming should improve the quality of the code produced, as
F Unit tests are typically white-box tests. well as one reason why it may fail to do so. (4 points)
T Each user story should be accompanied by at least one acceptance test. The quality improvement should come from the fact that two pairs of eyes see more than
Design patterns are sometimes classified into structural, behavioral, and one, and the copilot should be able to spot errors before the pilot. It might fail to do so if the
F personalities of the members do not match, and also if their levels of expertise differ by a
temporal.
wide margin.
T User stories are typically more complex than user cases.
2. Briefly explain why it may be impossible to cover all paths in the process of testing, even for
The process of verification attempts to answer the question “Are we building code units of moderate size. (4 points)
F
the product right?”

Inspection and testing are complementary activities: both are useful, only in
T
different ways.