SWRT:
Testing
Test Charter
To have a well defined and documented
test process; one that is repeatable and
implement.
To define a test vocabulary and glossary
of terms to be published and used Institute
wide.
To implement and enforce a review technique
of all products that will mitigate risks
and allow team success by:
- detecting defects/bugs as soon as possible;
- reducing rework and costs to repair;
- improving overall customer satisfaction.
This will be accomplished by conducting
three review types:
In Process Review
A technical review of the product with
focus on bug or defect detection
Decision Point Reviews
A review of controlling risks
Post Implementation Reviews
(30 day reviews)
A review of success in the overall development/release
process and allows opportunities for process
improvement.
Quality
Assurance/Quality Control
Quality Assurance is
a focus on processes:
- defining
- deploying
- continuous improving
...with the goal of defect prevention.
Quality Control is a
focus on products:
...with the goal of defect detection
What does Quality mean at MIT?
A product or service that meets
or exceeds requirements and standards and
delivers customer expectations free from
defects.
What are attributes of Quality?
- Capability: can it perform
the requested functions and features.
- Reliability: will it work
and resist failure (work next week/month/year).
- Usability: how easy it is
for the customer to use the product.
- Performance: is it responsive
and timely.
- Testability: how effectively
can the product be tested.
- Portability: can it be ported
with ease.
What are the costs of Quality?
- Failure: the cost to identify,
analyze, correct and retest defects/bugs.
- Appraisal: the cost to test
software and conduct reviews.
- Preventative: training and
process improving.
Software
Testing
What is software testing?
Testing that involves the operation of
an application under controlled conditions
and evaluating the results.
Why do we need to test software?
- To prove the program is no good; break
it.
- To detect errors and deviations from
requirements.
Why does software have bugs?
- miscommunication or no communication
as to the specifics of what an application
should or should not do (requirements)
- software complexity with inexperienced
users
- programming errors
- changing requirements
- time pressures; schedules
What is a risk?
The probability that an unfavorable event
will occur that results in loss.
What are some examples of risks
to software testing?
- incomplete or changing requirements
- developers exceed their schedule estimates
- management commitment and support
- time to do the job right
- application size
- application complexity
- business urgency
- introduction of third party software
- introduction to new technology
- lack of customer involvement
|
