The paper "Software Quality Assurance in Scenario of Project Management" is an outstanding example of a management report. Software quality testing is an analysis of software quality that is carried out in an attempt to decide if the quality of the software development is according to the requirements of the project sponsor, project stakeholders, and several other authoritarian bodies. It as well facilitates in setting-up the software’ s reliability and promotes a perceptive of the fundamental risks, if there is any when it is applied. In more simple words, software quality testing is a procedure of confirming that a software system or application is quality assured and performs all its functions efficiently whilst offering the company requirements documentation approved before.
Additionally, software quality testing could be performed at a variety of levels and several times through the software development lifecycle process. Though, the most excellent time to perform it is following the software development requirements that have been identified as well as on the achievement of the coding procedure. On the other hand, the main reason for carrying out software quality testing is to identify and correct software breakdowns that might or else have gone unnoticed.
In addition, the system testing is performed in dissimilar environments and by running using diverse scenarios with the objective to make sure that a system does what it is meant to perform at the best possible capability (My-Project-Management-Expert, 2009; Schulmeyer & Mcmanus, 1998). This literature review covers various aspects of software quality assurance in the scenario of project management. In this scenario, this research will assess and analyze some of the important aspects of project management and their relation and possible influence on software quality management.
In addition, this research will assess the basic practice of software quality assurance and the role of enhanced and effective project management at this paradigm. SOFTWARE QUALITY MANAGEMENT BASIC IDEA The delivery of quality software is going toward the new era. Though, for many years CIOs (chief information officers) have pointed to that one of their main precedences is lining up IT with business aims and objectives. In this scenario, the stress faced by the managers to renovate, grow, and change with market requirements requires companies to put attention to this main concern.
According to IBM software quality research and a survey carried out in 2006, 65% of the global business chief executive officers (CEOs) stated that they develop policy and plan to fundamentally change their businesses in the next two years in reaction to forces from competitive as well as market services.
Bogue, R.L., 2005. The top 4 things project managers do to reduce software quality. [Online] Available at: http://www.techrepublic.com/article/the-top-4-things-project-managers-do-to-reduce-software-quality/5991800 [Accessed 27 September 2011].
Borland Software Corporation, 2006. Software Quality Management. [Online] Available at: http://www.borland.com/resources/en/pdf/white_papers/software_quality_management.pdf [Accessed 28 September 2011].
Exforsys Inc., 2008. Software Quality Management. [Online] Available at: http://www.exforsys.com/tutorials/testing/software-quality-management.html [Accessed 26 September 2011].
Green, B., 2000. Building Better Software. [Online] Available at: http://www.robelle.com/library/papers/better/ [Accessed 26 September 2011].
IBM - Rational Software, 2011. Software Quality Management from IBM. [Online] Available at: http://www.bizforum.org/whitepapers/ibm-8.htm [Accessed 19 September 2011].
MetricStream Inc., 2011. What is Your Company's Cost of Poor Quality (CoPQ) - Tools for calculating and reducing it. [Online] Available at: http://www.metricstream.com/insights/costofPoorQuality_home.htm [Accessed 26 September 2011].
My-Project-Management-Expert, 2009. Software Quality Testing. [Online] Available at: http://www.my-project-management-expert.com/software-quality-testing.html [Accessed 28 September 2011].
Nandi, S., 2011. Phases of Software Quality Management. [Online] Available at: http://www.softwaretestingclub.com/profiles/blogs/phases-of-software-quality [Accessed 19 September 2011].
Petrasch, R., 1999. The Definition of ‚Software Quality’: A Practical Approach. [Online] Available at: http://www.chillarege.com/fastabstracts/issre99/99124.pdf [Accessed 28 September 2011].
Pressman, R.S., 2001. Software Engineering: A Practicioner's Approach, 5th Edition. London: McGraw Hill.
PTC, 2011. Quality Lifecycle Management. [Online] Available at: http://www.ptc.com/WCMS/files/118110/en/6530_Quality_Lifecycle_Management_TS_EN.pdf [Accessed 26 September 2011].
Schulmeyer, G.G. & Mcmanus, J.I., 1998. Handbook of Software Quality Assurance. 3rd ed. London: Prentice Hall PTR.
Seapine, 2011. Identifying the Cost of Poor Quality. [Online] Available at: http://downloads.seapine.com/pub/papers/CostPoorQuality.pdf [Accessed 27 September 2011].
SoftwareQualityAssuranceBlog, 2011. What makes someone good at software quality testing – Good tester characteristics. [Online] Available at: http://softwarequalityassuranceblog.com/ [Accessed 29 September 2011].
Sommerville, I., 2004. Software Engineering, 7th Edition. New York: Pearson Education (Addison Wesley).
Soni, A., 2010. The Organizational Impact of Poor Software Quality. [Online] Available at: http://saasinterrupted.com/2010/02/01/the-organizational-impact-of-poor-software-quality/ [Accessed 26 September 2011].