Abstract

Research and study of Software Quality has Traditionally Focused on the Overall Product Quality Rather than on the sub-phase’s milestones. There are many attempts over software testing as a standalone development phase which introduced in the literature; these efforts lacked the dynamic nature which has a diverse effect on the maintenance phase. This study will present the current software testing models; their challenges and at the end it will present our new dynamic model for applying quality assurance requirements over the sub-phases of the testing model. Quality properties may include as performance, efficiency, reliability, etc., new model will present for Improving the effectiveness and efficiency of the testing process through applying the quality requirements, designing high quality products, producing software with high Cost optimization, satisfying the product stakeholders.

Keywords:

Dynamic model, software development life cycle, software quality, software testing, software verification and validation,

References

1. Aggarwal, K.K. and S. Yogesh, 2005. Software Engineering. 2nd Edn., New Age International.
   
2. Aranda, J., S. Easterbrook and G. Wilson, 2007. Requirements in the wild: How small companies do it. Proceeding of the 15th IEEE International Requirements Engineering Conference (RE 2007).
   CrossRef    
3. Chandrasehakhar, K., 2005. Software Engineering and Quality Assurance. BPB.
   
4. Dan, P. and M. Russ, 2008. Head First Software Development. 1st Edn., O'Reilly, Sebastopol, CA.
   
5. David, J. and S. Hossein, 2005. Test-driven development: Concepts, taxonomy and future directions. IEEE Software, 38(9): 43-50.
   
6. Gottesdiener, E., 2005. The Software Requirements Memory Jogger: A Pocket Guide to Help Software and Business Teams Develop and Manage Requirements. GOAL/QPC, Salem, NH.
   
7. James, A.W., 2009. Exploratory Software Testing: Tips, Tricks, Tours and Techniques to Guide Test Design. Addison Wesley, ISBN-10: 0321636414; ISBN-13: 978-0321636416.
   
8. Karl, E.W., 2006. More About Software Requirements: Thorny Issues and Practical Advice . Microsoft Press, Redmond, WA.
   
9. Lewis, W., 2008. Software Testing and Continuous Quality Improvement. Auerbach, Boca Raton, FL.
   CrossRef    
10. Pekka, A., B. Nathan, M. Tiziana and M. Richard, 2007. Software process improvement. Proceeding of the Software Process Model 14th European Conference (EuroSPI 2007). Potsdam, Germany, September 26-28, 2007.
    PMCid:PMC3091376    
11. Pine, F.J., F. García and M. Piattini, 2008. Software process improvement in small and medium software enterprisesa systematic review. Softw. Qual. Control, 16(2): 237-261.
    CrossRef    
12. Pressman, R.S., 2005. Software Engineering: A Practitioner's Approach. McGraw-Hill, New York.
    
13. Pressman, R.S. and D. Ince, 2007. Software Engineering-a Practitioner's Approach. McGraw-Hill.
    PMCid:PMC1978391    
14. Roger, S.P., 2005. Software Engineering: A Practioner's Approach. 6th Edn., (International Edn.), McGraw-Hill, NY.
    
15. Schulmeyer, G.G., 2007. Handbook of Software Quality Assurance. 4th Edn., Artech House, Boston.
    
16. Software Engineering Institute, 2008. The Ideal Model. (Accessed on: October 10, 2008).
    Direct Link
17. Thayer, R.H. and M.J. Christiansen, 2005. Software Engineering. Volume 1: The Development Process. 3rd Edn., Wiley and Sons, NY.
    
18. Timothy, C.L. and L. Robert, 2005. Object-Oriented Software Engineering: Practical Software Development using UML and Java. 2nd Edn., McGraw-Hill, NY.
    
19. Weinberg, G.M., 2008. Perfect Software: And Other Illusions about Testing. Dorset House Publishing, New York.
    

Competing interests

The authors have no competing interests.

Open Access Policy

This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.

Copyright

The authors have no competing interests.