Quality Assurance Question Bank

head bank Q1. Why softw ar needs to be goatvased? Ans. every(prenominal) softw be harvest-home needs to be push throughpouringed since the increment answer is un up to(p) to produce faulting free computer softw ar package mathematical product. Even if the reading fulfill is able to produce shortcoming free softw ar package, we pull up stakes not be able to know unless(prenominal) & until we screen out it. Without examination it, we sh each(prenominal) not be having regainmly confidence that it will work. experiment not only identifies and reports defect besides withal measures the forest of the product, which wait ons to decide whether to release the product, or not. Q2.What is the rationality that bundle has Bugs? Ans. Following factors contri entirelye to the presence of hemipterous insects in the softw be product lotions- a. softw ar package constitution emergence barbs kindred visual joyrides, class libraries, compilers, scripting tools, et c. usu onlyy show their decl atomic number 18 rides in the system. b. To err is human. Likewise computer programmemers do drag mistakes turn program c. In fast-changing business environments infinitely modified requirements are decent a fact of demeanor. Such frequent change overs requested by the client leads to errors in the wraping already nearing completion.Last minute object changes leads to m whatsoever(prenominal) funny ho part like re pattern of the full-page system, rescheduling of engineers, scrapping of the work already completed, fresh requirements of congruous gravelyware etc d. A quickly written only poorly put down decree is stand out to require bugs. It be summates difficult to respect and qualify much(prenominal) work out that is badly written or poorly enter. its tough to maintain and modify rule that is badly written or poorly catalogueed the leave al iodin is bugs. In many system of ruless focusing provides no incentive for pr ogrammers to document their economy or write clear, beneathstandable, maintainable legislation.In fact, its usu entirelyy the adversary they grab points intimatelyly for quickly turning out work out, and there as jobs security measures if nobody else commode understand it (if it was hard to write, it should be hard to read). e. When out-of-doorise deadlines come too closing curtain & time pressures come, mistakes are bound to come Q3. What is the residual among QA and interrogatory? Ans. QA stands for eccentric potency, and chargees on cake of defects in the product being sustained. It is associated with the execute and activities relate to to the Process Improvement. lineament Assurance measures the quality of the buttes employed to urinate a quality product. Whereas examen refers to gauge Control, and focuses on Detection of faulting and removal there aft(prenominal). Or timberland Control measures the quality of a product. Q4. What is the contravent ion amid parcel examen and Debugging? Ans. mental examing is the suffice of locating or identifying the errors or bugs in a packet system. Whereas Debugging is the cognitive fulfill of Fixing the identified Bugs. It involves a mathematical operation of analyzing and rectifying the phrase structure errors, logic errors and whole different attributes of errors identified during the cognitive carry through of examen.Q5. What is the disagreement amid a Bug and a Defect? Ans. Bug is a fuss or an error in the computer bundle program computer inscribe, which is found in the application during interrogatory. Bug is responsible for failure of the application to comply with the craved specifications. Whereas Defect is paradox reported by the guest during usage of the bundle application. Q6. What is the distinction between a Bug and an enhancement? Ans. Bug is a problem or an error in the computer bundle package program code, which is found in the applica tion during studying.Bug is responsible for failure of the application to comply with the want specifications. Whereas Enhancement is the additive feature or functionality found and added to the application as desired by the end exploiter / real word node or quizzer during the scrutiny process. Q7. What is the difference between Requirements & Specifications? Ans. Requirements are statements go badn by the customer as to what needs to be achieved by the software system. posterior on these requirements are converted into specifications which are nothing but feasible or implementable requirements.Whereas Specifications are feasible requirements derived from disparate statements given by the customer. These are the starting point for the product ripening aggroup. Q8. What is the difference between check-out procedure and cogent evidence? Ans. check-out procedure involves reviews and contacts to evaluate documents, fancys, code, requirements, and specifications to p atronise whether items, processes, services, or documents con manikin to contract requirements or not. This flock be make with the helper of checklists, issues lists, walkthroughs, and reappraisal oppositions. The heading f handicap is to determine whether the products of a given phase of the software culture beat fulfill the requirements established during the previous phase or not. Whereas ecesis is the determination of the correctness of the final program or software product produced from a articulatement view with respect to the user needs and requirements. This involves certain exam of the product and takes regulate after(prenominal) baulks are completed. bundle verification raises the question, Are we building the Product Right? that is, does the software conform to its specification. bundle Validation raises the question, Are we building the Right Product? that is, the software doing what the user really requires. Q9. What is difference between Waterfa ll present and V Model? Ans. Waterfall Model Is a straight software instruction stick (a process for the creation of software) in which developing is seen as satiny steadily downwards (like a waterfall)through the phases of requirements analysis, design, implementation, mental hearing ( ecesis),integration, and maintenance. To follow the waterfall mock up, we decease from unity phase to the neighboring in a purely sequential manner.In handed-down waterfall illustration, testing comes at the far end of the tuition process. Whereas V Model or liveliness circle Testing involves carrying out verification of consistency, completeness and correctness of software at every stage of the victimization spiritedness cycle. It aims at catching the defects as early as executable and thus reduces the bell of fixing them. It involves continuously testing the system during all stages of the suppuration process quite a than scarcely limiting testing to the defy stage. Q10. What are baseline Documents? Ans.Baseline documents are the documents, which cod been O.K. by the customer and will not eat up any more(prenominal)(prenominal) changes. Baseline Documents cover all the details of the drop and thrust undergone walkthrough process. Once a document is Base-lined it cannot be changed unless there is a change request duly approved by the customer. Service Level Agreement (SLA) & Business Requirement Documents (BRD) are the examples of Baseline Documents. Q11. What is Defect Density? Ans. Defect Density Is a software mensurable furbish upd as meat way out of defects per LOC (lines of code).Alternatively it can be Total number of defects per Size of the fox. Here the measure of Size of the Project can be number of Function Points, Number of Feature Points, number of substance abuse Cases or KLOC (Kilo Lines of Code) etc. Q12. What is Quality? Ans. Quality software is software that is passably bug-free, devolveed on time and within bud thr um, tallys requirements and expectations and is maintainable. However, quality is a private term. Quality depends on who the customer is and their overall influence in the intention of things.Customers of a software increase throw off let in end-users, customer borrowing test engineers, testers, customer contract officers, customer instruction, the development ecesiss management, test engineers, testers, sales plurality, software engineers, stockh senescenters and accountants. Each type of customer will have his or her own slant on quality. The accounting department baron arrange quality in terms of profits, while an end- user aptitude define quality as user friendly and bug free. Q13. What is an charge? Ans.An recapitulation is a formal meeting, more formalized than a walkthrough and typically consists of 3-10 stack including a moderator, reader (the author of whatever is being reviewed) and a recording machine (to make notes in the document). The subject of the c ritique is typically a document, much(prenominal) as a requirements document or a test project. The use of an inspection is to find problems and see what is missing, not to fix anything. The top of the meeting is documented in a written report. Attendees should prepare for this type of meeting by reading through the document, before the meeting starts near problems are found during this preparation.Preparation for inspections is difficult, but is one of the most cost-effective methods of ensuring quality, since bug taproom is more cost effective than bug detection. A14. What is sise Sigma? Ans. Six Sigma mover Six Standard Deviations from the mean. It is a methodology aimed to reduce defect levels beneath 3. 4 Defects Per one Million Opportunities. Six Sigma nuzzle improves the process functioning, decreases conversion and maintains consistent quality of the process output. This leads to defect reduction and avail in profits, product quality and customer satisf fulfil.Q 15. What is difference between CMM and CMMI? Ans. CMM manner talent adulthood Model developed by the parcel plan make (SEI). It is a process capability adulthood model, which aids in the commentary and understanding of an organizations processes. CMM is mean as a tool for objectively mensurateing the ability of government contractors processes to perform a promise software project. Whereas CMMI means content Maturity Model Integration & it has superseded CMM. The old CMM has been renamed to package Engineering CMM (SE-CMM).Q16. What is Verification? Ans. Verification ticks the product is designed to ransom all functionality to the customer it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications this can be do with checklists, issues lists, walkthroughs and inspection meetings. Q17. What is Validation? Ans. Validation ensures that functionality, as defined in requirements, is the intended air of the product valid ation typically involves actual testing and takes place after verifications are completed. Q18.What is a Test pattern? Ans. A software project test plan is a document that describes the objectives, scope, approach and focus of a software testing driving. The process of preparing a test plan is a useful way to think through the efforts needed to underpin the acceptableness of a software product. The completed document will help people outside the test group understand the why and how of product validation. It should be everlasting(a) enough to be useful, but not so thorough that none outside the test group will be able to read it. Q19. What is a Walkthrough? Ans.A walkthrough is an informal meeting for evaluation or informational purposes. A walkthrough is also a process at an abstract level. Its the process of inspecting software code by following paths through the code (as placed by input conditions and choices make along the way). The purpose of code walkthroughs is to ensur e the code fits the purpose. Walkthroughs also offer opportunities to assess an individuals or teams competency. Q20. What is software system Life Cycle? Ans. Software life cycle begins when a software product is first conceived and ends when it is no extended in use.It accommodates phases like initial concept, requirements analysis, functional design, cozy design, reenforcement planning, test planning, coding, document preparation, integration, testing, maintenance, updates, re-testing and phase-ou Q21. What is the contrast between STLC & SDLC? Ans. STLC means Software Testing Life Cycle. It starts with activities like 1) Preparation of Requirements Document 2) Preparation of Test Plan 3) Preparation of Test Cases 4) Execution of Test Cases 5) synopsis of Bugs 6) coverage of Bugs 7) tracking of Bugs till closure.Whereas SDLC means Software Development Life Cycle is a software development process, used by a systems psychoanalyst to develop an information system. It start s with activities like 1) Project Initiation 2) Requirement collect and Documenting 3) designing 4) Coding and Unit Testing 5) Integration Testing 6) administration Testing 7) Installation and Acceptance Testing 8) Support or criminal maintenance Q22. What is the Difference between Project and Product Testing? Ans. If any organization is evolution the application according to the client specification then it is called as project.Accordingly its testing is cognise as Project Testing Whereas If any organization is ontogenesis the application and trade it is called as product. Hence its testing is known as Product Testing Q23. How do you introduce a reinvigorated software QA process? Ans. It depends on the size of the organization and the fortunes involved. For large organizations with high- encounter projects, a serious management buy-in is required and a formalized QA process is indispensable. For metier size organizations with lower peril projects, management and organi zational buy-in and a slower, gradually process is required.Generally speaking, QA processes should be balanced with productivity, in order to take hold any bureaucracy from getting out of hand. For lesserer groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, feedback to developers and good communicating is all- serious(a) among customers, managers, developers, test engineers and testers. Regardless the size of the community, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, complete and testable. Q24. What is configuration circumspection? Ans.Configuration heed (or CM) is the processes of controlling, coordinating and tracking the Standards and procedures for managing changes in an evolving software product. Configuration Testing is the process of checking the operation of the software being tested on various types of hardware. Q25. What is the character of QA i n a software producing guild? Ans. QA is responsible for managing, implementing, maintaining and continuously better the Processes in the Company and enable internal projects towards process maturity and ease process improvements and innovations in the organization.Tester is responsible for carrying out the testing efforts in the company. In many companies QA person is responsible two the economic consumptions of Testing as salubrious as creating and improving the processes. Q26. What is ill fortune Mode and Effect Analysis (FMEA)? Ans. Failure Mode and Effect Analysis is a systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence. Q27. What is Test Maturity Model or TMM? Ans.Test Maturity Model or TMM is a phoebe bird level staged framework for test process improvement, related to the Capability Maturity Model (CMM) that describes the keystone elements of an effective test process. Q28. What is the difference between API & ABI? Ans. industriousness Programming Interface (API) is a formalized fasten of software calls and routines that can be referenced by an application program in order to access supporting system or ne twainrk services. Whereas Application Binary Interface (ABI) is a specification defining requirements for portability of applications in binary program forms across opposite system platforms and environments.Q29. What is I V & V? Ans. I V & V means Independent Verification and Validation. Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. Verification can be done with the help of checklists, issues lists, walkthroughs, and inspection meetings. Whereas Validation typically involves actual testing and takes place after verifications are completed. Q30. What are the benefits of Software Validation? Ans. Software validation is an important tool employed to assure the quality of the so ftware products.Few benefits are as under 1) It increases the usability and reliability of the device software, resulting in reduced failure rates, less recalls and disciplinal actions, less liability to device manufacturers. 2) It reduces the long term cost by making it easier and less costly to reliably modify software and revalidate software changes. 3) It helps to reduce the long-term cost of software by bring down the cost of validation for each subsequent release of the software. Q31. What is the section of use Reviews in Software Development Life Cycle? Ans.Design review is a chief(a) tool for managing and evaluating software development projects. Design reviews allow management to confirm that all goals defined in the software validation plan have been achieved. Formal design reviews are more structured and include association from others outside the development team. Design reviews are documented, comprehensive, and systematic examinations of a design to evaluate the adequacy of the design requirements, to evaluate the capability of the design to meet these requirements, and to identify problems.Design reviews include examination of development plans, requirements specifications, design specifications, testing plans and procedures, all other documents and activities associated with the project. Q32. What is the need of Software Validation after a change? Ans. When any change even a small one is make to the software, following activities need to be performed 1) Re-establishment of the validation status of the software. 2) Conducting necessary validation analysis not for the sake of validation of the individual change, but o to know the effect of the change on the entire software system. ) Conducting commensurate level of regression testing to show that unchanged but threatened portions of the system have not been adversely touched. Regression testing is meant to provide a confidence that the software has been validated after the change. Q33. How would you exchange speed management that company needs a formal QA testing team? How would you explain that Software quality would not improve if the company get rid of QA team? Ans. Developing amazing applications isnt the said(prenominal) as testing them, ut a experienced QA tester, I would rather have a developers testing application than the testers who can just merely acquaint bug reports.QA team needs to build quality into software development life cycle. The bug in software design is 15times cheaper than a bug in code. QA productivity is really hard to measure. If QA team is doing testing right, , everything just happens smoothly, but if testers mess up even a little, everyone knows to the highest degree it. To be successful, QA team must create test plans, create test harnesses, create test cases and use testing tools. QA should ensure whether the application code is effectively delivering on the business requirements provided.The developers should unit test their own code and deliver perfectly good code , while QA testers should deliver code that real addresses business needs. For a company that make software applications, a rock-solid QA department is absolutely irreplaceable. Q34. WhatQuality Assurance and Quality Control activities are done differently for COTS / GOTS project than for a traditional custom development project? Ans. The activities themselves are broadly the same, but with different stakeholders, and different detail procedures for verification and validation.Often the challenge for SQA is to pin down the ownership of the requirements, which may be stand for by a tangled debate between marketing departments, adept eggheads, user groups, customer focus groups and other interested parties. Q35. What in your thought process is the role of SQA personnel with respect to inspections or testing? Ans. Formally, the role is to make the inspection process or testing process visible, both to the participants (so they can se e what they are achieving, how effective they are being) and to management (so that they can assess progress and risk).In practice, SQA personnel often need to act as facilitators or coaches. They are often regarded (wrongly) as the owners or custodians of the inspection or testing process, or even as the owners/custodians of the whole software process. situation of the reproduction and mentoring for SQA personnel should address the difficult dilemma of how to be adequately employed in the software process without being landed with the tariff for it. Q36. What are the most likely quality publications of choosing an inappropriate life cycle model for a software project? Ans. The most likely consequence is that the project will not deliver anything at all.Not because the lifecycle couldn? t be made to work technically, but because it will fail to contain the policy-making tensions between stakeholders. Q37. What in your printing, are the most important changes that occurre d in the role of Software Quality Assurance during the last 5 to 10 years? Ho Ans. rowing awareness and importance of public humans models much(prenominal) as SEI SW CMM, BOOTSTRAP and SPICE. Changing nature of software development, in particular model-based development (CASE) and component-based development (CBD). Growing need to connect software of different ages and sources.Software projects not pure software development, but including maintenance, package selection and implementation, and other software activities. (Perhaps software projects never were pure development, but such topics as project management, quality management and configuration management used to be taught as if they were. ) Faced with these changes, SQA needs to be both reductionist (giving close concern to the quality of components from various sources) and holistic (giving broad attention to the sudden properties of the whole assembled system, in terms of its overall fit to business requirements).As I s ee it, the mandate of SQA is to make defects in software products and processes visible to management. SQA fits into a context of use of software quality management where this visibility leads to corrective and rub action (not itself part of SQA), and to general software process improvement. Q38. Someone complains that during system testing the application often crashes. What likely process problem does that target? Ans. organized failure to carry out proper unit testing.OR repugnance between the development/unit test environment and the system test environment. AND in like manner management failure to respond promptly to the situation with corrective and antifertility action. Q39. What exposure have you had to auditing? Internal? External? Certification related? Ans. I have been trained as a lead tax assessor for ISO 9000 and also as an examiner for the European Quality Award. I have conducted internal audits and informal external assessments but not formal external aud its. I have advised organizations on steps towards certification. Q40. What in your opinion are the most significant fundamental differences between SEI SW-CMM and ISO 9000-3? Ans. The main difference is what the two models tell you. ISO 9000-3 gives you a yes/no answer, whereas SEI SW-CMM gives you a more complex assessment. This implies different ways of using the models for SQA and process improvement. 1. Difference is ISO is a model and CMMI is a model with framework. 2. Other one is Specific practices should be determinded in ISO and where as CMMI model having predefined useful specific and general practices. Q41. In your experience, who are the most important allies of SQA within an organization? Ans. SQA is a form of risk awareness, and is therefore potentially allied to any senior management with a risk management focus. Within whatsoever companies/industries (e. g. insurance), software risks are seen as having primarily financial consequences, and so the main ally mi ght be the financial director. Within other companies/industries (e. g. retail), software risks are seen as having mainly customer service implications, and so the main allies may be in marketing roles.In one client, we had useful conversations with the Company Secretariat, because of the ascribable persistence implications of some software risks. These conversations were triggered by Y2K issues, but ranged much more widely. In practice, SQA often fails to make these alliances, because it gets bogged down in obscure software technicalities and trivialities, which it is incapable(p) of communicating effectively even to software engineers, let simply anybody else. Q42. A company recruits its first and only SQA specialist. The person is bracing to the area.The company is relatively young, operates in a competitive commercial domain and has no previous SQA presence. The SQA specialist feels he needs to show some results during the next 6 to 9 months. What advice will you give him? Ans. Start with a risk assessment, to identify the significant software risks and their business implications. Identify managers now affected by these implications, who may be recruited as allies. Select a small number of issues to address in the initial phase. Try to include some quick wins, as well as some improvements that could be achieved within 3-6 months.Don? t try to do everything at once. At this stage, use whichever model you prefer (ISO 9000-3 or TickIT or SW-CMM or SPICE) merely as a framework, so that you know how what you? re doing fits into a larger picture. Q43. What advice would you give to person who asked you where to start to introduce to their company a inflection and quality reportage program? Ans. Use the GQM approach to derive relevant poetic rhythm from private and corporate goals. Select a small number of key metrics that will be directly relevant to project managers and/or software engineers.Put the metrics into the hands of the workers, as a tool for personal performance improvement. Q44. What is Total Quality Management? Ans. A company committedness to develop a process that achieves high quality product and customer satisfaction. Q45. What is Quality Circle? Ans. A group of individuals with related interests that meet at level(p) intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality. Quality Assurance Question assertQuestion bank Q1. Why software needs to be tested? Ans. Every software product needs to be tested since the development process is unable to produce defect free software. Even if the development process is able to produce defect free software, we will not be able to know unless & until we test it. Without testing it, we shall not be having enough confidence that it will work. Testing not only identifies and reports defect but also measures the quality of the product, which helps to decide whether to release the product, or not. Q2.What is the reason that Software has Bugs? Ans. Following factors contribute to the presence of bugs in the software applications- a. Software development tools like visual tools, class libraries, compilers, scripting tools, etc. usually introduce their own bugs in the system. b. To err is human. Likewise programmers do make mistakes while programming c. In fast-changing business environments continuously modified requirements are becoming a fact of life. Such frequent changes requested by the customer leads to errors in the application already nearing completion.Last minute design changes leads to many chaos like redesign of the whole system, rescheduling of engineers, scrapping of the work already completed, fresh requirements of compatible hardware etc d. A quickly written but poorly documented code is bound to have bugs. It becomes difficult to maintain and modify such code that is badly written or poorly documented. its tough to maintain and modify code that is badly written or poorly documented the result is bugs. In many organizations management provides no incentive for programmers to document their code or write clear, understandable, maintainable code.In fact, its usually the opposite they get points mostly for quickly turning out code, and there as jobs security if nobody else can understand it (if it was hard to write, it should be hard to read). e. When project deadlines come too close & time pressures come, mistakes are bound to come Q3. What is the difference between QA and Testing? Ans. QA stands for Quality Assurance, and focuses on Prevention of defects in the product being developed. It is associated with the Process and activities related to the Process Improvement.Quality Assurance measures the quality of the processes employed to create a quality product. Whereas Testing refers to Quality Control, and focuses on Detection of Defect and removal thereafter. Or Quality Control measures the quality of a product. Q4. What is the difference between Software Testing and Debugging? Ans. Testing is the process of locating or identifying the errors or bugs in a software system. Whereas Debugging is the process of Fixing the identified Bugs. It involves a process of analyzing and rectifying the syntax errors, logic errors and all other types of errors identified during the process of testing.Q5. What is the difference between a Bug and a Defect? Ans. Bug is a problem or an error in the software code, which is found in the application during Testing. Bug is responsible for failure of the application to comply with the desired specifications. Whereas Defect is problem reported by the customer during usage of the software application. Q6. What is the difference between a Bug and an Enhancement? Ans. Bug is a problem or an error in the software code, which is found in the application during Testing.Bug is responsible for failure of the application to comply with the desired speci fications. Whereas Enhancement is the additional feature or functionality found and added to the application as desired by the end user / real word customer or tester during the testing process. Q7. What is the difference between Requirements & Specifications? Ans. Requirements are statements given by the customer as to what needs to be achieved by the software system. Later on these requirements are converted into specifications which are nothing but feasible or implementable requirements.Whereas Specifications are feasible requirements derived from various statements given by the customer. These are the starting point for the product development team. Q8. What is the difference between Verification and Validation? Ans. Verification involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications to confirm whether items, processes, services, or documents conform to specified requirements or not. This can be done with the help of checklists, issues lists, walkthroughs, and inspection meetings. The purpose f verification is to determine whether the products of a given phase of the software development cycle fulfill the requirements established during the previous phase or not. Whereas Validation is the determination of the correctness of the final program or software product produced from a development project with respect to the user needs and requirements. This involves actual testing of the product and takes place after verifications are completed. Software Verification raises the question, Are we building the Product Right? that is, does the software conform to its specification. Software Validation raises the question, Are we building the Right Product? that is, the software doing what the user really requires. Q9. What is difference between Waterfall Model and V Model? Ans. Waterfall Model Is a sequential software development model (a process for the creation of software) in which development is seen as flowing steadil y downwards (like a waterfall)through the phases of requirements analysis, design, implementation, testing (validation),integration, and maintenance. To follow the waterfall model, we proceed from one phase to the next in a purely sequential manner.In traditional waterfall model, testing comes at the far end of the development process. Whereas V Model or Life Cycle Testing involves carrying out verification of consistency, completeness and correctness of software at every stage of the development life cycle. It aims at catching the defects as early as possible and thus reduces the cost of fixing them. It involves continuously testing the system during all stages of the development process rather than just limiting testing to the last stage. Q10. What are Baseline Documents? Ans.Baseline documents are the documents, which have been approved by the customer and will not have any more changes. Baseline Documents cover all the details of the project and have undergone walkthrough proces s. Once a document is Base-lined it cannot be changed unless there is a change request duly approved by the customer. Service Level Agreement (SLA) & Business Requirement Documents (BRD) are the examples of Baseline Documents. Q11. What is Defect Density? Ans. Defect Density Is a software metric defined as Total number of defects per LOC (lines of code).Alternatively it can be Total number of defects per Size of the Project. Here the measure of Size of the Project can be number of Function Points, Number of Feature Points, number of Use Cases or KLOC (Kilo Lines of Code) etc. Q12. What is Quality? Ans. Quality software is software that is reasonably bug-free, delivered on time and within budget, meets requirements and expectations and is maintainable. However, quality is a subjective term. Quality depends on who the customer is and their overall influence in the scheme of things.Customers of a software development project include end-users, customer acceptance test engineers, tester s, customer contract officers, customer management, the development organizations management, test engineers, testers, salespeople, software engineers, stockholders and accountants. Each type of customer will have his or her own slant on quality. The accounting department might define quality in terms of profits, while an end- user might define quality as user friendly and bug free. Q13. What is an Inspection? Ans.An inspection is a formal meeting, more formalized than a walkthrough and typically consists of 3-10 people including a moderator, reader (the author of whatever is being reviewed) and a recorder (to make notes in the document). The subject of the inspection is typically a document, such as a requirements document or a test plan. The purpose of an inspection is to find problems and see what is missing, not to fix anything. The result of the meeting is documented in a written report. Attendees should prepare for this type of meeting by reading through the document, before t he meeting starts most problems are found during this preparation.Preparation for inspections is difficult, but is one of the most cost-effective methods of ensuring quality, since bug prevention is more cost effective than bug detection. A14. What is Six Sigma? Ans. Six Sigma means Six Standard Deviations from the mean. It is a methodology aimed to reduce defect levels below 3. 4 Defects Per one Million Opportunities. Six Sigma approach improves the process performance, decreases variation and maintains consistent quality of the process output. This leads to defect reduction and improvement in profits, product quality and customer satisfaction.Q15. What is difference between CMM and CMMI? Ans. CMM means Capability Maturity Model developed by the Software Engineering Institute (SEI). It is a process capability maturity model, which aids in the definition and understanding of an organizations processes. CMM is intended as a tool for objectively assessing the ability of government con tractors processes to perform a contracted software project. Whereas CMMI means Capability Maturity Model Integration & it has superseded CMM. The old CMM has been renamed to Software Engineering CMM (SE-CMM).Q16. What is Verification? Ans. Verification ensures the product is designed to deliver all functionality to the customer it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications this can be done with checklists, issues lists, walkthroughs and inspection meetings. Q17. What is Validation? Ans. Validation ensures that functionality, as defined in requirements, is the intended behavior of the product validation typically involves actual testing and takes place after verifications are completed. Q18.What is a Test Plan? Ans. A software project test plan is a document that describes the objectives, scope, approach and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the ef forts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the why and how of product validation. It should be thorough enough to be useful, but not so thorough that none outside the test group will be able to read it. Q19. What is a Walkthrough? Ans.A walkthrough is an informal meeting for evaluation or informational purposes. A walkthrough is also a process at an abstract level. Its the process of inspecting software code by following paths through the code (as determined by input conditions and choices made along the way). The purpose of code walkthroughs is to ensure the code fits the purpose. Walkthroughs also offer opportunities to assess an individuals or teams competency. Q20. What is Software Life Cycle? Ans. Software life cycle begins when a software product is first conceived and ends when it is no longer in use.It includes phases like initial concept, requirements analysis, functional design , internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, re-testing and phase-ou Q21. What is the Difference between STLC & SDLC? Ans. STLC means Software Testing Life Cycle. It starts with activities like 1) Preparation of Requirements Document 2) Preparation of Test Plan 3) Preparation of Test Cases 4) Execution of Test Cases 5) Analysis of Bugs 6) Reporting of Bugs 7) Tracking of Bugs till closure.Whereas SDLC means Software Development Life Cycle is a software development process, used by a systems analyst to develop an information system. It starts with activities like 1) Project Initiation 2) Requirement Gathering and Documenting 3) Designing 4) Coding and Unit Testing 5) Integration Testing 6) System Testing 7) Installation and Acceptance Testing 8) Support or Maintenance Q22. What is the Difference between Project and Product Testing? Ans. If any organization is developing the application accordin g to the client specification then it is called as project.Accordingly its testing is known as Project Testing Whereas If any organization is developing the application and marketing it is called as product. Hence its testing is known as Product Testing Q23. How do you introduce a new software QA process? Ans. It depends on the size of the organization and the risks involved. For large organizations with forged projects, a serious management buy-in is required and a formalized QA process is necessary. For medium size organizations with lower risk projects, management and organizational buy-in and a slower, step-by-step process is required.Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, feedback to developers and good communication is essential among customers, managers, developers, test eng ineers and testers. Regardless the size of the company, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, complete and testable. Q24. What is configuration Management? Ans.Configuration Management (or CM) is the processes of controlling, coordinating and tracking the Standards and procedures for managing changes in an evolving software product. Configuration Testing is the process of checking the operation of the software being tested on various types of hardware. Q25. What is the role of QA in a software producing company? Ans. QA is responsible for managing, implementing, maintaining and continuously improving the Processes in the Company and enable internal projects towards process maturity and facilitate process improvements and innovations in the organization.Tester is responsible for carrying out the testing efforts in the company. In many companies QA person is responsible both the roles of Testing as well as cr eating and improving the processes. Q26. What is Failure Mode and Effect Analysis (FMEA)? Ans. Failure Mode and Effect Analysis is a systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence. Q27. What is Test Maturity Model or TMM? Ans.Test Maturity Model or TMM is a five level staged framework for test process improvement, related to the Capability Maturity Model (CMM) that describes the key elements of an effective test process. Q28. What is the difference between API & ABI? Ans. Application Programming Interface (API) is a formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or mesh topology services. Whereas Application Binary Interface (ABI) is a specification defining requirements for portability of applications in binary forms across different system platforms and environments.Q29. What is I V & V? Ans. I V & V mean s Independent Verification and Validation. Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. Verification can be done with the help of checklists, issues lists, walkthroughs, and inspection meetings. Whereas Validation typically involves actual testing and takes place after verifications are completed. Q30. What are the benefits of Software Validation? Ans. Software validation is an important tool employed to assure the quality of the software products.Few benefits are as under 1) It increases the usability and reliability of the device software, resulting in reduced failure rates, less recalls and corrective actions, less liability to device manufacturers. 2) It reduces the long term costs by making it easier and less costly to reliably modify software and revalidate software changes. 3) It helps to reduce the long-term cost of software by reducing the cost of validation for each subsequent release of the soft ware. Q31. What is the role of Design Reviews in Software Development Life Cycle? Ans.Design review is a primary tool for managing and evaluating software development projects. Design reviews allow management to confirm that all goals defined in the software validation plan have been achieved. Formal design reviews are more structured and include participation from others outside the development team. Design reviews are documented, comprehensive, and systematic examinations of a design to evaluate the adequacy of the design requirements, to evaluate the capability of the design to meet these requirements, and to identify problems.Design reviews include examination of development plans, requirements specifications, design specifications, testing plans and procedures, all other documents and activities associated with the project. Q32. What is the need of Software Validation after a change? Ans. When any change even a small one is made to the software, following activities need to be performed 1) Re-establishment of the validation status of the software. 2) Conducting necessary validation analysis not for the sake of validation of the individual change, but o to know the effect of the change on the entire software system. ) Conducting suitable level of regression testing to show that unchanged but vulnerable portions of the system have not been adversely affected. Regression testing is meant to provide a confidence that the software has been validated after the change. Q33. How would you convince upper management that company needs a formal QA testing team? How would you explain that Software quality would not improve if the company get rid of QA team? Ans. Developing amazing applications isnt the same as testing them, ut a experienced QA tester, I would rather have a developers testing application than the testers who can just plainly submit bug reports.QA team needs to build quality into software development life cycle. The bug in software design is 15times c heaper than a bug in code. QA productivity is really hard to measure. If QA team is doing testing right, , everything just happens smoothly, but if testers mess up even a little, everyone knows about it. To be successful, QA team must create test plans, create test harnesses, create test cases and use testing tools. QA should ensure whether the application code is effectively delivering on the business requirements provided.The developers should unit test their own code and deliver perfectly good code , while QA testers should deliver code that actually addresses business needs. For a company that make software applications, a rock-solid QA department is absolutely irreplaceable. Q34. WhatQuality Assurance and Quality Control activities are done differently for COTS / GOTS project than for a traditional custom development project? Ans. The activities themselves are broadly the same, but with different stakeholders, and different detailed procedures for verification and validation.O ften the challenge for SQA is to pin down the ownership of the requirements, which may be represented by a complex debate between marketing departments, technical eggheads, user groups, customer focus groups and other interested parties. Q35. What in your opinion is the role of SQA personnel with respect to inspections or testing? Ans. Formally, the role is to make the inspection process or testing process visible, both to the participants (so they can see what they are achieving, how effective they are being) and to management (so that they can assess progress and risk).In practice, SQA personnel often need to act as facilitators or coaches. They are often regarded (wrongly) as the owners or custodians of the inspection or testing process, or even as the owners/custodians of the whole software process. Part of the training and mentoring for SQA personnel should address the difficult dilemma of how to be adequately engaged in the software process without being landed with the res ponsibility for it. Q36. What are the most likely quality consequences of choosing an inappropriate life cycle model for a software project? Ans. The most likely consequence is that the project will not deliver anything at all.Not because the lifecycle couldn? t be made to work technically, but because it will fail to contain the political tensions between stakeholders. Q37. What in your opinion, are the most important changes that occurred in the role of Software Quality Assurance during the last 5 to 10 years? Ho Ans. rowing awareness and importance of public domain models such as SEI SW CMM, BOOTSTRAP and SPICE. Changing nature of software development, especially model-based development (CASE) and component-based development (CBD). Growing need to connect software of different ages and sources.Software projects not pure software development, but including maintenance, package selection and implementation, and other software activities. (Perhaps software projects never were p ure development, but such topics as project management, quality management and configuration management used to be taught as if they were. ) Faced with these changes, SQA needs to be both reductionist (giving close attention to the quality of components from various sources) and holistic (giving broad attention to the emergent properties of the whole assembled system, in terms of its overall fit to business requirements).As I see it, the mandate of SQA is to make defects in software products and processes visible to management. SQA fits into a context of software quality management where this visibility leads to corrective and preventative action (not itself part of SQA), and to general software process improvement. Q38. Someone complains that during system testing the application often crashes. What likely process problem does that indicate? Ans. Systematic failure to carry out proper unit testing.OR inconsistency between the development/unit test environment and the system test environment. AND ALSO management failure to respond promptly to the situation with corrective and preventative action. Q39. What exposure have you had to auditing? Internal? External? Certification related? Ans. I have been trained as a lead assessor for ISO 9000 and also as an examiner for the European Quality Award. I have conducted internal audits and informal external assessments but not formal external audits. I have advised organizations on steps towards certification. Q40. What in your opinion are the most significant fundamental differences between SEI SW-CMM and ISO 9000-3? Ans. The main difference is what the two models tell you. ISO 9000-3 gives you a yes/no answer, whereas SEI SW-CMM gives you a more complex assessment. This implies different ways of using the models for SQA and process improvement. 1. Difference is ISO is a standard and CMMI is a model with framework. 2. Other one is Specific practices should be determinded in ISO and where as CMMI model having pr edefined useful specific and general practices. Q41. In your experience, who are the most important allies of SQA within an organization? Ans. SQA is a form of risk awareness, and is therefore potentially allied to any senior management with a risk management focus. Within some companies/industries (e. g. insurance), software risks are seen as having mainly financial consequences, and so the main ally might be the financial director. Within other companies/industries (e. g. retail), software risks are seen as having mainly customer service implications, and so the main allies may be in marketing roles.In one client, we had useful conversations with the Company Secretariat, because of the due diligence implications of some software risks. These conversations were triggered by Y2K issues, but ranged much more widely. In practice, SQA often fails to make these alliances, because it gets bogged down in obscure software technicalities and trivialities, which it is incapable of communic ating effectively even to software engineers, let alone anybody else. Q42. A company recruits its first and only SQA specialist. The person is new to the area.The company is relatively young, operates in a competitive commercial domain and has no previous SQA presence. The SQA specialist feels he needs to show some results during the next 6 to 9 months. What advice will you give him? Ans. Start with a risk assessment, to identify the significant software risks and their business implications. Identify managers directly affected by these implications, who may be recruited as allies. Select a small number of issues to address in the initial phase. Try to include some quick wins, as well as some improvements that could be achieved within 3-6 months.Don? t try to do everything at once. At this stage, use whichever model you prefer (ISO 9000-3 or TickIT or SW-CMM or SPICE) merely as a framework, so that you know how what you? re doing fits into a larger picture. Q43. What advice would you give to someone who asked you where to start to introduce to their company a metrics and quality reporting program? Ans. Use the GQM approach to derive relevant metrics from personal and corporate goals. Select a small number of key metrics that will be directly relevant to project managers and/or software engineers.Put the metrics into the hands of the workers, as a tool for personal performance improvement. Q44. What is Total Quality Management? Ans. A company commitment to develop a process that achieves high quality product and customer satisfaction. Q45. What is Quality Circle? Ans. A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.