Question

Question 1 (20 marks) State whether you (1) completely agree, (2) partially agree/disagree or (3) completely disagree with each of the following statements Justify your answers. Provide examples or counterexamples where appropriate (a) "Test fixtures are more useful in black-box testing than in white-box testing." 4 marks (b) "The immediate outcome of a code review is a highly cohesive piece of soft- ware. 4 marks (c) "Coupling issues can be fixed during maintenance, but also make maintenance more difficult." 4 marks [4 marks (d) "Business rules are not written as user stories." [4 marks (e) "Planning poker is a game of chance."

Answer 1

a)completely disagree
reason:-
software test fixture means to provide necessary code for initialization for the testing process.
in black box testing, tester is not aware of the internal details of the system.
in white box testing, tester needs to know internal details of the the system.
that's why test fixture are more useful in white box testing.

b)completely agree
reason:-cohesion focuses on relationship within the module.
the study is confine with in the module.
in case of cohesion,a module focuses on single thing, hence code can be reviewed immediately.

c)completely agree
reason:
coupling means dependency between modules.
one module depends on another.
it focuses on the relationship between modules.
coupling should be minimum to build a good software.
since one module is depending on another module, it means changes in one module can affects the another module.
if coupling is high, then to make any changes , programmer needs to know the details of other modules.
if the coupling issue is not taken care by the development team at the time of development,then fixing coupling issue at the time of maintenance makes software maintenance very difficult because it requires the study of all the modules.

d)completely agree
reason:- user story means scenario.
a scenario is an overview of a problem.
business rules are more precise.
it covers the requirements in detailed form.
business rules can not be written as user stories.
for example:-business rules specifies the conditions/validations in more precise form.
Example: user story/scenario
create a program to generate the bill for a customer.
customer can purchase many items.

business rules for the above scenario
1)customer bill should be auto generated
2)first bill no. should start with b100, second b101,...and so on.
3)if customer demands an item which is not present in the
shop or the demanded quantity is not available,then customer should be informed properly with the following message
item not available
or
required quantity is not available.
4)digits should not be allowed in customer name.

in this way many more rules can be described.
hence , it would be naive to say that

e)partially agree
reason:-
planning poker is a game of
1. making decisions(correct decisions greatly contribute in the winning )
2. chance(luck works)
3. skill(some mathematical exercise contributes in the winning)