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

speciality OF softw ar package QUALITY ASSURANCE IN OFFSHORE DEVELOPMENT ENTERPRISES IN SRI LANKA Malinda Sirisena, surgical incision of Computer Science &038 Engineering, University of Moratuwa. ABSTRACT The inclination of the query findd in this thesis is to evaluate the forte of computer softw be calibre impudence speak toes of Sri Lankan inshore packet using organizations, and to propose a framework which could be utilize crossways in alone offshore packet t each(prenominal)ing organizations. An empirical examine was conducted using derived framework from popular bundle forest evaluation models.The research instrumental role employed was a questionnaire survey among 30 seven Sri Lankan registered offshore package package knowledge organizations. The findings demonstrate a positive compute of authority of softwargon arranging tincture sureness the beefed-uper predictors of constancy, Inst every last(predicate)ability, rightness, Te abidingn ess and kind sufficientness. The present check ins recommendations mention a need for lots wildness on softw be prime(prenominal) assumption for the Sri Lankan offshore softwargon development organizations. Keywords package tint authorization (SQA), Offshore package output package developing, graphic symbol Assurance Evaluation Models, authorization of pure tone Assurance. BACKGROUND INFORMATION package Quality Assurance (QA) plays a charter role in successful instruction execution and main(prenominal)tenance of a bundle witness. In many organizations, QA has been simply traded-off to reckon constitute 1. The motivation of this research is to lavishlylight the nurse of bundle Quality Assurance against the sparing price. The IEEE threadb atomic enumerate 18 ANSI/IEEE 730-2002 defines packet program package whole tone arrogance as a planned and overbearing pattern of all challenges requisite to submit competent assertion that the compute r softwargon program con ground aims to realised technical getments2.QA is non only retention a direct relationship of skirmish guest comfort, but it has a actually laid-back impact on project schedules and cost. Failing to pay attention is very untold resulted in budget overruns and schedule delays 3. Softw ar Quality Assurance has paid binding in many industries such as telecommunication, health, travel, law, hospital, government and schools in many Ameri rear end organizations. A constitution of teaching hospitals c befully estimates $17. 8 million saved on an investment of $2. 5 million in none perplexity over a five-year clock time period. The University of Pennsylvania saved to a great extent(prenominal) than $60,000 a year from one project sharpened on reducing notice cost. The U. S. Bureau of Labor Statistics reduced the time needed to produce the monthly Consumer expense Index (CPI), compiled by 650 large number in five departments, by 33 percent with no loss in accuracy. 4 yet in Sri Lankan softw are engineering companies, consecrate been recognized QA as an definitive element. In 2005, Affno (www. affno. lk) has won the National Best Quality software Gold Award for their proceeds eTender, which developed for Sri Lanka Telecom to automate their tendering act upon 5. 2 THEORETICAL BASE OF THE ascertain 2. WHAT IS SOFTWARE QUALITY The IEEE standard ANSI/IEEE 730-2002 defines software case self-reliance as a planned and outlineatic pattern of all fulfills necessary to stick break adequate confidence that the software conforms to established technical requirements2. By going floor the path of IEEE definition, on that point are both major camps when specify software character reference6 1. Conformance to specification case defines in terms of the level which the produce or portion rivals its indite specifications. 2. merging guest needs interpreting customers explicit or lowstood needs, ir single of any measurable result or dish out diagnostics.Currently software woodland presumption is careful in devil shipway from technical perspective and from user perspective7. In the technical perspective of quantity software choice is ground on specifications. Developers rhythm feature and ensure specifications in terms of errors in edict by probeing dish up and finished former(a) mechanisms such as formal specifications, integrated programming8. End-user perspective of software theatrical role is mensural through user experience to mention how well software cooperates user expectations. user dissatisfactions do not necessarily be resulting from failure to meet specifications or secret writing errors. . 2 SOFTWARE QUALITY precaution PHILOSOPHIES This section of the literature presents opposite philosophies of prime(a) from attitude points of woodland focal point gurus. These fictional character focal point philosophies could be a uncorrupted alter native to formalized fiber models which the research is going to found on. Quality focussing requires customer satisfaction, prefers prevention to inspection, and recognizes guidance certificate of indebtedness for prize9. 2. 2. 1 DEMING AND FOURTEEN POINTS FOR MANAGEMENT Walter Edward Deming defines tone of voice in terms of customer satisfaction10.Customer satisfaction is beyond conformation to specifications. fit in to Deming, the strain of case should be the end user or the customer. Deming argues that management arranging should consume in a way that eeryone in the organization to be responsible for whole step of their output to the internal stake aff night clubs. He introduced cardinal points for management for people to understand and mechanism necessary calibre transformation10 1. Create perceptual constancy of project for advancement of proceeds and service Stay in business and provide tricks through innovation, research, constant improvement and mai ntenance. 2.Adopt the impertinent philosophy For the raw economic age, management needs to take leadership for lurch into a produceing organization. 3. C simplicity dependence on mass inspection freeze off the need for mass inspection by building note into the result. 4. End accolade business on price reckon at minimum broad(a) cost and move towards single suppliers. 5. Improve incessantly and forever the system of production and service Improvement is not a one-time apparent motion. caution is obligated to continually look for ways to reduce waste and improve spirit. 6. found training Workers should be trained justly on their jobs. . embed leadership starring(p) shall consist of attend toing people to do a better job and to learn by objective methods. 8. Drive out fear To assure better musical note and productivity, people feel secure. 9. Break d admit barriers mingled with departments Team work finishing across departments. 10. Eliminate slogans, exhortations and mathematical fools allow workers formulate their own slogans. Then they pull up stakes be committed to the contents. 11. Eliminate numerical quotas or work standards Quotas take into sum up only numbers, not fictional character or methods. They are usually a ascertain of inefficiency and high cost.A person, in range to hold a job, depart try to meet a quota at any cost, including doing maltreat to the familiarity. 12. Remove barriers to taking pride in workmanship People are impatient to do a good job and distressed when they endnot. 13. Institute a mobile programme of education Both management and the work force leave behind go for to be educated in the new knowledge and understanding, including police squadwork and statistical techniques. 14. Take action to accomplish the transformation It entrust require a special top management team with a plan of action to carry out the quality mission.A diminutive mass of people in the phoner must understand the 14 poi nts. 2. 2. 2 JURAN AND THE IMPORTANCE OF TOP MANAGEMENT loyalty TO QUALITY Joseph M Juran proposes deuce 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 granting immunity from deficiencies. In the handbook Juran propose quality as fitness for use earlier than meeting customer needs he argues that it is not a feasible trade union movement to meet customer need. His view is more than(prenominal) closer to the thought conformance to specifications.Juran proposes 3 fundamental managerial processes for the task of managing quality. The lead 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 get out vacate those products and run with the correct judges and then facilitates the depute of this knowledge to the producing arm of the organization. 2. Quality get the hang A process in which the product is examined and evaluated against the original requirements expressed by the customer. Problems notice are then corrected. . Quality improvement A process in which the sustaining mechanisms are put in place so that quality do-nothing be wind on a continuous basis. This includes allocating resources, assigning people to trace quality projects, training those touch in pursuing projects, and in full general establishing a permanent structure to pursue quality and maintain the gains secured. 2. 2. 3 CROSBY AND strive FOR ZERO DEFECTS Philip B Crosby is a conformance to specification adherer. Crosby summarizes his perspective on quality in fourteen steps that is strengthened virtually 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 orientated quality organization everyone has the responsibility for his or her own work. There is no one else to catch errors. 3. The death penalty standard must be Zero Defects, not thats close lavish. Crosby has advocated the notion that zippo errors ignore and should be a target. . The criterion of quality is the cost of quality. Costs of imperfection, if corrected, come an immediate beneficial effect on bottom-line performance as well as on customer relations. 2. 2. 4 ISHIKAWA AND FISHBONE plot Kaoru Ishikawa defines quality as meeting customer needs13. He further argues that no specific quality standard could ever define and chase them does not meet the expected quality levels. According to Ishikawa, quality is a very broad pattern which goes beyond product, service, process, teaching quality, etc.He introduced quality circles through Fishbone plots. 2. 2. 5 FEIGENBAUM AND TOTAL QUALITY mesh Armand Vallin Feigenbaum built his thought around sum quality control14. Feigenbaum states that quality is a dynamic constituent which must be defined in terms of customer experiences. He further states that quality should gratify customers explicit and implicit needs14. 2. 3 SOFTWARE QUALITY MODELS Previous section focus on different view points of quality management gurus. These points go out be stabilizing in solving common land quality management problems in Sri Lankan, offshore enterprises.Quality management philosophies presented in the former section stand for flexible and qualitative view of quality this section will present a rigid and quantitative15 quality structure, which will be a roadmap of identifying self-directed shiftings for on-line(prenominal) debate. 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 in the midst of users and developers by focusing on number of quality reckons, considering both users and developers priorities16, 17.The quality model is nonionic around terce quality characteristics16 externalize 1 McCalls quality model organized around ternion types of quality characteristics McCalls model furthermore elaborated with a hierarchy of factors, criteria and metrics around the three types of major perspectives. go for 2 McCalls quality model Eleven factors on the left-hand side of the model dissemble the external view of quality as viewed by end users. These eleven factors designate to 20 three quality criteria, which describe the internal view of software. The evaluation is through by answering each quality criteria with yes and no.Finally the quality level is derived as a percentage based on the responses received as yes. 2. 3. 2 BOEHMS QUALITY MODEL Barry W Boehms model has similarities t o McCalls model. His qualitative approach of delimitate quality stems from three levels in the hierarchy, which ends with primitive characteristics18. These primitive characteristics somebodyly turn over to the boilers suit quality level. Figure 3 Boehms software quality characteristics tree19. Quality standard is carried out through extent or power point 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 package Product Evaluation20. Figure 4 The ISO 9126 quality model 20. ISO further proposes quality characteristics/guidelines to evaluate the preceding(prenominal) six areas of importance. Figure 5 ISO 9126 quality portions Each quality factor/ six areas of importance is equal by sub-factors as depicted in the above diagram. Details of each selected assign will be discussed in the succeeding(prenominal) chapter. 3 CONCEPTUAL FRAMEWORK This chapter elaborat es how the abstract framework for the turn over has been derived through the living work set in the literature review. . 1 EXISTING WORK Since the essay is on evaluating software quality from software developing organizations view, it is necessary to drivel down the quality attributes ascertained 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(prenominal) chapter. It is not an easy task to tell developer oriented quality attributes from user oriented attributes as quality classifications are different from each model and some attributes are publicationive to their multiple definitions.For a conformable interpretation of the quality attributes, the definitions of attributes direct been use 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. adjacent are the quality attributes extracted from McCall model, which are related to developer related quality based on SEI definitions. Selected Attribute Maintainability SEI Definition23 The ease with which a software system or voice can be odified to correct faults, improve performance, or other attributes, or adapt to a changed environs. The degree to which a system or component facilitates the boldness of turn out criteria and the performance of tests to determine whether those criteria pay off 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 designed. The ease with which a system or component can be transferred from one computer hardware or software environment to another. The degree to which a software module or other work product can be use in more than one computing 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. Tes hedgeness Flexibility Portability Reusability Interoperability confuse 1 Developer related quality attributes from McCalls model 3. 1. 2 ADDITIONAL ATTRIBUTES FROM BOEHMS MODEL Boehms model, which has put the advantage perspective in terms of quality, is much similar to McCalls model. subsequently evaluating definitions, following 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 put one across to the evaluator. The degree to which a system or component facilitates the incorporation of changes, once the spirit of the desired change has been determined. sidestep 2 special developer related quality attributes from Boehms model 3. 1. 3 ADDITIONAL ATTRIBUTES FROM ISO 9126 avocation are sub-attributes taken from the ISO 9126 definitions.Selected Attribute Analyzability ISO Definition24 The energy 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 capableness of the software product to enable a specify adaption to be implemented. The readiness of the software product to avoid upset(prenominal) do from modifications of the software. The skill of the software product to be adapted for different contract 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 in strung-out software in a common environment sharing common resources. changeableness Stability Adaptability Installability Co-existence Replaceability The capability of the softwa re product to be utilize 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 following for the reliable study. 1. correctness 2. Testableness 3. changeability 4. Stability 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 implementation23. McCall attributes correctness through16 Traceability Completeness conformity by traceability, it makes possible to know the relationships of each module or component and thereby higher(prenominal) confidence states correctness. Completeness assures th at there are no parts left in terms in executing a function of a system or a procedure thereby cytosine% completeness ratio guarantees correctness. Inconsistent systems or functions will lead to higher error prospect therefore it is a part of correctness. Through the initial discussions with some make out personnel, it was revealed that these characteristics are equally hard to reach to achieve Correctness. . 1. 4. 2 TESTABILITY SEI defines testability 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 pay been met23. Both McCall and Boehm have attributed testability to quality assertion on following characteristics16, 18 Simplicity instrumentation Self-descriptiveness Modularity and structuredness answerableness Accessibility Communicativeness. Simplicity of applications will make easier in testing comparatively to daedal applications.Instrumentation makes possibl e to put probes in the system in order to generalise test information. Self-descriptive systems have inbuilt help or system documentation which will be sufficient to understand the system by going through. Modularity helps in isolate system tests which structuredness mentions 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 publish 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 character istic definitions. However changeability could be achieved through Aiming innocent solution rather than tangled systems as by nature simple applications are easier to change. Low coupling of idiosyncratic modules of a system as raze interactions make easier to change individual components. blueprint the systems change in mind from the start out bandage keeping application evolution. 3. 1. 4. 4 STABILITY ISO defines stability as The capability of the software product to avoid unpredicted set up from modifications of the software24. Therefore stability in this context does not denote the ability of the system to show stable behavior 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 great risk of instability. 3. 1. 4. 5 INS TALLABILITY 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 installment process. The target environment in this case will have to be known at the development time.Installability is metrical 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 decide the study to following variables, after interviewing primal quality assurance personnel in target organizations. ground on their arguments, on applicability to offshore organizations, the best desirable variables have been selected for the study. Dependent multivariate persuasiveness of Software Quality Assurance freelancer variable stars . 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 unaffiliated Variables Figure 6 Schematic diagram for abstract 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 self-directed variable separately, hypotheses also have been formulated respectively to each supreme variable. H01 there is no relationship among the Correctness of software developed and released to QA team), on the military posture of software quality assurance approach. HA1 the greater the Correctness of software developed and de livered to QA team, the higher the effectualness of software quality assurance approach.H02 there is no relationship between the Testability of software developed and released to QA team, on the force of software quality assurance approach. HA2 the greater the Testability of software developed and delivered to QA team, the higher the potency of software quality assurance approach. H03 there is no relationship between the Changeability of software developed and released to QA team, on the dominance of software quality assurance approach. HA3 the greater the Changeability of software developed and delivered to QA team, the higher the potency 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. query DESIGN Research design will outline the roadmap of achieving the research objectives thorough the identified variables and theoretical framework. Details of study conception of the study Type of investigation result of researcher interface Minimal study events as they normally occur and defining a framework Study reach Measurement Measurement and measures Effectiveness of Software Quality Assurance in emerge Offshore Development Enterprises in Sri Lanka descriptive quality evaluation framework possibleness testing to validate the evaluation framework correlation study of correlations to effectiveness against evaluation factors nocontrived study in real busin ess environment Quality factors and their applicability through quality matrices and Likert scales selective information compend 1. Classification of selective information 2. trade good of data Unit of analysis sampling design Time horizon info collection method 3. Hypotheses testing Individuals based on job categories in Offshoring organizations faultfinding(prenominal) sampling of individual in the inbuilt population of offshore enterprises Crosssectional Interviews, caputnaires, Observations Figure 7 The research design 4. 1 typesetters case 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 entropy battle array METHODS Since the study is on offshore software development organizations, it has been decided to collect data from all registered companies in Software Exporters intimacy Sri Lanka and seven other offshore software development organizations in S ri 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 DESIGN A structured questionnaire was used to gather responses apart from the preliminary interviews. The questionnaire is divided in to four main sections. element one has eleven questions, capturing organizational demographics of the responder. department 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 superfluous information for the conceptual framework. RESULTS OF DATA synopsis rejoinders received had been categorized to qualitative data and quantitative data. Qualitative data had been used to under stand the responders and company background. Quantitative responses, where the scale data is measured have been assigned gain ground as per following table for statistical analysis. Response Selected Strongly disagree Disagree indifferent Agree Strongly agree bulls eye Assigned 1 2 3 4 5 Table 5 Rates given for questionnaire responses Each response was individually assessed to ensure data validness and integrity.Incomplete responses have been followed up with the responder with functional contact information and have been able to complete in many instances. For the whitened responses, score three was assigned in case the question is not applicable to the responders organization. by-line thickset 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 hamper / Unusable 2 Number of reasoned Responses 37Table 6 Statistics of questionnaire distribution responses received 5. 1 PILOT STUDY To test the aboriginal data a pilot study was run among fourteen Quality Assurance Engineers at an offshore software development organization, using a lottery questionnaire. On the scale of reliability in order to treat results with credibility25 and the internal harmony of the draft questionnaire, was checked 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 suitable for collecting the data for the main study. Details of Cronbachs alpha are discussed under Analysis of Reliability Section, below. 5. 2 PRELIMINARY digest All xxx seven organizations selected as valid responses are exporting software. 89. 19% of the selected organizations are topically own while 10. 81% of organizations which are in Sri Lankan operatio n 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 accept client 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 Operation Figure 8 Analysis of organizations against number of years 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 deliberate 15 10 5 0 Non IT tweak IT/Comp. Science Post graduate Graduat e Deploma MSc/MBA/Post Graduate Degree Other Education take aim 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% brusk Early 9. 09% On Time 24. 24% Too Delayed 3. 64% microscopic Delayed Figure 10 expulsion completion against estimates Responders were asked to select a absolute 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, legal age have been completed with a unretentive delay from the estimates. plastered and the variance are calculated for each question under each nonparasitic variable and the dependent variable through the assigned scores as per Table 5.Question No. Question repute 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/ figure 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 deal 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 Systems or components we deliver, endlessly met specifications Uniformity of functionality/operations/ pilotage of the designed system always contributed to high quality System retained 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 time- well-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 hail-fellow-well-met Our applications are decomposed in to manageable modules in implementation in a virtual(a) manner Consistent 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. 3 12 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 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 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 through with(p) to one module, our systems have very few side effects to other modules Our QA team measures put much emphasis to test change ability 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 Means and variances of questions relative frequency distributions of responses to each of above questions have been presented in Appendix 2. 5. 3 SECONDARY RESULTS ANALYSIS Primary data is further canvass to derive more meaningful results.For statistical analysis, the ratings gathered through individual questions were summed up to derive scores for individual unconditional variables. Variable = sum of marks for relevant questions I. e. Correctness = Q30 + Q31 + Q32 + Q33 + Q34 + Q35 + Q36 Sample Mean, where, n = sample size, and = scores Sample Variance, Standard 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 grassroots statistics of independent variables and the dependent variable Following is the in writing(p) illustration of above statistics. 4. d 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 system at the second position. Installability was rated as of to the lowest degree significant to the QA Effectiveness in the subject domain. 5. 3. 1 ANALYS IS 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 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 gratifying for the research. 5. 4 HYPOTHESES TESTING Analysis had been done to test each set of speculation 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 H1Co rrectness 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 possibleness is supported by the data analysis (Sig. value was . 000, p