Remember that all models are wrong; the practical question is how wrong do they have to be to not be useful.
The most that can be expected from any model is that it can supply a useful approximation to reality: All models are wrong; some models are useful
With that well known disclaimer, here's presenting a hopefully useful model for addressing your software development project's quality assurance needs.
It starts at the root Test and Quality Assurance Documentation entity which is an aggregation of the following 3 top level header entities of
- Planning - Test Strategy and Test Management Plan
- Doing - Test Cases
- Reporting - Test Reports
The main goal of the model is to help kick start the thought process for a software project's new quality assurance development via software testing. The model identifies many entities in the software testing domain and draws relationships between them.
This approximate model could perhaps be further extended for your specific project's needs for quality assurance and software testing.
Your inputs are welcome!
Feel there are more core basic entities that can be added to this model?
Any extension entities or new relationships between entities?
Please, write in the comments section below.
 |
| A Model for Quality Assurance via Software Testing |
