Вы находитесь на странице: 1из 8

SESSION 10 Question: 1.Write about the SQA encompasses?

Answer: SQA encompasses: (1) a quality management approach (2) effective software engineering technology (3) formal technical reviews (4) a multi-tiered testing strategy (5) document change control (6) software development standard and its control procedure (7) measurement and reporting mechanism Question: 2.What are all the types of quality control? Answer: Quality design -> the characteristics that designers specify for an item. --> includes: requirements, specifications, and the design of the system. Quality of conformance -> the degree to which the design specification are followed. It focuses on implementation based on the design. Question: 3.What is quality control? Answer: The series of inspections, reviews, and test used throughout the develop cycle of a software product SESSION 11 Question: 1. Define SQA? Answer: It is defined as a planned and systematic approach to the evaluation of the quality and adherence to software product standards,processes and procedures. Question: 2.Write about the SQA groups tasks? Answer: - Prepare a SQA plan for a project - Participate in the development of the projects software process description - Review engineering activities to verify compliance with the defined process - Audits designated software work products to verify compliance the defined process - Ensure the deviations in software work and products according to a documented procedure - Records any noncompliance and reports to senior management Question: 3.What is software reviews?Why software reviews?

Answer: software reviews- a filter for the software engineering process. Purpose: serves to uncover errors in analysis, design, coding, and testing. Why software reviews? - To err is human - Easy to catch the errors in engineers work SESSION 12 Question: 1.When Should QA testing start in a project and why? Answer: QA is involved in the project from the beginning.This helps the teams communicate and understand the problems ana concerns, also gives time to setup the testing environment and configuration. On the other hand, actual testing starts after the test plans are written,reviewed and approved based on the design documentation. Question: 2.Define Quality of conformance? Answer: Degree to which design specifications are followed in manufacturing the product Question: 3.Define Quality Costs and their types? Answer: Prevention costs - quality planning, formal technical reviews, test equipment, training Appraisal costs - in-process and inter-process inspection, equipment calibration and maintenance, testing Failure costs - rework, repair, failure mode analysis External failure costs - complaint resolution, product return and replacement, help line support, warranty work SESSION 13 Question: 1.Explain SQA Costs and Benefits? Answer: Software Quality Assurance has been developed for years and it has been proven to be useful for some situations. We have to emphasize the word some since there are companies who have disputed the idea of SQA with so many reasons.

Taking a look at the reasons, it all goes down to the idea of getting your moneys worth. Companies have to work with SQA may have found the benefits against its costs. On the other hand, there are companies that have completely ignored the idea of SQA exactly because of its costs. The effort and tools that will be employed in SQA may only affirm what the developers have done in their testing stage. In this article we take a look at the benefits of an SQA. Every business who wants to have a highly efficient application or any software company that wants to offer a good application has to use an SQA program. But just like any businesses, they have to ensure that any business movement will be beneficial. The idea of employing SQA is no different. The cost of an SQA could be too much that the price could easily outweigh its benefits. Every company has to ensure that employing SQA in their software development will be beneficial and will work at their advantage. The Other Side of SQA The ideal scenario of implementing SQA is that the cost should have a direct effect on the softwares quality. The higher the cost of using SQA, the better the software should perform. There are tools in SQA that are known to be pricey and but it comes with a higher chance of providing better and complete metrics regarding the application. The manpower used in this department will also have to receive financial compensation so it should also be considered. Again, the more experienced the company the higher will their cost be. That should be considered when the application is expected to have more than usual errors. On the other hand, the company can also think twice of using SQA when they know the application is properly rendered. It is a gamble that everyone could employ if they know their application works well. SQA can also be disregarded when a testing tool is used by developers to gauge every line of the application. Question: 2.What is software quality assurance? Answer: Business software is never built overnight. It takes a lot of planning, consultation and testing to be able to come up with an initial version of the application. If a business hurries up the development of a certain application, they would end up spending more in addressing the problem the application brought than they have earned. Question:

3.Why SQA?
Answer: There are so many reasons why a company should consider SQA. It is all about business survival and SQA is just one of the many tools the company should effectively use. And just like a tool, it has to be effectively used to its maximum. If the tool is not used to its full

extent, the tool will just be a financial burden to the company. SQA should also be utilized at the same way to its full extent. One of the reasons why businesses and companies opt out in using SQA is their inability to realize who effective an SQA when properly used SESSION 14 Question: 1.What are the steps implied by statistical quality assurance? Answer: 1. Information about s/w defects, 2. An attempt is made to trace each defect to its underlying cause, 3. Using the pareto principle, 4. Move to correct the problems that have caused the defects. Question: 2.Define Verification and Validation. Answer: Verification refers to the set of activities that ensure that s/w correctly implements a specific function. Validation refers to a different set of activities that ensure that the s/w that has been built is traceable to customer requirements. Question: 3.What is SQA group? Answer: SQA group consists of many different constituencies like software engineers, project managers, customers, salespeople and the individuals which are having software quality assurance responsibility. SESSION 15 Question: 1.What are all the different types of Software implementation? Answer: Different Types of SQA implementations are: Requirements Phase Design and Implementation Phase Software Testing Phase Integration and Maintenance Phase Question: 2.Write a short notes for Requirements Phase? Answer: The SQA team has to ensure that the User Requirements will be addressed and should be traced. When traceable, the SQA should be able to logically gauge if the User

