Information Technology Reference
In-Depth Information
..1.
Challenges
From the end user's perspective, it does not matter what methodology, tools, and
strategies you are using for testing the software application as long as you achieve
the target of delivering them a software application that is defect-free, has good per-
formance even during peak loads, has good usability features, and works overall as
intended and as per their expectations. They may forgive you for a late delivery but
will never forgive you for delivering an application that fails in any of these goals.
On the other hand, your customer's management will be looking at meeting costs
and time deadlines for the project along with quality.
When testing project execution starts, management and end users may expect
to receive timely and detailed reports so that they have a good understanding of
project progress. The consideration here is that because they do not have access to
what is going on with the project, they want a good report so that they are aware of
the progress on the project.
..1. Conclusion
It is an accepted fact that familiarity ensures better quality during product devel-
opment. In the development of any product, the more time the development team
spends on developing the product, the more mature and better the finished product
is. To cut development time, standardized processes are adopted so that most of the
activities related to the project have known courses of action. Similarly lessons learned
from past projects ensure reduction of chances that any phase or activity of the project
may go in the wrong direction, which may lead to higher costs, project delays, or bad
product quality. In the case of software development, adherence to software engineer-
ing methodologies ensures reduced risks of defects entering in the software product.
On the other hand, introduction of the test team in the project from as early a
stage as possible ensures a better percentage of error detection. The test team gets
familiar with the product features and gets thoroughly familiar with the require-
ments. This ensures that the test team develops more understanding about the
product and requirements. They have more time to make more iterations of testing
with the product, which results in a better-tested product.
