Methods and Tools for Software Quality Management - Assignment Example

Methods and Tools for Software Quality Management: A Literature Review Surname, Name Professor Course Institution Date Outline 1 Introduction 2 Definition of Software Quality Management 3 Methods and Tools for Software Quality Management 3.1 Manual Testing 3.2 Automated Testing 3.3 Verification and Validation Methodology 3.4 Requirements Traceability Matrix (RTM) 3.5 Requirements Verification Matrix 3.6 Software Quality Assurance 4 Software Testing 4.1Unit testing 4.2 Functional testing 4.3 Integration testing 4.4 System testing 4.5 Usability testing 4.6 Software performance testing 4.7 Load testing 4.8 Installation testing 4.9 Regression testing 4.10 User Acceptance Testing 5 Quality Management Tools 5.1 Pareto chart 5.2 Histogram 5.3 Fish Bone 5.4 Flow Chart 5.5 Check points 5.6 Scatter Diagram 5.7 Control Charts 6 Benefits of Methods and tools for Software Quality Management 7 Conclusion 8 References Abstract The world is at the age of a high industrial and technological revolution, as the speed of inventions and production increases rapidly. As the world gets deep into diversity, quality is becoming inevitable. Software development is one of the areas that have undergone tremendous growth and revolutions, as many businesses and individuals turn to using software tools to solve their problems. This paper is a literature review, which discusses the methods and tools for ensuring that quality is achieved in software development. It focuses on the methods and tools that are important, and always followed in the process of quality software development and management. It covers the methods and tools that are used in software quality management, giving practical examples, from a critical perspective. It will focus on ensuring quality software management, and cover all the important processes, which include, the tests that should be done, and the methods and tools for quality software management. This will show the need for both manual and automatic testing, and the use of the seven quality assurance and control methods, while developing quality software. 1. Introduction Technological revolution in the present world is responsible for the rapid growth of software (Schaefer & Spillner, 2011). Quality management is one of the inevitable processes in software development. All software should be developed in a way that they can be able to perform their intended purpose without any problems. This means that they should be created without any errors and faults, so that they can perform their intended functions (Reifer, 2006). The success of a business, however, depends on the quality of the software and the systems used in the management of critical areas of any business (Pettichord & Kaner, 2011). Quality software will always be efficient and productive. It is well designed and developed. This means that powerful quality management systems must be set up to ensure the production of strong software and systems, which will guarantee production. Good quality management systems control the production of software, right from the design. Software development hence needs to involve a series of both manual and automatic tests, as well as verifications, to ensure that all processes are followed to the latter and that the software is being developed according to the required standards (Reifer, 2006). Software engineers always have to employ the use of different methods and tools to ensure that quality software is produced. It is usually necessary, therefore, for software developers to employ the use of all or some of the seven tools of quality management and analysis as they try achieve quality software (Reifer, 2006). Different tests should also be done, which include manual and automatic testing, in an attempt to produce quality software. This means that quality software management is a systematic process that includes all these tests, while using different tools and methods to achieve quality. This essay will give a comprehensive review of quality software management. 2. Definition of Software Quality Management Quality management is a process that incorporates all the activities involved in ensuring that a product meets its requirements, in order to achieve the set goals and objectives (Pettichord & Kaner, 2011). It includes consistent examination of the products’ process of development, starting from the product’s design to the completion of the development. Software quality management, therefore, is a set of all processes involved in ensuring they produce their software with a high quality, which will be able to meet all the expectations of its functioning, and deliver the best results possible. It starts with the choice of the right designers and engineers and continues through the systematic development process, exercising a critical analysis of each stage, in an attempt to identify and eliminate any loopholes that may hinder the success of the software product (Schaefer & Spillner, 2011). This means it looks at all the specified requirements like the performance of the software, usability and supportability, and the ability of the software to perform excellently, even in unforeseen circumstance, and maintain a low rate of defects. It also aims at ensuring the consistency, accuracy, durability and viability of the software. It ensures that the software is not overly complicated and that it can be easily reviewed and modified in the future. Because software works in different environments, quality software management will still be responsible that the software is compatible with many standard applications and that it can also work with other software programs, from other developers, to achieve the desired results in a business. Above all, quality software management considers that poor quality software is the mother to many unforeseen disaster and must be avoided at all costs. 3. Methods and Tools for Software Quality Management 3.1. Manual testing Manual testing is one of the most powerful ways of identifying defects of a software program (Schaefer & Spillner, 2011). Manual testers assume the position of the final, end user of the software, and use the features of the product, just like an end user would do. In the process, they are able to test all sections of the software, to ensure that they are fully functional according to their purpose. They ensure this by observing the behaviors of the software program when given different instructions under varying circumstances. For a complete testing of the software, testers usually follow a written plan in their functioning, which is usually designed to cover all aspects of the software’s operation (Pettichord & Kaner, 2011). All software should undergo this process, to help identify and correct any preliminary defects, before delivering the software to the intended end users. 3.2. Automated Testing Just like manual testing, this is also a significant method of software testing and validation that ensure the correct functioning of the software program. However, this method is relatively cheap and time efficient than manual testing. It is hence used to cut on the cost of real testing. Testers write down a script-guide, which follows the systematic sequence of steps for testing. In most companies, the test runs overnight, and the results are received in the morning, since it does not require manual supervision (Hoskisson, 2011). It becomes cost friendly when the same testing sequence can be re-used, and when the results achieved are easy to interpret. 3.3. Verification and Validation Methodology Verification and validation, V&V, is the process of reviewing software to ensure that it is up to all its specifications and that it delivers the intended results without experiencing any difficulty. It is a vital section of the software development cycle, which ensures that software is appealing, from its design to function ability. It ensures that the software has the ability to solve the exact problem of the end user. It should also solve other modifications arising from the original problem. The methodology involves identifying if the software has any faults, malfunction, or failure. A fault, in V&V, is the absence of a function in the software’s coding, while a failure is the demonstration of a fault, when the software is executed. A malfunction will mean that the software program does not comply with its initial specifications, hence does not perform the specific intended purpose. In most cases, V &V is usually done by a team of independent software engineers who were not part of the team that designed and developed of the program. It involves inspection, analysis, testing and demonstration. The most common technique follows the following steps: Design Verification- This is crucial in establishing that the software has an appropriate design, which does not only comply with the needs of the end user, but also software development rules and regulations. Requirements Verification- This stage is meant to ensure that the software system matches its requirements, which are both functional and non-functional. Code Verification- Code verification is used to ensure that the coding used does not have faults, which may frustrate the efficient operation of the software in the future. Validation of the software- After an extensive verification of the software system, verification is done. Validation is done based on, white box and black box testing, experience technicalities, compliance with the international software requirements for standardization, and error handling techniques. 3.4. Requirements Traceability Matrix (RTM) The process involved in the authentication of the relationship between the requirements of the products’ end user and programs that have been developed to meet those specifications is called requirements traceability (Hoskisson, 2011). Requirements traceability includes analyzing the software specifications; the end user’s desired design, the software coding used, test plans, and other aspects, in the process of developing appropriate software. Requirement traceability matrix, the RTM, is the output of SDLC section of the requirements control. It is, therefore, a detailed document, which covers all the specifications and their traceability in a single face. This may be done using a specification tree or table. A sample specification table is shown below. Where: ReQ.1- Unit test ReQ.2- Installation test ReQ.3- Adaptability test ReQ.4- Consistency test ReQ.5- Usability test ReQ.6- Functional testing Sample Traceability Matrix Requirements ReQ.1 ReQ.2 ReQ.3 ReQ.4 ReQ.5 ReQ.6 Test Cases X Y Z X Y Z Success X Failure Y Test Implicitly Z 1.1 X 1.2 Y 1.3 Z 1.4 1.5.1 1.5.2 This is a straightforward example of the traceability matrix. Using this matrix, the software engineers can be able to determine whether the software is in line with its entire requirement, and establish whether it will be able to solve the problems specified by the end user. 3.5. Requirements Verification Matrix Verification is a crucial stage of software development, just like traceability matrix, in order to achieve the desired quality. It is hence the process of establishing whether the product will correctly execute certain functions. A standard verification matrix will involve testing the software’s components, integration testing, system tests, and acceptance test. This means that the software will be tested in relation to related hardware, as well as the correctness of its functionality. This is necessary to ensure that the software is not only effective, but also meets its requirements and that it will be accepted by the customer. It is hence both a testing and critical review of the software system. 3.6. Software Quality Assurance Quality assurance is the validation and verification of the entire software engineering stages (Burnstein, 2008). It is a planned and systematic collection of activities that confirm the software’s standards, requirements, and development procedures. It is different from testing, which involves a given section of the system. Quality assurance is an extensive supervision and testing program to ensure all the requirements are met. It, therefore, involves all the systematic procedures that are employed at various stages of quality control. Figure: 1. (Thompson, 2006) Quality assurance is concerned with prevention, therefore; it monitors and takes charge of any improvements, in an attempt to ensure to that all the standards and agreed upon methodologies are followed, and identifies and solves all problems. It is the father of all other quality assurance procedures, since it deals with inspection and control of the entire software development process. It is responsible for ensuring that the management and the team of software engineers work together towards producing software that is consistent with all the requirements. 4. Software Testing System testing refers to a set of procedures for executing a system with the aim of establishing errors (Myres, 2005). Software differs from physical process that depends on inputs for the production of outputs. The difference lies in the manner of failure where the physical process may fail at one level and prove easy to manage, software is the direct opposite. A software defect occurs as a result of design errors and is not prone to destruction, unlike manufacturing defects. Software bugs usually appear in software unit because of the complexity involved during the process. Despite the complexity involved, system testing is key in improving the quality and minimizing dangerous bugs (Beizer, 2005). Over 50% of time used in system development is spent on system testing meaning that the testing bit is of foremost importance. 4.1. Unit Testing Unit testing falls in the process of software development where minute testable parts are separately scrutinized for proper procedure. Unit testing is not usually automated as; it happens on a manual basis (Burnstein, 2008). This testing method is a constituent used in Extreme Programming (XP), which is a practical approach of software development. It builds an artifact through continuous testing and revision. It is, however, of importance to note that unit testing encompasses those descriptions that are indispensable in performing the unit in test. This, therefore, leads developers to transform the source code devoid of the functioning effects of other functioning units. Patience of the developers is vital, as the process of unit testing is involving and, takes time. 4.2. Functional Testing Functional testing refers to examining an application against the needs of a business. It is usually done using the specifications brought by the client or the design panel. Functional testing encompasses other testing procedures; unit testing, system testing, regression testing plus interface and usability testing. Software testing defers in that, the application applied should supply what the users need. This software testing enables business organization to serve a lot of customers with excellent efficiency. In a scenario where functional tests are difficult to perform, solutions can be located at Web Services HTML and XML. 4.3. Integration Testing Integration testing in more a combinatory test which includes individual units to test them in a cluster. There is a hierarchy in which these units are arranged from the smallest; unit testing is followed by integration testing, which is closely followed in rank system testing, and finally acceptance testing. Then reason behind the hierarchy is to ensure that an error is quickly detected in the interaction of the integrated units. Devices known as test stubs are used in each level and keep building to the next level as seen. This level of testing helps in avoiding bugs that occur as a result of integration. It means that, through the process of integration, the software life is increased and recycling to develop software becomes possible. Despite many developers delving in integration testing, it is important to note that bugs are known for developing at this stage. Any software developer beginning integration testing must first test all units independently. From then on a test plan can be created before test data and where applicable establish scripts to do the test cases. When integration of the components has been completed, test cases can be conducted. After all the above procedures, available bugs should be fixed , and the code retested. The integration process is then repeated to a point where all components have been integrated properly in integration testing. 4.4. System Testing System testing is more complex than integration testing because, at this stage; the complete system is put to the test. The main reason why this test was started and developed was to ensure that the system falls in line with what it was created for. The process used in the manufacture of an ink pen, for instance; the cap, the body, the tail, the ink cartridge and the ball point get a separate unit test and production. When more than two units are ready, they get assembled for Integration Testing. 4.5. Usability Testing The other software testing is usability testing. It implies how best equipment can be used in concurrence with the purpose for which it has been created for. Usability testing is known for effectively measuring the usability with the system. The reason why this is essential in software testing is, it helps to determine whether the change is necessary in the whole process. The changes are made with consumers in mind; has to be handled by the consumer with masterly ease. The developer always works on presentation of the system to ensure it attracts consumers. Functionality is also incorporated , and it is in such an instance that a vital part could be left out only to be discovered by consumer later. It is at this stage of testing that a developer will know where certain errors usually occur and revise on the real product. 4.6. Software Performance Testing Software performance testing is an evaluation that indicates how well a system meets its requirements of time. Two dimensions can be used to indicate software performance; they deal with responsiveness plus scalability (Badgett & Sandler, 2011). Responsiveness deals with the capability of a system to cover its objectives fully, while scalability refers to a system’s ability to keep on meeting the time objectives as the software function increases. Weyuker and Vokolos (2006) argue the basic problems that projects tale after research are caused by system performance degradation and not the crashing of a system or inaccurate responses by the system. System performance failure may result when there lacks performance estimates or budgets. 4.7. Load Testing When anticipating fabrication load, load test are carried out in the end of performance tests. This test is carried out to ensure that production has occurred within the time frames documented SLAs (Service Level Agreements). This test is basic and calls for substantial investment from companies, so that the action anticipated can be simulated precisely in a trial environment. Important to note here is that the test should be carried out repeatedly and in each case yield the same result. Load test is also vital in determining the least configuration and quantification of a threat. 4.8. Installation Testing Installation testing is also as pivotal in testing activities. The consumer is interacting with the commodity, for the first time, and it is, therefore, vital to ensure that the consumer is not troubled during installation of the software. Trouble arises today because unlike before where software could be distributed physically by the CD format, today software installation can be possible via the internet. A lot of factors the means of distribution and the operating system that one supports will affect the installation process. The process also differs depending on the platforms for instance neat GUI used in windows or clear command line in the case of Unix boxes. 4.9. Regression Testing Regression testing is normally performed to ensure that, altering the software does not have any side-effects that was not intended. This is, however, difficult to accomplish, as there are large test suites because changes come in rapidly. In a bid to make regression testing more efficient, researchers have come up with regression test selection (RTS) , but the problem of incompatible process assumption and unpredictable performance keep draining the whole process. Mismatched process assumption and inappropriate evaluating models also come in as barriers towards regression testing. 4.10. User Acceptability Testing Finally, there is the user acceptance testing (Tripath & Naik, 2010). At this stage, a section of people representing the final users come in to examine the application. This is known to happen in the real world cases. Those who will be using the application put it to test before finally accepting it. This instills confidence to the buyer that the application will meet the requirements they are shopping. This testing bit also ensures that bugs are eliminated. It is worth noting that before carrying out User Acceptance testing, the application should be developed. 5.0. Quality Management Tools 5.1. Pareto Chart A Pareto chart is a quality control tool that can be used to identify the most significant factor among a wide set of variables. By employing the use of this tool, the team of quality control can be able to establish few problems, which have the greatest effect on the operation of the software. This chart is a combination of bars, like that of a histogram, and a line graph. The bars are used to represent individual variables while the line graph is used to show the aggregate total value. Model Pareto Chart Figure: 2. (Pyzdek, 2010) This method may also be used to keep a record of the most common mistakes and defects during software development. The Pareto analysis tool establishes problems with their root causes, hence guiding the quality control team to identify the cause of a malfunction in their software. 5.2. Flow Charts These are pictorial demonstrations, which show a step by step process for developing a product (Blaze, 2010). Figure: 3. (Fryman, 2008) The above simple example of a flow chat gives the reader a picture of what happens before this person gets out of bed. Using this flow chat, the owner will always follow this systematic process and will never miss any step. In the same sense, software developers use flow charts for consistency and standardization. Just by looking at a flow chart, one can be able to determine the steps to follow, at what time, and when to make a certain weighty decision. Like the saying goes, “A picture is worth a thousand words.” Therefore, once a flow chat is created, it becomes easy for the logic of a given process to be understood, and a third party can also understand what is going on without straining. Flow charts in quality management system are used to ensure standardization. Using this tool, software developers can be able to ensure that they follow consistent procedures in designing and developing their software. They are also beneficial in ensuring that no important step of the software development is skipped. 5.3. Histograms Histograms are quality management tools used for summarizing data and displaying data variation graphically. Using a histogram, the user can be able to interpret a given set of data and derive the most common variables and the relationship that exists between different data variables (Clarke, 2007). They also help to break data into small sections, for determining the frequencies of different events (Blaze, 2010). Just like the Pareto chart, this tool can be used to identify the most common mistake, errors, and faults that occur during software development process. They can also be used to identify the most acceptable software designs, according to their frequencies, in the process of ensuring the quality system management. 5.4. Scatter Diagrams Scatter diagrams are used to show the interrelationship between two different variables. They are scattered diagrams, each representing a certain value, which can be used for interpreting the data. They are used for variables that are under the control of an experiment. In software engineering, where there are many variables, scatter diagrams can be used to determine the relationships between different points, hence when there is a default, the developers can easily identify the cause, due to these relationships. This means that they are indispensable in identifying the cause of a problem, hence ensuring the desired quality is achieved. They can also be used to determine the severity of a fault, since they usually show the degree of the effect caused by the relationship between different variables. 5.5. Fish Bone The fish borne diagram is pivotal in identifying the cause of a fault and its effect. It shows a problem and all the factors that can lead to the occurrence of the problem. Below is a sample fish bone. Figure: 4. (Rhyn, 2007) This tool can be used by engineers to check the quality of a product by testing to ensure that all the problems listed on the fish bone have been corrected. They can also be used find the possible solution to a defect easily. 5.6. Control Points These are graphs that are used to study the behavior of different processes over time. Data is usually arranged according to time, based on a collection of average historic findings. Hence, when developing a software program, developers can always identify the stages that have been recorded to give engineers a lot of problems, hence exercise due care. They can also be able to identify the mist common problems at different stages, and react appropriately in case of a defect. 5.7. Check Points Check Points, or tally charts can be used to record information for repeatedly done experiments. This can help the team of quality assurance mangers to determine the most crucial stages in the development of different software, and hence conduct the necessary checks to ensure the viability of each stage of development. 6. Benefits of Methods and Tools for Software Quality Management Software engineering is a critical process that involves the design and development of appropriate programs (Tripath & Naik, 2010). It is a complex process that involves multiple series of steps, before the final product is delivered. The right software product is one that conforms to all the end user’s requirements and can deliver the desired results, without experiencing technical problems. To achieve these results, there is a strong need for a system of analysis and evaluation that will ensure the right product is achieved. However, due to the complexity of the project, a single step is not sufficed to develop a superior product. These methods and tools, therefore, used to ensure the viability of the program through a series of tests, aimed at identifying and solving any problems (Clarke, 2007). Because the software may be used different end users to solve a diversity of human needs, a critical and deep analysis is essential to ensure that the software will be able to solve both intended and any unforeseen problems that may arise in the future use of the software. Arguably, these methods and tools are also significant in ensuring that the software meets the right quality and aligns with all the functional and non-functional software development policies, including international standards. They also ensure portability of the software. Elimination of errors, failures and software is also a responsibility of these methods and tools. There are some errors which may not be easily noticed, unless exhaustive scrutiny is done. For example, it may be difficult to realize a straightforward syntax error of, “1, 8”, which was supposed to be, “1.8.” With effective use of these methods and tools, however, they can be identified and corrected. Many small and large businesses across the globe now use software to handle their data and daily operations (Tripath & Naik, 2010). It is hence vital that they get the correct software products which can help to solve their problems. It is remarkably true that using faulty or wrong software may have a cost of zero to a billion dollars. Software engineers are exceptionally careful to develop products that are neither faulty, nor wrong. They have to make sure that their software solve the specific intended problem, and by so doing, they may save businesses from incurring losses due to use of the wrong software products. Therefore, the use of these quality management methods and tool becomes handy. 7. Conclusion It is evident from this paper that quality management of software systems is a crucial process towards ensuring the correct functionality of the final software. All the processes, tools and method discussed in this essay have proved to be of equal importance in software development, in order to ensure that the desired quality is achieved. Flow charts, pareto diagrams, histograms are all crucial, this means that while striving to achieve quality, software developers must ensure they use these tools. This will not ensure that software works properly, but will also lead to consistency with other software and international standards, which will mean quality. Tests must also be used to compliment the use of these tools, so that we can achieve quality (O’regon, 2011). Quality software management is, therefore, vital in the process of delivering high end software. It is especially pertinent in the competitive world of today, where there is no chance to make a mistake. A simple error by software developers may make them lose their customer; hence, keen attention must be observed to ensure that error free software that serves its intended purpose is produced. References Blaze, M. 2010. Insights to Performance Excellence 2009-2010: An Inside Look at the 2009 -2010, Baldrige Award. New York: ASQ Quality Press. Burnstein, I. 2008.Practical Software Testing: A Process-Oriented Approach. Chicago: Springer Publishers. Clarke, T. 2007. European Corporate Governance Systems; Reading and Perspectives. New Delhi: Taylor & Francis. Fryman, 2008. Sample Flow Chart. Mathematics Society of Arabia viewed 18 May 2012. Hoskisson, R. et. al. 2011. Strategic Management: Competitiveness and Globalization: Cases. Hong Kong: John Wiley and Sons Publishers. Jung-Min, K., Adam, P., & Gregg, R. 2005. An Empirical Study of Regression Test Application Frequency. The Journal of Software Testing, Verification & Reliability. Volume 15, Issue4, pp. 257-279 O’ regon, G. 2011. Introduction to Software System Improvement. London: Springer Publishers. Pyzdek, R. 2010. Model Pareto Chart, E-draw Organization, viewed 17 May 2012. Pettichord, B., & Kaner, C. 2011. Lessons Learned in Software Testing: A Context-Driven Approach. New York: John Wiley & Sons Publishers. Reifer, D.2006. Software Management. New Jersey: John Wiley & Sons. Sandler, C.,& Badgett, T. 2011. The Art of Software Testing. New York: John Wiley and Sons Schaefer, H., & Spillner, A. 2011. Software Testing Foundations: A Study Guide for the Certified Tester Exam. California: O'Reilly Media, Inc. Schermerhorn, J. 2009. Management: Management: Leading and Collaborating in the Competitive World. New York: John Wiley & Sons. Thompson, R. 2008. Q.A Diagram. Soft Prodigy Diagrams, viewed 17 May 2012. Tripath, P., & Naik, S. 2010. Software Testing and Quality Assurance: Theory and Practice. New York: John Wiley & Sons. Wartkin,J., & Mills, S. 2010. Testing It: An Off-the- Shelf Software Testing Process. New York: Cambridge University Press. Weyuker, J., & Vokolos, F. 2006. Perfomance Testing of Sofware Systems. New York: Sage Publishers. Read More