1. 1 تضمين کيفيت در نرم افزار تضمين کيفيت در نرم افزار پژمان صالحی ارديبهشت 1386

2. 2 کيفيت در فرهنگ لغات کيفيت دارای تعبير زير می باشد در فرهنگ لغات کيفيت دارای تعبير زير می باشد ”ويژگی ها و يا مشخصات يک چيز“ ”ويژگی ها و يا مشخصات يک چيز“ در مورد نرم افزار 2 نوع کيفيت مطرح می باشد: در مورد نرم افزار 2 نوع کيفيت مطرح می باشد: کيفيت طراحی که شامل نيازمنديها، توصيفات ، و طراحی سيستم می باشد. کيفيت طراحی که شامل نيازمنديها، توصيفات ، و طراحی سيستم می باشد. کيفيت همنوايي که بيشتر بر پياده سازی تاکيد دارد. کيفيت همنوايي که بيشتر بر پياده سازی تاکيد دارد. رضايت مشتری = توليد محصول + کيفيت بالا + تحويل طبق برنامه با بودجه پيش بينی شده رضايت مشتری = توليد محصول + کيفيت بالا + تحويل طبق برنامه با بودجه پيش بينی شده

3. 3 کيفيت نرم افزار کيفيت نرم افزار شامل کارکردهای مورد انتظار سيستم، کارايي مورد انتظار، مستندات استاندارد توسعه و کليه انتظاراتی که در داخل تيم توسعه وجود دارد

4. 4 هزينه کيفيت هزينه های پيشگيری هزينه های پيشگيری quality planning quality planning formal technical reviews formal technical reviews test equipment test equipment Training Training هزينه های شکست داخلی هزينه های شکست داخلی rework rework repair repair failure mode analysis failure mode analysis هزينه های شکست خارجی هزينه های شکست خارجی complaint resolution complaint resolution product return and replacement product return and replacement help line support help line support warranty work warranty work

5. 5 تضمين کيفيت نرم افزار مرور تکنيکی آزمايش و مرور طرح اندازه گيری تحليل و گزارش گيری تعريف فرآيند و استاداردهای آن

6. 6 وظايف گروه SQA آماده سازی طرح SQA آماده سازی طرح SQA طرح بايد شامل طرح بايد شامل ارزيابی هايي که بايد انجام گيرد. ارزيابی هايي که بايد انجام گيرد. مرورهايي که بايد انجام پذيرد مرورهايي که بايد انجام پذيرد استانداردهايي که بايد در پرويه مورد توجه قرار گيزد استانداردهايي که بايد در پرويه مورد توجه قرار گيزد رويه هايي جهت رديابی و شناسايي خطا رويه هايي جهت رديابی و شناسايي خطا مستنداتی که بايد توسط گروه SQA توليد گردد مستنداتی که بايد توسط گروه SQA توليد گردد ميزان بازخوردی که به تيم نرم افزار منتقل می شود. ميزان بازخوردی که به تيم نرم افزار منتقل می شود. همکاری با تيم توسعه در زمينه تعريف فرآيند توليد نرم افزار همکاری با تيم توسعه در زمينه تعريف فرآيند توليد نرم افزار گروه SQA بايد فرآيند توسعه را به منظور پيروی از سياستهای سازمانی، استاندارهای داخلی در توسعه، و استاندارهای خارجی مرور کند. گروه SQA بايد فرآيند توسعه را به منظور پيروی از سياستهای سازمانی، استاندارهای داخلی در توسعه، و استاندارهای خارجی مرور کند.

