Extensive Hands On Experience
C/J SYSTEM SOLUTIONS, INC.
Consulting and Training for Computer
Professionals
SYSTEM TESTING AND QUALITY ASSURANCE
*
Meeting client’s needs is the most important part of any project
*
Learn how to make the most of the testing process
*
Identify what needs to be tested prior to development start
*
Involve all team members in the project plan to ensure success
*
Reduce maintenance by doing it right the first time
*
Prioritize and schedule testing in accordance with client’s needs
*
Measure to mange throughout the process
*
Benefit from “lessons learned” during the project not just after
*
Introduce traceability to reduce regression testing time
*
Design and implement a traceability matrix
*
Collect metrics continuously to “Measure To Manage”
Good software does not just happen. It
requires a documented and repeatable process. Beginning with identifying
customer's needs (not wants as they want everything), understanding impact on
other existing products, allocating resources of personnel and budget, design
and development, white and black box testing, documenting process so it is
repeatable and traceable, on through systems and acceptance testing, are all
intimately integrated. Yet many companies fail to communicate within their own
department, much less with others. Over 90% of developers have never used their
products as customers, yet they are expected to know how the customer will
implement their software in the customer's environment.
Quality Assurance is tasked with the
responsibility to identify and manage processes during the entire product life
cycle and to ensure the product meets the customer's needs. Most of the money
spent on a product during its life cycle will be in maintenance, not on
development. (Look at the cost of Y2K) A product will be used for many years
after the first development cycle. What will the cost and how difficult will it
be to maintain a "working" product? Don't assume that the person
originally responsible to design and develop is going to remember months or
years later how they "did it." After the project team is disbanded
and the staff goes on to do additional duties, who is going to remember how,
what, why, or when? The farther into the development process defects are
uncovered, the costlier it will be to fix them. It makes much more sense to
spend the resources to prevent as opposed to cure. Quality Assurance ensures
standard processes are in place and traceability is available. The major cost
of removing "bugs" in the system is not in repair, but instead, in
finding them.
The Quality Assurance seminar is
designed to provide your staff with the knowledge and skills necessary to
produce a "quality product" from the beginning. It is not the amount of testing that is
done but the amount of “quality testing” that matters. The System Testing and Quality Assurance
workshop helps the participants design a system that can be easily developed
and maintained be implementing proven processes. Subjects to be covered include
but are not limited to - -
|
* Needs analysis |
* Problem tracking |
* Product status |
Who should attend? Business
Analysts, Developers, Programmers, Project Management, Quality Assurance,
Customer Support, Testers, Quality Control, stake holding users, and anyone
else responsible for ensuring the design, development, testing, delivery, and
support of any projects.
|
| Designing and Implementing Testable Requirements | consulting | copyright |