Requirements has been address or not. Aside from being logical, the software requirement proposed should be verifiable. In this phase, testing the proposed SR is encouraged. The SQA team could even use CASE tools so that it could easily prove the functionalitys worthiness in answering the User Requirements. CASE tools could quicken the verification of the functionality although monetary concerns should be considered. Question: 3. Write a short notes for Software Testing Phase? Answer: The developers will now test their application. Using cases, the development team should be able to show how the application will tackle certain commands and functions. On the other hand, the SQA team should be able to use some of their tools to ensure the metrics in terms of processing speed is achieved. Using popular tools, the developers should also test the softwares ability to handle stress efficiently. In this phase of the software development, the developers of the application are given enough time to redevelop the application. Most of the time, the SQA team will also receive feedback from the developers if they want to defend the efficiency of the application. SESSION 16 Question: 1.What are all the Essential software documentation involved in the SQA? Answer: 1.Software Requirements 2.Analysis Documentation that captures semantics of the system function points as viewed through scenarios 3.Architectural and implementation documentation that communicates the vision and details of the architecture to the development team. 4.Design Documentation 5.Design and Implementation documentation 6. Source code Documentation 7.Technical Documentation 8.Test Documentation 9.Installation and checkout Documentation 10.Operation and Maintenance Documentation 11.Project Management Documentation 12.Marketing Documentation 13. User Documentation Question: 2.Define:Software configuration management Answer: The traditional software configuration management (SCM) process is looked upon by practitioners as the best solution to handling changes in software projects. It identifies the functional and physical attributes of software at various points in time, and performs

systematic control of changes to the identified attributes for the purpose of maintaining software integrity and traceability throughout the software development life cycle. The SCM process further defines the need to trace changes, and the ability to verify that the final delivered software has all of the planned enhancements that are supposed to be included in the release. It identifies four procedures that must be defined for each software project to ensure that a sound SCM process is implemented. They are: 1. 2. 3. 4. Configuration identification Configuration control Configuration status accounting Configuration audits

Question: 3. Software Requirements Specification-Define Answer: A Software Requirements Specification (SRS) a requirements specification for a software system is a complete description of the behavior of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. In addition to use cases, the SRS also contains non-functional requirements. Nonfunctional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). SESSION 17 Question: 1.What are the documentation in the Review Process? Answer:

Test Plans Test Specifications Test Procedures Test Reports

Question: 2. What is Software Review? Answer: A process or meeting during which a software product is project persoonel, managers, users,customers, user representatives or other intersted parties for comment or approval Question: 3.What are Walk Through Reviews? Answer: It is a form of peer review where the author leads members of the developments team and other interested parties through a software product and their participants ask questions and make comments about defects. SESSION 18

Question: 1.Who is an Author? Answer: The Author, who represents the software product in step-by-step manner at the walkthrough meeting, and its probably responsible for completing most action items. Question: 2.What are the types of audits? Answer:

Financial Audits Quality Audits Integrated Audits

Question: 3.What are the phases of Audits? Answer: SQA Audit has Four Phases:

Planning and preparation The site visit Reporting Follow-UP

PART-B 1. Explain in detail the Quality tasks and responsibilities. (12) 2. Explain in detail about the Documentation. (12) 3. Explain the Procedural description template and Action items (12) 4. Explain in detail the CMM Compatibility of Reviews and audits. (12) 5. Explain the management review process. (12) 6. Explain the technical review process. (12) 7. Explain the types of reviews. (12) 8. Explain the software inspection process. (12) 9. a) Explain walkthrough process. (6) b) Explain the Audit process. (6) 10. a) Explain the Document verification and validation. (6) b) Explain the factors affecting the SQA effort. (6)

Unit-II SOFTWARE QUALITY ASSURANCE Part-A (2 Marks) 1. What are Quality tasks? 2. What is SQA Plan? 3. Define Software quality Assurance (SQA). 4. List out the Teams and Responsibilities. 5. What makes the QA work minimal? 6. What are the factors affecting the SQA effort? 7. List out the seven keys to Leadership. 8. What are the ways of killing the Quality Assurance? 9. What are the Characteristics of Software quality assurance ? 10. List out the elements of Documentation. 11. What is SRS? 12. What is SDD? 13. What are the steps in Document Distribution? 14. Draw the Documents Documentation plan worksheet. 15. Give the Reviewing description template. 16. What are action Items? 17. List out the special responsibilities of Technical Review Process. 18. What is software inspection? 19. What is walkthrough? 20. What is audit process? 21. Write short notes on Document verification. Part-B 1. Explain in detail the Quality tasks and responsibilities. (16) 2. Explain in detail about the Documentation. (16) 3. Explain the Procedural description template and Action items (16) 4. Explain in detail the CMM Compatibility of Reviews and audits. (16) 5. Explain the management review process. (16) 6. Explain the technical review process. (16) 7. Explain the types of reviews. (16) 8. Explain the software inspection process. (16) 9. a) Explain walkthrough process . (8) b) Explain the Audit process. (8) 10. a) Explain the Document verification and validation. (8) b) Explain the factors affecting the SQA effort. (8)

Вам также может понравиться