Software Engineering for Students A Programming Approach

Summary 287
The strategic thinking considers the role of the method within the class, and whether
this method is appropriate within the context of the whole system. The person thinks
about such questions as: Which other components use it? Can the system be simplified so
that this method is just not needed? Can the method be generalized so that it is more widely
useful? Is this method in the right place, or should it be relocated into some other class?
The pair periodically switch roles, so that overall they are working as equals. Pairs
don’t stay together, but change from day to day. It simply depends on who is available,
but the people are drawn from the same project team, so they have a shared understanding
of the project. And no one forces people to pair up if they do not get along.
When a pair starts work, it may be that one person will have more experience or
expertise. Later, the gap narrows, so that they are genuinely collaborating on an equal
basis, one person’s strengths compensating for the other’s weaknesses.
The central feature of pair programming is that two people are communicating
intensely, sharing ideas, learning from each other, supporting each other, articulating
ideas verbally and solving problems. It is creative, sociable, enjoyable and effective. It is
claimed that pair programming improves productivity, code quality and job satisfaction.
Even though, at first sight, twice the effort is spent on development, the time is more
than reclaimed in more effective working.
Of course, pair programming means that pairs of people are working closely – almost
intimately – together. This depends on an organizational culture that is collaborative
and supportive.
20.6 ● Discussion
Perhaps the ultimate method for collaborative working aimed at reducing bugs is open
source development. This is such an important technique that we devoted a whole separate
chapter to the topic.
How effective are the techniques of walkthroughs, inspections and pair programming?
The answer is that they are surprisingly effective as compared with using testing.
We review the evidence in Chapter 31 on assessing methods.
Summary
A structured walkthrough is a meeting at which a document is examined by a group
of people in order to find errors. Structured walkthroughs are based on the premise
that ideas that are shared will be the better for it. The careful organization of a
walkthrough is important. Walkthroughs can lead to improved software quality –
reliability and maintainability – because of the scrutiny of project material by a
group. Effort can be reduced and deadlines more easily met.
Inspections are a more formal approach to a group review meeting.
In pair programming, two people sit at the computer, working closely together on
design, coding and testing.