|
|
|
|
Introduction People
expect software to be perfect – but it is not.
The IT industry has a truly appalling track record. Projects are
frequently late, over budget and we often discover errors in the system or
perhaps the wrong system has been delivered. As a result the relationship
between IT providers and its customers can become rocky. A way to improve is
needed. However,
there has been much argument over the years, about the principals, objectives
and limits of testing. What seems clear looking at the industry are that; it is
difficult, not as successful and takes longer than people imagine. For
instance, projects have customers and suppliers and teams. They must agree about
what the project is for and what is to be delivered. Remember that the customer
will WANT something, what they NEED may be different and what the supplier
believes they are going to deliver – their perception of what the customer
needs and what is POSSIBLE may be different. For
example: Ø
Assumptions
can be taken for granted Ø
Communication
styles differ Ø
Ambiguity
is often present Good
test planning, management and communication are essential in bringing all this
together and eliminating these irregularities. In conclusion, testing must be
pre-considered. The following sub-sections provide a comprehensive background to what software testing is all about and what are good standards to follow: Ø Stages
|
Send mail to Anthony.Cairns@AnthonyCairns.com with
questions or comments about this web site.
|