7. 7 وظايف گروهSQA وظايف گروهSQA مرور فعاليتهای مهندسی نرم افزار برای اطمينان از پيروی اصول مرور فعاليتهای مهندسی نرم افزار برای اطمينان از پيروی اصول ميزان انحراف مستندات و رويه ها مشخص می گردد. ميزان انحراف مستندات و رويه ها مشخص می گردد. انجام بازرسی در فرآيند توسعه نرم افزار به منظور پيروی از اصول از پيش تعيين شده. انجام بازرسی در فرآيند توسعه نرم افزار به منظور پيروی از اصول از پيش تعيين شده. به صورت تصادفی يک سری از مستندات مورد بررسی قرار می گيرند. به صورت تصادفی يک سری از مستندات مورد بررسی قرار می گيرند. به صورت دوره ای گزارشاتی را برای مديريت پروژه ارائه شود به صورت دوره ای گزارشاتی را برای مديريت پروژه ارائه شود اطمينان از اينکه انحرافات موجود در فرآيند مستند سازی شده و به آنها رسيدگی گردد. اطمينان از اينکه انحرافات موجود در فرآيند مستند سازی شده و به آنها رسيدگی گردد. ثبت مواردی که به آنها رسيدگی نشده و گزارش آنها به مديريت ارشد. ثبت مواردی که به آنها رسيدگی نشده و گزارش آنها به مديريت ارشد. موارد بايد پيگيری شوند تا از اجرای آنها اطمينان حاصل گردد. موارد بايد پيگيری شوند تا از اجرای آنها اطمينان حاصل گردد.

8. 8 Why SQA Activities Pay Off? cost to find and fix a defect 100 10 log scale 1 Req. Design code test system test field use 0.75 1.00 1.50 3.00 10.00 60.00-100.00

9. 9 Reviews & Inspections... there is no particular reason why your friend and colleague cannot also be your sternest critic. Jerry Weinberg

10. 10 What Are Reviews? a meeting conducted by technical people for technical people a meeting conducted by technical people for technical people a technical assessment of a work product created during the software engineering process a technical assessment of a work product created during the software engineering process a software quality assurance mechanism a software quality assurance mechanism a training ground a training ground

11. 11 What Reviews Are Not A project summary or progress assessment A project summary or progress assessment A meeting intended solely to impart information A meeting intended solely to impart information A mechanism for political or personal reprisal! A mechanism for political or personal reprisal!

12. 12 The Players review leader producer recorder reviewer standards bearer (SQA) maintenanceoracle user rep

13. 13 Conducting the Review be prepared—evaluate product before the review review the product, not the producer keep your tone mild, ask questions instead of making accusations stick to the review agenda raise issues, don't resolve them avoid discussions of style—stick to technical correctness schedule reviews as project tasks record and report all review results 1. 2. 3. 4. 5. 6. 7. 8.

14. 14 Review Options Matrix trained leader agenda established reviewers prepare in advance producer presents product “reader” presents product recorder takes notes checklists used to find errors errors categorized as found issues list created team must sign-off on result IPR—informal peer review WT—Walkthrough IN—Inspection RRR—round robin review IPRWTIN RRR nomaybemaybemaybenomaybenonononoyesyesyesyesnoyesnonoyesyes yesyesyesnoyesyesyesyesyesyesyesyesyesnonoyesnonoyesmaybe * *

15. 15 Sample-Driven Reviews (SDRs) SDRs attempt to quantify those work products that are primary targets for full FTRs. SDRs attempt to quantify those work products that are primary targets for full FTRs. To accomplish this … Inspect a fraction a i of each software work product, i. Record the number of faults, f i found within a i. Inspect a fraction a i of each software work product, i. Record the number of faults, f i found within a i. Develop a gross estimate of the number of faults within work product i by multiplying f i by 1/a i. Develop a gross estimate of the number of faults within work product i by multiplying f i by 1/a i. Sort the work products in descending order according to the gross estimate of the number of faults in each. Sort the work products in descending order according to the gross estimate of the number of faults in each. Focus available review resources on those work products that have the highest estimated number of faults. Focus available review resources on those work products that have the highest estimated number of faults.

