Tutorial Letter 101 / Studiebrief 101 School of Computing ... - Name
Tutorial Letter 101 / Studiebrief 101 School of Computing ... - Name
Tutorial Letter 101 / Studiebrief 101 School of Computing ... - Name
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
3. Problem domain component<br />
4. All <strong>of</strong> the above<br />
33. S<strong>of</strong>tware engineers always need to create components from scratch in order to meet customer<br />
expectations fully.<br />
1. True<br />
2. False<br />
34.<br />
Which <strong>of</strong> the following is not one <strong>of</strong> the four principles used to guide component-level design?<br />
1. Dependency Inversion Principle<br />
2. Interface Segregation Principle<br />
3. Open-Closed Principle<br />
4. Parsimonious Complexity Principle<br />
35.<br />
The use <strong>of</strong> stereotypes can help identify the nature <strong>of</strong> components at the detailed design level.<br />
1. True<br />
2. False<br />
Chapter 17<br />
36. In s<strong>of</strong>tware quality assurance<br />
work there is no difference between s<strong>of</strong>tware verification and<br />
s<strong>of</strong>tware validation.<br />
1. True<br />
2. False<br />
37.<br />
The best reason for using Independent s<strong>of</strong>tware test teams<br />
is that<br />
1. s<strong>of</strong>tware developers do not need to do any testing.<br />
2. strangers<br />
will test the s<strong>of</strong>tware mercilessly.<br />
3. testers do not get involved with the project until testing begins.<br />
4. the conflicts<br />
<strong>of</strong> interest between developers and testers is reduced.<br />
38. What is the normal order <strong>of</strong> activities in which traditional s<strong>of</strong>tware testing is organized?<br />
a. integration testing b. system testing c. unit testing d. validation testing<br />
1. c, a, d, b<br />
2. d, c, a, b<br />
3. c, b, a, d<br />
4.<br />
a, c, b, d<br />
20<br />
39.<br />
By collecting s<strong>of</strong>tware metrics and making use <strong>of</strong> existing s<strong>of</strong>tware reliability models it is possible<br />
to develop meaningful guidelines<br />
for determining when s<strong>of</strong>tware testing is done.