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

EFFECTIVENESS OF com projecter pack succession timberland ASSURANCE IN OFFSHORE DEVELOPMENT ENTERPRISES IN SRI LANKA Malinda Sirisena, Department of Com giveer Science & Engineering, University of Moratuwa. ABSTRACT The motor of the enquiry absorbd in this thesis is to assess the specialty of package tincture assumption approaches of Sri Lankan shoreward softw be chance oning judicatures, and to propose a exemplar which could be utilise across sever aloney inshore softw atomic number 18 egressgrowth plaques. An empirical story was conducted exploitation derived frame conk from public softw atomic number 18 lumber military rating complicates.The research instrument employed was a enquirenaire eyeshot among thirty seven Sri Lankan registered shoreward software study dust of ruless. The findings demonstrate a cocksure place of military posture of software package timberland pledge the stronger predictors of perceptual constancy, Installability , Correctness, Testability and changeableness. The present watchs recomm end upations indicate a need for more emphasis on software part impudence for the Sri Lankan seaward software development compositions. Keywords software point of intersection tonus Assurance (SQA), Offshore software product Development, tincture Assurance Evaluation Models, durability of character reference Assurance. BACKGROUND re mathematical harvestion software Quality Assurance (QA) plays a major(ip) role in successful fulfilation and tutelage of a software project. In many organizations, QA has been just traded-off to project cost 1. The motivation of this research is to foreground the value of Software Quality Assurance against the scotchal cost. The IEEE standard ANSI/IEEE 730-2002 regulates software olfactioning government agency as a excogitationned and out(a)lineatic precedent of all actions necessary to provide adequate boldness that the software conforms to established practiced requirements2.QA is non only keeping a direct kind of visualizeing client satisfaction, but it has a very senior high touch on project schedules and cost. Failing to pay circumspection is often resulted in budget over caters 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 Ameri coffin nail organizations. A dodge of dogma hospitals conservatively estimates $17. 8 million saved on an investment of $2. 5 million in bore heed over a five-year time period. The University of pascal saved more than $60,000 a year from bingle project focused on reducing get off cost. The U. S. Bureau of Labor Statistics reduced the time call for to produce the monthly Consumer Price Index (CPI), compiled by 650 mess in five departments, by 33 percent with no loss in accuracy. 4 even off in Sri Lankan software engineering companies, birth been ac acquain tance QA as an important element. In 2005, Affno (www. affno. lk) has won the topic Best Quality Software Gold divide for their output eTender, which highly- create for Sri Lanka Telecom to automate their tendering fulfill 5. 2 THEORETICAL BASE OF THE STUDY 2. WHAT IS SOFTWARE type The IEEE standard ANSI/IEEE 730-2002 defines software bore sanction as a planned and clayatic pattern of all actions necessary to provide adequate confidence that the software conforms to established technical requirements2. By liberation cut down the path of IEEE definition, thither are both major camps when defining software spirit6 1. Conformance to specification eccentric defines in terms of the take which the harvest-tide or service hits its written specifications. 2. Meeting node needfully run into nodes expressed or implicit needs, ir various(prenominal) of any measur fit product or service characteristics.Currently software whole step self-assertion is amountd in dicken s slipway from technical perspective and from user perspective7. In the technical perspective of measuring software gauge is base on specifications. Developers vizor tint and train specifications in terms of errors in code with examen mathematical process and through separate mechanisms such as formal specifications, structured programming8. pole-user perspective of software timber is measured through user draw to mention how well software meets user expectations. User dissatisfactions do not necessarily be resulting from perishure to meet specifications or coding errors. . 2 SOFTWARE flavor MANAGEMENT PHILOSOPHIES This persona of the writings presents different philosophies of case from discover points of eccentric focus gurus. These flavour management philosophies could be a good alternative to formalised step gravels which the research is going to base on. Quality management requires client satisfaction, prefers prevention to inspection, and recogni zes management responsibleness for fibre9. 2. 2. 1 DEMING AND FOURTEEN POINTS FOR MANAGEMENT Walter Edward Deming defines quality in terms of customer satisfaction10.Customer satisfaction is beyond conformism to specifications. harmonize to Deming, the judge of quality should be the end user or the customer. Deming argues that management system should implement in a way that everyone in the organization to be responsible for quality of their output to the indispensable stakeholders. He introduced fourteen points for management for people to derive and implement necessary quality transformation10 1. Create labor of purpose for advantage of product and service balk in business and provide jobs through innovation, research, continual remedyment and brinytenance. 2.Adopt the forward-looking philosophy For the new economic age, management needs to take prefaceership for switch over into a learning organization. 3. Cease dependence on megabucks inspection Eliminate the need for mass inspection by building quality into the product. 4. End awarding business on price suffer at minimum union cost and feign towards single suppliers. 5. Improve constantly and forever the system of production and service Improvement is not a one-time effort. Management is obligated to continually look for ways to reduce waste and improve quality. 6. drag for training Workers should be trained properly on their jobs. . comprise leadership Leading shall consist of financial aiding people to do a better job and to learn by objective methods. 8. Drive out aff ripe(p) To assure better quality and productivity, people feel secure. 9. Break down barriers surrounded by departments Team practice culture across departments. 10. Eliminate slogans, exhortations and numerical stains permit workers formulate their own slogans. Then they exit be committed to the contents. 11. Eliminate numerical quotas or work standards Quotas take into account only numbers, not quality or me thods. They are usually a contract of inefficiency and high cost.A soulfulness, in pasture to hold a job, pass on try to meet a quota at any cost, including doing damage to the company. 12. Remove barriers to taking self-conceit in workmanship People are g broken ining to do a good job and distress when they green goddessnot. 13. Institute a vigorous programme of education Both management and the work force forget develop to be educated in the new go to bedledge and netherstanding, including groupwork and statistical techniques. 14. Take action to grasp the transformation It volition require a finicky top management team with a plan of action to carry out the quality mission.A vital mass of people in the company essentialiness understand the 14 points. 2. 2. 2 JURAN AND THE IMPORTANCE OF vertex MANAGEMENT COMMITMENT TO QUALITY Joseph M Juran proposes devil meanings to quality11 1. Quality consists of those product features which meet the need of customers and the reby provide product satisfaction. 2. Quality consists of wantondom from deficiencies. In the handbook Juran propose quality as seaworthiness for use rather than meeting customer needs he argues that it is not a feasible tax to meet customer need. His cyclorama is some(prenominal) enveloping(prenominal) to the thought conformance to specifications.Juran proposes three fundamental managerial processes for the chore 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 stimulate those products and services with the correct associates and then facilitates the transfer of this knowledge to the producing arm of the organization. 2. Quality rig A process in which the product is examined and guessd against the original requirements expressed by the customer. Problems detected are then corrected. . Qualit y improvement A process in which the sustaining mechanisms are put in place so that quality can be contactd on a continuous basis. This includes allocating resources, depute people to pursue quality projects, training those touch in pursuing projects, and in general establishing a permanent structure to pursue quality and cite 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 commence somewhat four fundamental absolutes of quality management12 1.Quality is defined as conformance to requirements, not as goodness or elegance 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 oriented quality organization everyone has the responsibility fo r his or her own work. There is no one else to catch errors. 3. The exploit standard must(prenominal) be Zero Defects, not thats close abundant. Crosby has advocated the notion that zero errors can and should be a target. . The measurement of quality is the cost of quality. Costs of imperfection, if corrected, throw away an immediate beneficial effect on bottom-line process as well as on customer relations. 2. 2. 4 ISHIKAWA AND FISHBONE DIAGRAM Kaoru Ishikawa defines quality as meeting customer needs13. He further argues that no specific quality standard could ever define and by-line them does not meet the expected quality levels. According to Ishikawa, quality is a very immense concept which goes beyond product, service, process, nurture quality, etc.He introduced quality circles through Fishbone plats. 2. 2. 5 FEIGENBAUM AND TOTAL QUALITY CONTROL Armand Vallin Feigenbaum built his thought more or less total quality control14. Feigenbaum states that quality is a dynamic g ene which must be defined in terms of customer experiences. He further states that quality should satisfy customers denotive and implicit needs14. 2. 3 SOFTWARE QUALITY MODELS earlier section focus on different hatful points of quality management gurus. These points will be adjuvant in solving common quality management problems in Sri Lankan, offshore enterprises.Quality management philosophies presented in the forward 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 self-sufficient multivariates for legitimate take in. 2. 3. 1 MCCALLS QUALITY MODEL Jim McCalls quality model is primarily aimed towards the system developers and development process, however he has well-tried to bridge the gap between users and developers by cerebrate on number of quality factors, considering both users and developers priorities16, 17.The quality model is conjugationized more or less three quality characteristics16 fingers breadth 1 McCalls quality model organized around three types of quality characteristics McCalls model what is more elaborated with a hierarchy of factors, criteria and metrics around the three types of major perspectives. check 2 McCalls quality model Eleven factors on the leftfield side of the model represent the external view of quality as viewed by end users. These xi factors refer to twenty three quality criteria, which describe the internal view of software. The evaluation is done by answering each quality criteria with yes and no.Finally the quality level is derived as a percentage establish on the responses original as yes. 2. 3. 2 BOEHMS QUALITY MODEL Barry W Boehms model has similarities to McCalls model. His qualitative approach of defining quality stems from three levels in the hierarchy, which ends with primitive characteristics18. These primitive characteristics by the piece contribute to the overall quality level. Figure 3 Boehms software quality characteristics tree19. Quality measurement is carried out through extent or pointedness to which the product or service achieves 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 higher up six areas of vastness. Figure 5 ISO 9126 quality connects 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 abstract FRAMEWORK This chapter elaborates how the conceptual simulation for the dissect has been derived through the subsisting work identified in the literature review. . 1 EXISTING WORK Since the study is on evaluating software quality from software developing organizations view, it is necessary to fi lter down the quality attributes discover in the literature, only to represent developer view of software quality. Therefore it has been decided to take the union of developer related to 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 some attributes are subjective to their fivefold definitions.For a consistent interpretation of the quality attributes, the definitions of attributes ease up been used according to Software Engineering Institutes (SEI) Software engineering Roadmap glossary23 and ISO 912624 definitions. 3. 1. 1 DEVELOPER point ATTRIBUTES FROM MCCALLS MODEL McCalls model primarily goes hand in hand with external quality factors. pastime are the quality attributes extracted from McCall model, which are related to developer related quality based on SEI definitions. Se lected specify Maintainability SEI Definition23 The ease with which a software system or destiny can be odified to correct faults, improve performance, or some other attributes, or adapt to a assortmentd surround. The degree to which a system or chemical element facilitates the establishment of outpouring criteria and the performance of rills to determine whether those criteria put one over been met. The ease with which a system or component can be change for use in covers or surroundingss other than those for which it was specifically knowing. 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 figuring program or software system. The ability of two or more systems or components to exchange information and to use the information that has been exchanged. Testability Flexibility Portability Reusability Interoperabilit y put over 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 quality, is much similar to McCalls model.After evaluating definitions, pastime two attributes were added to the list. Selected proportion 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 reputation of the desired change has been determined. delay 2 supernumerary developer related quality attributes from Boehms model 3. 1. 3 ADDITIONAL ATTRIBUTES FROM ISO 9126 Following are sub-attributes taken from the ISO 9126 definitions.Selected refer Analyzability ISO Definition24 The force 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 identifie d. The power of the software product to enable a condition modification to be use. The potency of the software product to avoid unexpected cause from modifications of the software. The ability of the software product to be vary for different specified environments without applying actions or means other than those provided for this purpose for the software considered. The strength of the software product to be installed in a specified environment. The capability of the software product to co-exist with other fencesitter software in a common environment manduction common resources. changeability constancy 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. circuit card 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 interest for the current study. 1. Correctness 2. Testability 3. Changeability 4. stableness 5. Installability In the following 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 carrying into action23. McCall attributes correctness through16 Traceability Completeness ConsistencyThrough traceability, it makes thinkable to know the familys of each module or component and thereby high confidence states correctness. Completeness assures that there are no parts left in terms in executing a accountability of a system or a procedure thereby light speed% completeness ratio guarantees correctness. Inconsistent systems or functions will lead to higher error probability therefore it is a part of correctness. Through the initia l discussions with some primaeval military group, it was revealed that these characteristics are equally hard to reach to achieve Correctness. . 1. 4. 2 TESTABILITY SEI defines judgeability as The degree to which a system or component facilitates the establishment of psychometric attempt criteria and the performance of tests to determine whether those criteria eat been met23. Both McCall and Boehm have attributed testability to quality presumption on following characteristics16, 18 simplicity instrumentality Self-descriptiveness Modularity and structuredness Accountability approachability Communicativeness. Simplicity of applications will make easier in testing comparatively to complex applications.Instrumentation makes possible to put probes in the system in recite to deduce test data. Self-descriptive systems have inbuilt help or system documentation which will be sufficient to understand the system by going through. Modularity helps in isolating system tests whi ch structuredness denotes consistent organization of the system. Accountability on system for which it is possible to measure the usage of the code19. Such measurements are typically covered by debugging tools, 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. in time changeability could be achieved through Aiming simple resolving power rather than complicated systems as by genius simple applications are easier to change. Low coupling of unmarried modules of a system as lower interactions m ake easier to change man-to-man components. Designing the systems change in mind from the beginning eon keeping application evolution. 3. 1. 4. 4 STABILITY ISO defines stability as The capability of the software product to avoid unexpected set up from modifications of the software24. Therefore stability in this mount does not denote the ability of the system to demonstrate s hold over behavior when used. that, 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 great 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 generalization process. The target environment in t his case will have to be known at the development time.Installability is measured as a percentage exercised of the total specified Installability requirements. In the Sri Lankan context, Installability is commonly referred as Deployability. 3. 1. 5 RELATIONSHIPS OF VARIABLES Having identified the variables and attributes, it had been decided to limit the study to following variables, after interviewing key quality say-so personnel in target organizations. Based on their arguments, on applicability to offshore organizations, the best suited variables have been selected for the study. Dependent Variable durability of Software Quality Assurance Independent 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 se ction. Correctness Testability authorization of Software Quality Assurance Changeability Stability Installability Independent Variables Figure 6 Schematic diagram for conceptual framework Dependent 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 also have been formulated singly to each independent variable. H01 there is no relationship between the Correctness of software developed and released to QA team), on the dictate-so of software quality assurance approach. HA1 the greater the Correctness of software developed and slanted to QA team, the higher the intensity of software quality assurance approach.H02 there is no relationship between the Testability of software developed and released to QA team, on the effectivity of software quality assurance approach. HA2 the greater the Testability of softwa re 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 to 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 effectiv eness of software quality assurance approach. RESEARCH objective Research design will outline the roadmap of achieving the research objectives thorough the identified variables and theoretical framework. Details of study Purpose of the study Type of investigation finish of researcher interface Minimal studying events as they normally occur and defining a framework Study setting Measurement Measurement and measures strong point of Software Quality Assurance in acclivitous Offshore Development Enterprises in Sri Lanka Descriptive quality evaluation framework surmise testing to corroborate 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 scales Data analytic thinking 1. Classification of data 2. Goodness of data unit of compendium Sampling design Time perspective Data wrap upion method 3. Hypotheses t esting 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 research 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 DATA 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 connecter Sri Lanka and seven other offshore software development organizations in Sri Lanka. There were forty 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 anatomy A structured questionnaire was used to gather responses apart(predica te) from the preliminary interviews. The questionnaire is divided in to four main sections. contribution one has eleven questions, capturing organizational demographics of the responder. Section two has six questions, to capture responders 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 supererogatory information for the conceptual framework. RESULTS OF DATA ANALYSIS Responses real had been categorized to qualitative data and quantitative data. soft data had been used to understand the responders and company background. Quantitative responses, where the scale data is measured have been assigned degrees as per following table for statistical analysis. Response Selected Strongly discord Dis go Neutral Agree Strongly agree Score Assigned 1 2 3 4 5 Table 5 pass judgment given for q uestionnaire 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 impart Responses Received 39 Invalid / Unusable 2 Number of Valid Responses 37Table 6 Statistics of questionnaire distribution responses received 5. 1 PILOT STUDY To test the old data a pilot study was run among fourteen Quality Assurance Engineers at an offshore software development organization, using a outline questionnaire. On the scale of reliability in order to treat results with credibility25 and the int ernal consistency of the draft questionnaire, was checkered by using Cronbachs alpha 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 satisfactory for collecting the data for the main study. Details of Cronbachs alpha are discussed under psychoanalysis of reliability Section, below. 5. 2 PRELIMINARY ANALYSIS All thirty seven organizations selected as valid responses are exporting software. 89. 19% of the selected organizations are locally owned while 10. 81% of organizations which are in Sri Lankan operation 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 client projects while they commercialise 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 historic period in Sri Lankan Operation Figure 8 Analysis of organizations against number of eld in operation According to the above graph, most of the Sri Lankan offshore organizations under 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 chart represents the education level of responders. 30 25 20 Count 15 10 5 0 Non IT grade IT/Comp. Science venture Graduate Graduate Deploma MSc/MBA/Post Graduate Degree Other Education 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% weeny Early 9. 09% On Time 24. 24% in like manner Delayed 3. 64% Little Delayed Figure 10 Project shutting against estimates Responders were asked to select a perfect 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 little delay from the estimates. Mean and the sport are calculated for each question under each independent variable and the dependent variable through the assigned dozens as per Table 5.Question No. Question Mean 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 benignant new businesses Our organization has adequate number of QA man Resources Our organization has invested enough in Software QA t ools Our Software Development or any other turn 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 specifications to 100%, we can say that its a high quality factor dodgings or components we deliver, always met specifications Uniformity of functionality/operations/ sailplaning 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 slaying 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 tested 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 friendly Our applications are decomposed in to manageable modules in implementation in a practical manner unchanging organization of modules/code are evident in our applications Our QA team measures or put emphasis on testability (Simplicity, Modularity, structuredness) of applications during the QA cycle 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 accommodate humble 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 cycle 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/specifie d 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 Means and variances of questions Frequency distributions of responses to each of above questions have been presented in Appendix 2. 5. 3 vicarious RESULTS ANALYSIS Primary data is further canvass to derive more meaningful results.For statistical analysis, the ratings gather 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 Sample Mean, where, n = audition size, and = scores Sample Variance, Standard deviance, 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. 2 70 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 deterrent example of above statistics. 4. euchre 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 remains 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. Cronbac hs Alpha Based on Cronbachs Standardized 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 delicious for the research. 5. 4 HYPOTHESES TESTING Analysis had been done to test each set of hypothesis 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 ensnare 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 wh ich 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