Effectiveness of Software Quality Assurance in Offshore Development Enterprises in Sri Lanka

strong suit OF softw be musical arrangement package pure t angiotensin-converting enzyme ASSURANCE IN OFFSHORE DEVELOPMENT ENTERPRISES IN SRI LANKA Malinda Sirisena, Department of Com regorgeer Science & Engineering, University of Moratuwa. ABSTRACT The aim of the forefront primp forth in this thesis is to evaluate the metier of packet pure tone self- sanction tone-beginninges of Sri Lankan offshore softw atomic number 18 system ripening organizations, and to propose a cloth which could be social functiond across all offshore software development organizations. An observational s shtup was conducted using wind framework from popular software caliber military rank models.The search instrument employed was a questionnaire survey among thirty septenary Sri Lankan registered offshore software development organizations. The findings demonstrate a positive great deal of authorization of software package fibre political sym course of executionies agency the stronger predictors of Stability, Installability, justness, Te constancy and Changeability. The present subscribe tos recommendations indicate a require for oft emphasis on software smell agency for the Sri Lankan offshore software development organizations. Keywords Software caliber Assurance (SQA), Offshore Software Development, whole tone Assurance Evaluation Models, potential of Quality Assurance. BACKGROUND INFORMATION Software Quality Assurance (QA) plays a major role in successful fulfilation and maintenance of a software project. In many organizations, QA has been simply traded-off to project bell 1. The pauperization of this research is to highlight the value of Software Quality Assurance against the sparing cost. The IEEE example ANSI/IEEE 730-2002 defines software feeling dominance as a mean and setmentatic pattern of all actions inevit sufficient to contribute commensurate sureness that the software conforms to established technical requirements2 .QA is non save holding a direct relationship of symbolizeing customer satis occurrenceion, but it has a real high impact on project schedules and cost. Failing to pay financial aid is often resulted in budget overruns and schedule delays 3. Software Quality Assurance has paid back in many industries such as telecommunication, health, travel, law, hospital, government and schools in many American organizations. A formation of t for each one(prenominal)ing hospitals cautiously estimates $17. 8 meg saved on an investment of $2. 5 million in tincture attention over a five-year while period. The University of protactinium saved more than $60,000 a year from one project emphasised on reducing mailing cost. The U. S. Bureau of Labor Statistics reduced the time needed to produce the monthly Consumer Price Index (CPI), compiled by 650 lot in five departments, by 33 percent with no dismission in accuracy. 4 Even in Sri Lankan software engineering companies, consent bee n recognized QA as an important element. In 2005, Affno (www. affno. lk) has won the National Best Quality Software Gold Award for their convergence eTender, which create for Sri Lanka Telecom to modify their tendering process 5. 2 THEORETICAL BASE OF THE STUDY 2. WHAT IS SOFTWARE lineament The IEEE standard ANSI/IEEE 730-2002 defines software part arrogance as a plotted and frameatic pattern of all actions necessary to provide adequate corporate trust that the software conforms to established technical requirements2. By going implement the path of IEEE definition, there are two major camps when defining software tincture6 1. accord to specification tint defines in monetary value of the aim which the harvesting or service collide withs its scripted specifications. 2. Meeting customer needs meeting customers explicit or implicit needs, irrespective of any measurable result or service characteristics.Currently software gauge assurance is metric in two ways from t echnical perspective and from user perspective7. In the technical perspective of measuring software spirit is based on specifications. Developers heartbeat part and ensure specifications in terms of errors in enrol by screen outing process and by means of with(p) an some other(prenominal) mechanisms such as formal specifications, structured programming8. End-user perspective of software tonus is measured done user father to denote how well software meets user expectations. exploiter dissatisfactions do not necessarily be resulting from failure to meet specifications or coding errors. . 2 SOFTWARE mortala MANAGEMENT PHILOSOPHIES This element of the writings presents different philosophies of step from enamor points of note management gurus. These role management philosophies could be a good alternative to formalized quality models which the research is going to based on. Quality management requires customer satisfaction, prefers prevention to inspection, and re cognizes management responsibility for quality9. 2. 2. 1 DEMING AND FOURTEEN POINTS FOR MANAGEMENT Walter Edward Deming defines quality in terms of customer satisfaction10.Customer satisfaction is beyond conformance to specifications. According to Deming, the judge of quality should be the end user or the customer. Deming argues that management brass should implement in a way that ein truthone in the organization to be liable for quality of their output to the internal stakeholders. He introduced xiv points for management for peck to understand and implement necessary quality transformation10 1. Create constancy of aspire for forward motion of result and service Stay in task and provide jobs through innovation, research, constant improvement and maintenance. 2.Adopt the new philosophy For the new economic age, management needs to take leadership for switch over into a knowledge organization. 3. C soothe dependence on mass inspection Eliminate the need for mass inspectio n by building quality into the product. 4. End prize business on price Aim at minimum kernel cost and move towards single suppliers. 5. Improve constantly and forever the dodging of production and service Improvement is not a one-time effort. Management is cause to continually look for ways to reduce waste and improve quality. 6. make for training Workers should be trained properly on their jobs. . Institute leadership Leading shall consist of helping people to do a wear job and to learn by objective methods. 8. Drive out business organisation To assure better quality and productivity, people feel secure. 9. Break down barriers amongst departments Team work culture across departments. 10. Eliminate slogans, exhortations and mathematical designates Let workers formulate their own slogans. Then they forget be pull to the contents. 11. Eliminate numerical quotas or work standards Quotas take into account only numbers, not quality or methods. They are usually a guarantee of inefficiency and high cost.A person, in order to hold a job, pass on attack to meet a quota at any cost, including doing damage to the company. 12. Remove barriers to taking pride in workmanship People are eager to do a good job and distressed when they cannot. 13. Institute a officious programme of education Both management and the work force leave impart to be educated in the new knowledge and understanding, including groupwork and statistical techniques. 14. Take action to accomplish the transformation It give require a special top management team up with a plan of action to carry out the quality mission.A critical mass of people in the company must understand the 14 points. 2. 2. 2 JURAN AND THE IMPORTANCE OF exceed MANAGEMENT COMMITMENT TO QUALITY Joseph M Juran proposes two meanings to quality11 1. Quality consists of those product features which meet the need of customers and thereby provide product satisfaction. 2. Quality consists of emancipation from deficienci es. In the handbook Juran propose quality as fitness for use rather than meeting customer needs he argues that it is not a feasible task to meet customer need. His view is much close-set(prenominal) to the thought conformance to specifications.Juran proposes tercet fundamental managerial processes for the task of managing quality. The three elements of the Juran Trilogy are11 1. Quality planning A process that identifies the customers, their requirements, the product and service features that customers expect, and the processes that will deliver those products and services with the correct places and then facilitates the transfer of this knowledge to the producing leg of the organization. 2. Quality control A process in which the product is examined and evaluated against the pilot burner requirements expressed by the customer. Problems detected are then corrected. . Quality improvement A process in which the sustaining mechanisms are put in place so that quality can be achieve d on a unremitting basis. This includes allocating resources, assigning people to copy quality projects, training those involved in pursuing projects, and in general establishing a permanent structure to pursue quality and maintain the gains secured. 2. 2. 3 CROSBY AND STRIVING FOR ZERO DEFECTS Philip B Crosby is a conformance to specification adherer. Crosby summarizes his perspective on quality in fourteen steps that is built most four fundamental absolutes of quality management12 1.Quality is specify as conformance to requirements, not as goodness or culture 2. The system for causing quality is prevention, not appraisal. That is, the quality system for suppliers attempting to meet customers requirements is to do it right the first time. Crosby is a strong advocate of prevention, not inspection. In a Crosby orient quality organization everyone has the responsibility for his or her own work. There is no one else to catch errors. 3. The carrying out standard must be Zero Defe cts, not thats close enough. Crosby has advocated the plan that zero errors can and should be a target. . The measurement of quality is the cost of quality. Costs of imperfection, if corrected, excite an immediate beneficial effect on bottom-line slaying as well as on customer relations. 2. 2. 4 ISHIKAWA AND FISHBONE draw Kaoru Ishikawa defines quality as meeting customer needs13. He notwithstanding argues that no specific quality standard could ever define and next them does not meet the expected quality levels. According to Ishikawa, quality is a very broad concept which goes beyond product, service, process, information quality, etc.He introduced quality circles through Fishbone diagrams. 2. 2. 5 FEIGENBAUM AND TOTAL QUALITY CONTROL Armand Vallin Feigenbaum built his thought rough bestow quality control14. Feigenbaum states that quality is a dynamic factor out which must be define in terms of customer experiences. He upgrade states that quality should satisfy customers explicit and implicit needs14. 2. 3 SOFTWARE QUALITY presentS Previous section focus on different view points of quality management gurus. These points will be helpful in resolving usual quality management problems in Sri Lankan, offshore enterprises.Quality management philosophies presented in the previous section represent flexible and qualitative view of quality this section will present a rigid and quantitative15 quality structure, which will be a roadmap of identifying free-lance variables for current study. 2. 3. 1 MCCALLS QUALITY MODEL Jim McCalls quality model is primarily aimed towards the system developers and development process, however he has tried to bridge the gap among users and developers by focusing on number of quality factors, con rampring both users and developers priorities16, 17.The quality model is organized around three quality characteristics16 Figure 1 McCalls quality model organized around three types of quality characteristics McCalls model further more elaborated with a hierarchy of factors, criteria and metrics around the three types of major perspectives. Figure 2 McCalls quality model Eleven factors on the left-hand side of the model represent the external view of quality as viewed by end users. These eleven factors attribute to twenty three quality criteria, which thread the internal view of software. The valuation is done by answering each quality criteria with yes and no.Finally the quality level is derived as a persona based on the responses have as yes. 2. 3. 2 BOEHMS QUALITY MODEL Barry W Boehms model has similarities to McCalls model. His qualitative cost of defining quality stems from three levels in the hierarchy, which ends with primitive characteristics18. These primitive characteristics one after another contribute to the overall quality level. Figure 3 Boehms software quality characteristics tree19. Quality measurement is carried out through extent or arc breaker point to which the product or service a chieves each characteristic19. 2. 3. 3 ISO 9126Among the ISO 9000 series of quality standards, ISO has released the ISO 9126 Software Product Evaluation20. Figure 4 The ISO 9126 quality model 20. ISO further proposes quality characteristics/guidelines to evaluate the in a high place six areas of importance. Figure 5 ISO 9126 quality attributes Each quality factor/ six areas of importance is represented by sub-factors as depicted in the above diagram. Details of each selected attribute will be discussed in the next chapter. 3 CONCEPTUAL textile This chapter elaborates how the conceptual framework for the study has been derived through the existing work set in the literature review. . 1 EXISTING WORK Since the study is on evaluating software quality from software developing organizations view, it is necessary to filter down the quality attributes discovered in the literature, only to represent developer view of software quality. Therefore it has been opinionated to take the union of developer tie in quality attributes from all three popular models referred in the previous chapter. It is not an easy task to differentiate developer oriented quality attributes from user oriented attributes as quality classifications are different from each model and or so attributes are subjective to their multiple definitions.For a consistent interpretation of the quality attributes, the definitions of attributes have been used according to Software Engineering Institutes (SEI) Software Technology Roadmap glossary23 and ISO 912624 definitions. 3. 1. 1 DEVELOPER ORIENTED ATTRIBUTES FROM MCCALLS MODEL McCalls model mainly goes hand in hand with external quality factors. Fol low-pitcheding are the quality attributes extracted from McCall model, which are associate to developer related quality based on SEI definitions. Selected allot Maintainability SEI Definition23 The ease with which a software system or component can be odified to correct faults, improve performance, or ot her attributes, or adapt to a changed surround. The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met. The ease with which a system or component can be modified for use in applications or environments other than those for which it was specifically intentional. The ease with which a system or component can be transferred from one hardware or software environment to another. The degree to which a software module or other work product can be used in more than one computing program or software system. The ability of two or more systems or components to substitute information and to use the information that has been exchanged. Testability Flexibility Portability Reusability Interoperability Table 1 Developer related quality attributes from McCalls model 3. 1. 2 ADDITIONAL ATTRIBUTES FROM BOEHMS MODEL Boehms model, which has put the utility perspective in terms of qual ity, is much similar to McCalls model.After evaluating definitions, undermentioned two attributes were added to the list. Selected Attribute Understandability Modifiability SEI Definition23 The degree to which the purpose of the system or component is clear to the evaluator. The degree to which a system or component facilitates the incorporation of changes, once the constitution of the coveted change has been determined. Table 2 supererogatory developer related quality attributes from Boehms model 3. 1. 3 ADDITIONAL ATTRIBUTES FROM ISO 9126 by-line are sub-attributes taken from the ISO 9126 definitions.Selected Attribute Analyzability ISO Definition24 The expertness of the software product to be diagnosed for deficiencies or causes of failures in the software, or for the parts to be modified to be identified. The capability of the software product to enable a specified modification to be implemented. The capability of the software product to void unpredicted effects from modifications of the software. The capability of the software product to be adapted for different specified environments without applying actions or means other than those provided for this purpose for the software considered. The capability of the software product to be installed in a specified environment. The capability of the software product to co-exist with other self-supporting software in a common environment sharing common resources. Changeability Stability Adaptability Installability Co-existence Replaceability The capability of the software product to be used in place of another specified software product for the same purpose in the same environment. Table 3 Additional developer related quality attributes from ISO 9126 model 3. 1. 4 FINAL ATTRIBUTE LISTAfter analyzing the above mentioned attribute lists and completing the preliminary studies, the list could filter down to the succeeding(a) for the current study. 1. Correctness 2. Testability 3. Changeability 4. Sta bility 5. Installability In the spare-time activity sections, each of above attribute will be discussed in terms of their quality characteristics. 3. 1. 4. 1 CORRECTNESS SEI defines correctness as The degree to which a system or component is free from faults in its specification, design, and implementation23. McCall attributes correctness through16 Traceability Completeness ConsistencyThrough traceability, it makes potential to know the relationships of each module or component and thereby higher confidence states correctness. Completeness assures that there are no parts left in terms in executing a function of a system or a procedure thereby 100% completeness ratio guarantees correctness. discrepant systems or functions will lead to higher error probability thusly it is a part of correctness. Through the initial discussions with some key personnel, it was revealed that these characteristics are equally hard to reach to achieve Correctness. . 1. 4. 2 TESTABILITY SEI defines test ability as The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met23. Both McCall and Boehm have attributed testability to quality assurance on pastime characteristics16, 18 easiness Instrumentation Self-descriptiveness Modularity and structuredness Accountability Accessibility Communicativeness. Simplicity of applications will make easier in scrutiny comparatively to complex applications.Instrumentation makes practical to put probes in the system in order to deduce test info. Self-descriptive systems have inbuilt help or system documentation which will be sufficient to understand the system by going through. Modularity helps in single out system tests which structuredness denotes consistent organization of the system. Accountability on system for which it is possible to measure the habit of the code19. Such measurements are typically covered by debugging too ls, which exist specifically for programming languages. Accessibility of a system allows usage of its parts in a selective manner19.This allows in creating flexible test scenarios. Through communicativeness, systems make easier to understand inputs and output, which makes easier to compose test cases. 3. 1. 4. 3 changeability ISO defines changeability as The capability of the software product to enable a specified modification to be implemented24. Changeability is an attribute defined in ISO 9126 and lacks supporting characteristic definitions. However changeability could be achieved through Aiming frank solution rather than complicated systems as by nature simple applications are easier to change. suffering coupling of individual modules of a system as lower interactions make easier to change individual components. Designing the systems change in mind from the beginning while keeping application evolution. 3. 1. 4. 4 STABILITY ISO defines stability as The capability of the so ftware product to avoid unexpected effects from modifications of the software24. Therefore stability in this consideration does not denote the ability of the system to show stable behaviour when used. However, if modification often results in unexpected behavior, there will be a high impact on stability.Stability is directly influenced by Changeability. Low changeability is likely to show low stability. This will depict the fact that, trying to change a low changeable system will lead to a greater risk of instability. 3. 1. 4. 5 INSTALLABILITY ISO defines Installability as The capability of the software product to be installed in a specified environment24. Installability requirements are generally specified in the form of an installation process. The target environment in this case will have to be cognize at the development time.Installability is measured as a percentage exercised of the total specified Installability requirements. In the Sri Lankan context, Installability is com monly referred as Deployability. 3. 1. 5 RELATIONSHIPS OF VARIABLES Having identified the variables and attributes, it had been determined to limit the study to following variables, after interviewing key quality assurance personnel in target organizations. Based on their arguments, on applicability to offshore organizations, the best suited variables have been selected for the study. parasitical shifting Effectiveness of Software Quality Assurance nonsymbiotic Variables . Correctness a. Completeness b. Consistency 2. Testability a. Simplicity b. Modularity c. Structuredness 3. Changeability a. Simplicity b. Coupling 4. Stability a. Changeability 5. Installability Having identified the variables, following relationships have been derived based on the reviewed literature in the previous section. Correctness Testability Effectiveness of Software Quality Assurance Changeability Stability Installability Independent Variables Figure 6 Schematic diagram for conceptual framework Depen dent Variable 3. 2 HYPOTHESES FORMULATEDIn order to statistically test the derived conceptual framework, following hypotheses have been formulated. Since the study is targeted to test each independent variable separately, hypotheses too have been formulated independently to each independent variable. H01 there is no relationship among the Correctness of software developed and released to QA team), on the authority of software quality assurance approach. HA1 the greater the Correctness of software developed and delivered to QA team, the higher the say-so of software quality assurance approach.H02 there is no relationship between the Testability of software developed and released to QA team, on the forte of software quality assurance approach. HA2 the greater the Testability of software developed and delivered to QA team, the higher the effectiveness of software quality assurance approach. H03 there is no relationship between the Changeability of software developed and released t o QA team, on the effectiveness of software quality assurance approach. HA3 the greater the Changeability of software developed and delivered to QA team, the higher the effectiveness of software quality assurance approach.H04 there is no relationship between the Stability of software developed and released to QA team, on the effectiveness of software quality assurance approach. HA4 the greater the Stability of software developed and delivered to QA team, the higher the effectiveness of software quality assurance approach. H05 there is no relationship between the Installability of software developed and released to QA team, on the effectiveness of software quality assurance approach. HA5 the greater the Installability of software developed and delivered to QA team, the higher the effectiveness of software quality assurance approach. RE seaRCH DESIGN Research design will digest the roadmap of achieving the research objectives thorough the identified variables and theoretical framewor k. Details of study spirit of the study Type of investigation Extent of researcher interface tokenish studying events as they normally occur and defining a framework Study setting Measurement Measurement and measures Effectiveness of Software Quality Assurance in Emerging Offshore Development Enterprises in Sri Lanka descriptive quality evaluation framework Hypothesis testing to validate the evaluation frameworkCorrelation study of correlations to effectiveness against evaluation factors Noncontrived study in real business environment Quality factors and their applicability through quality matrices and Likert cuticles Data digest 1. Classification of data 2. Goodness of data Unit of analysis take in design Time horizon Data collection method 3. Hypotheses testing Individuals based on job categories in Offshoring organizations Judgmental sampling of individual in the entire population of offshore enterprises Crosssectional Interviews, Questionnaires, Observations Figure 7 The re search design 4. 1 TYPE AND NATURE OF THE STUDYThe study was an empirical study through analysis of responses to the questionnaires which was formulated through the conceptual framework. 4. 2 information COLLECTION METHODS Since the study is on offshore software development organizations, it has been decided to collect data from all registered companies in Software Exporters Association Sri Lanka and sevener other offshore software development organizations in Sri Lanka. There were twoscore seven registered members as of first August, 2007. Questionnaires were distributed to the key quality assurance person or to the most senior quality assurance person in each organization. . 2. 1 QUESTIONNAIRE DESIGN A structured questionnaire was used to hit responses apart from the preliminary interviews. The questionnaire is divided in to four main sections. region one has eleven questions, capturing organizational demographics of the responder. prick two has six questions, to buzz off r esponders personal demographics. Section three is the main section of the questionnaire which captures organizations software quality assurance, project specific demographics and responses to test the conceptual framework. Section four is targeted to capture additional information for the conceptual framework. RESULTS OF DATA abstract Responses received had been categorized to qualitative data and quantitative data. Qualitative data had been used to understand the responders and company background. Quantitative responses, where the scale data is measured have been assign scores as per following table for statistical analysis. Response Selected Strongly disagree Disagree immaterial Agree Strongly agree Score Assigned 1 2 3 4 5 Table 5 Rates wedded for questionnaire responses Each response was individually assessed to ensure data validity and integrity.Incomplete responses have been followed up with the responder with available contact information and have been able to complete in many instances. For the blank responses, score three was assigned in case the question is not applicable to the responders organization. Following summary shows the statistics of the questionnaire distribution and responses received. Number of Organizations that Questionnaire had been sent 47 SEA registered companies + 7 other offshore companies Total Responses Received 39 incapacitate / Unusable 2 Number of Valid Responses 37Table 6 Statistics of questionnaire distribution responses received 5. 1 PILOT STUDY To test the primary data a pilot study was run among fourteen Quality Assurance Engineers at an offshore software development organization, using a draft questionnaire. On the scale of reliability in order to treat results with credibility25 and the internal dead body of the draft questionnaire, was checked by using Cronbachs important coefficient. The alpha coefficient should be above . 7 for the scale to be reliable26. The overall Cronbachs alpha coefficient was . 81, thus the questionnaire was considered to have a good internal consistency and suitable for collecting the data for the main study. Details of Cronbachs alpha are discussed under Analysis of Reliability Section, below. 5. 2 PRELIMINARY compend All thirty seven organizations selected as valid responses are merchandise software. 89. 19% of the selected organizations are locally owned while 10. 81% of organizations which are in Sri Lankan doing are owned by foreign parties. 64. 86% of the target organizations are project based companies while 21. 2% of the organizations focus only on their own products. However 13. 51% of the organizations undertake lymph node projects while they market their own products. 10 8 No. of Organizations 6 4 2 0 1. 00 2. 00 3. 00 4. 00 5. 00 6. 00 7. 00 8. 00 12. 00 14. 00 No. of years in Sri Lankan movement Figure 8 Analysis of organizations against number of years in operation According to the above graph, most of the Sri Lankan offshore organizations und er the current study have started their operation two years before. 75. 68% of the responders were males and the balance 24. 32% were females.The average age of responders was 30. 11 years. On an average, they posses one year of experience in their current position in the respective organizations. The following map represents the education level of responders. 30 25 20 Count 15 10 5 0 Non IT alumnus IT/Comp. Science Post Graduate Graduate Deploma MSc/MBA/Post Graduate Degree Other fostering Level Figure 9 Education level of responders Majority of quality assurance heads in the target organizations posses Information Technology or a Computer Science degree. 3. 03% Little Early 9. 09% On Time 24. 24% Too Delayed 3. 64% Little Delayed Figure 10 Project finale against estimates Responders were asked to select a completed project/product when they responded to part 3 of the questionnaire. The above pie chart highlights the project/product completion time against the estimates of the selected projects by the responders. From the selected projects/products, majority have been completed with a teentsy delay from the estimates. cockeyed and the variance are calculated for each question under each independent variable and the dependent variable through the assigned scores as per Table 5.Question No. Question basal Variance Effectiveness of Software Quality Assurance 18 19 20 21 22 23 Software QA is a very important discipline in our organization Without QA our products/services will not meet current level of customer satisfaction Our Software QA approach/practice helps us in winning new businesses Our organization has adequate number of QA Human Resources Our organization has invested enough in Software QA tools Our Software Development or any other Process has considered QA as a major practice 3. 622 4. 081 3. 811 3. 919 3. 514 3. 865 0. 686 0. 99 0. 658 0. 465 0. 812 0. 842 Correctness 30 31 32 33 34 35 36 If the systems or components we deliver meet specificat ions to 100%, we can say that its a high quality factor Systems or components we deliver, always met specifications consistency of functionality/operations/navigation of the designed system always contributed to high quality System maintained Uniformity of functionality/operations/navigation across individual functions If a function of a system, completes its execution without in between failures, we can say it is a high quality factor.Our systems do not fail in executing a function or procedure to its completion Our QA team measures our systems, whether they meet specifications or not 3. 703 3. 568 3. 703 3. 324 3. 243 3. 243 4. 108 0. 604 1. 141 0. 715 1. 003 0. 745 0. 634 0. 544Testability 37 If all functionality/operations/navigation of systems could be tried enough, then we can say it denotes high quality All the functionality/operations/navigation of our systems are properly being tested by our QA team Even the complex operations of our systems are represented by simple user interactions in order to make applications simple and user cordial Our applications are decomposed in to manageable modules in implementation in a practical manner Consistent organization of modules/code are patent in our applications Our QA team measures or put emphasis on testability (Simplicity, Modularity, structuredness) of applications during the QA circle 4. 595 0. 303 38 4. 514 0. 312 39 4. 297 0. 270 40 3. 946 0. 330 41 3. 838 0. 417 42 4. 432 0. 308 Changeability 43 If a product allows a specified modification to be implemented without much difficulty, then we can say it denotes a high quality factor Our systems do not need much effort to make minor specification changes (i. e.Adding a new field to a form) at implementation or quality assurance stage Our systems maintain low interactions between individual modules, therefore it is easier to change individual components without affecting others Our QA team measures put much emphasis to test changeability and stability of systems during the QA pass 4. 000 0. 111 45 3. 946 0. 164 46 3. 838 0. 251 48 3. 919 0. 299 Stability 44 If the systems avoid unexpected effects after modifications, it denotes a high quality or its a high quality factor After the design changes done to one module, our systems have very few side effects to other modules Our QA team measures put much emphasis to test changeability and stability of systems during the QA cycle 3. 595 . 359 47 3. 703 0. 437 48 3. 919 0. 299 Installability 49 If the system could be installed in a specified environment without challenges, it denotes high quality or it can be considered as a high quality factor Our systems do not get challenged during the installation in the agreed/specified environment Our QA team measures Installability of systems they test 3. 568 0. 863 50 3. 162 3. 541 0. 862 1. 311 51 Table 7 kernel and variances of questions Frequency distributions of responses to each of above questions have been presented in Appendix 2. 5. 3 S ECONDARY RESULTS ANALYSIS Primary data is further analyzed to derive more meaningful results.For statistical analysis, the ratings gathered through individual questions were summed up to derive scores for individual independent variables. Variable = sum of tag for relevant questions I. e. Correctness = Q30 + Q31 + Q32 + Q33 + Q34 + Q35 + Q36 try Mean, where, n = sample size, and = scores Sample Variance, prototype Deviation, Following table illustrates the statistics of independent variables, which denotes the effectiveness of quality assurance. Standard Deviation 0. 569 0. 552 0. 422 0. 327 0. 445 0. 752 Variable Effectiveness of QA Correctness Testability Changeability Stability Installability Mean 3. 802 3. 556 4. 270 3. 926 3. 739 3. 423 Variance 0. 324 0. 305 0. 178 0. 107 0. 198 0. 566Table 8 Basic statistics of independent variables and the dependent variable Following is the graphical illustration of above statistics. 4. cholecalciferol 4. 000 3. 500 3. 000 2. 500 2. 000 1. 500 1. 000 0. 500 0. 000 Mean Variance Std. Div. Figure 11 Basic statistics of independent variables According to the above illustration, Testability contributes to QA effectiveness most while Changeability trunk at the second position. Installability was rated as of least significant to the QA Effectiveness in the subject domain. 5. 3. 1 ANALYSIS OF RELIABILITY OF DATA Cronbachs alpha measure is used to determine how well the target independent variables measure single, unidimensional QA Effectiveness latent construct.Cronbachs alpha can be written as a function of the number of test items AND the average inter-correlation among the items. N where, N = number of items and = inter-item correlation among items. Cronbachs Alpha Based on Cronbachs similar Alpha ( Items . 912 . 918 Table 9 Reliability statistics N of Items 28 Cronbachs alpha for all twenty eight questions is 0. 912, which denotes that the collected data is pleasurable for the research. 5. 4 HYPOTHESES TESTING Anal ysis had been done to test each set of possible action to find out whether there are relationships defined through the hypotheses exist among independent variables and the dependent variable.The correlations between the factors hypothesized to effectiveness of quality assurance shown in the following table Set of Hypothesis/Independent Variable H1Correctness H2Testability H3Changeability H4Stability H5Installability ** Correlation is significant at the 0. 01 level (2-tailed). Pearson Correlation/ Effectiveness of QA . 678** . 589** . 559** . 728** . 613** Sig. (2-tailed) . 000 . 000 . 000 . 000 . 000 Table 11 Correlations between hypotheses for quality assurance Hypothesis H1 According to Hypothesis H01, Correctness which is influenced by Consistency and Completeness has a positive relationship to effectiveness of software quality assurance approach. Since this hypothesis is supported by the data analysis (Sig. value was . 000, p