16. 16 Metrics Derived from Reviews inspection time per page of documentation inspection time per KLOC or FP errors uncovered per reviewer hour errors uncovered per preparation hour errors uncovered per SE task (e.g., design) number of minor errors (e.g., typos) number of errors found during preparation number of major errors (e.g., nonconformance to req.) (e.g., nonconformance to req.) inspection effort per KLOC or FP

17. 17 Statistical SQA Product & Process measurement... an understanding of how to improve quality... Collect information on all defects Find the causes of the defects Move to provide fixes for the process

18. 18 Six-Sigma for Software Engineering The term “six sigma” is derived from six standard deviations—3.4 instances (defects) per million occurrences—implying an extremely high quality standard. The term “six sigma” is derived from six standard deviations—3.4 instances (defects) per million occurrences—implying an extremely high quality standard. The Six Sigma methodology defines three core steps: The Six Sigma methodology defines three core steps: Define customer requirements and deliverables and project goals via well- defined methods of customer communication Define customer requirements and deliverables and project goals via well- defined methods of customer communication Measure the existing process and its output to determine current quality performance (collect defect metrics) Measure the existing process and its output to determine current quality performance (collect defect metrics) Analyze defect metrics and determine the vital few causes. Analyze defect metrics and determine the vital few causes. Improve the process by eliminating the root causes of defects. Improve the process by eliminating the root causes of defects. Control the process to ensure that future work does not reintroduce the causes of defects.

19. 19 Software Reliability A simple measure of reliability is mean-time-between- failure (MTBF), where A simple measure of reliability is mean-time-between- failure (MTBF), where MTBF = MTTF + MTTR The acronyms MTTF and MTTR are mean-time-to-failure and mean-time-to-repair, respectively. Software availability is the probability that a program is operating according to requirements at a given point in time and is defined as Software availability is the probability that a program is operating according to requirements at a given point in time and is defined as Availability = [MTTF/(MTTF + MTTR)] x 100%

20. 20 Software Safety Software safety is a software quality assurance activity that focuses on the identification and assessment of potential hazards that may affect software negatively and cause an entire system to fail. Software safety is a software quality assurance activity that focuses on the identification and assessment of potential hazards that may affect software negatively and cause an entire system to fail. If hazards can be identified early in the software process, software design features can be specified that will either eliminate or control potential hazards. If hazards can be identified early in the software process, software design features can be specified that will either eliminate or control potential hazards.

21. 21 Mistake-Proofing Poka-yoke (mistake-proofing) devices—mechanisms that lead to the prevention of a potential quality problem before it occurs or the rapid detection of quality problems if they are introduced. An effective poka-yoke device exhibits a set of common characteristics: An effective poka-yoke device exhibits a set of common characteristics: It is simple and cheap. If a device is too complicated or expensive, it will not be cost effective. It is simple and cheap. If a device is too complicated or expensive, it will not be cost effective. It is part of the process. That is, the poka-yoke device is integrated into an engineering activity. It is part of the process. That is, the poka-yoke device is integrated into an engineering activity. It is located near the process task where the mistakes occur. Thus, it provides rapid feedback and error correction. It is located near the process task where the mistakes occur. Thus, it provides rapid feedback and error correction.

22. 22 ISO 9001:2000 Standard ISO 9001:2000 is the quality assurance standard that applies to software engineering. ISO 9001:2000 is the quality assurance standard that applies to software engineering. The standard contains 20 requirements that must be present for an effective quality assurance system. The standard contains 20 requirements that must be present for an effective quality assurance system. The requirements delineated by ISO 9001:2000 address topics such as The requirements delineated by ISO 9001:2000 address topics such as management responsibility, quality system, contract review, design control, document and data control, product identification and traceability, process control, inspection and testing, corrective and preventive action, control of quality records, internal quality audits, training, servicing, and statistical techniques. management responsibility, quality system, contract review, design control, document and data control, product identification and traceability, process control, inspection and testing, corrective and preventive action, control of quality records, internal quality audits, training, servicing, and statistical techniques.