1 / 17

An Approach towards Software Quality Assessment

An Approach towards Software Quality Assessment. Introduction. What is Quality The Quality of a product or service refers to the perception of the degree to which the product or service meets the customer's expectations. Quality has no specific meaning unless related to a

megan
Download Presentation

An Approach towards Software Quality Assessment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An Approach towards Software Quality Assessment

  2. Introduction What is Quality The Quality of a product or service refers to the perception of the degree to which the product or service meets the customer's expectations. Quality has no specific meaning unless related to a specific function and/or object. Quality is a perceptual, conditional and somewhat subjective attribute.

  3. Why is software quality important? • long-term profitability • short-term profitability • doing it right the first time • facilitates development • given the constantly changing nature of software, higher quality software is easier to develop / maintain • customer satisfaction • prevalence of software in society • including safety critical systems and devices

  4. Approach • External and Internal quality attributes. • Add a new sub category regarding to manger (as shown in figure next). Then evaluate all these attributes to the participants of a software project (these are user, developer, and manager). According to methodology, design three different tables which have various attributes for evaluation. We look at these attributes from three different points of views, these are:

  5. Time Cost Manager User Developer Correctness Usability Efficiency Reliability Integrity Adaptability Accuracy Robustness Maintainability Flexibility Portability Reusability Readability Testability Understandability Product Size Data Structure Complexity Decision Complexity Industry Experience Proposed Approach (contd…) Figure Categorization of quality attributes

  6. Proposed Approach (contd…) User’s view (Also called external Quality): Table 1: External quality attributes

  7. So from the previous table we obtain: Total External Quality Value (EQ) = 4.8 Total Number of External Quality Factors (NEQ) = 8 Hence Average External Quality = EQ / NEQ = 0.6

  8. Proposed Approach (contd…) Developer’s View (Internal View): Table 2: Internal quality attributes

  9. Proposed Approach (contd…) • The value of last attribute (Industry Experience) in Table 2 is decided on the basis of developer’s experience in industry on different projects that is, as follows • 0 - 1 years experience = Very Low (0.2) • 1 - 3 years experience = Low (0.4) • 3 - 5 years experience = Normal (0.6) • 5 - 7 years experience = High (0.8) • 7 years and above = Very High (1.0)

  10. Proposed Approach (contd…) Table 3. Internal quality attributes So, from the table 2 and 3 we obtain: Total Internal Quality Value from Table 2 and 3 (IQ) = 4.2 + 2.2 = 6.4 Total Number of Internal Quality Factors from Table 2 and 3 (IEQ) = 8 + 3 = 11 Hence Average Internal Quality Value = IQ / IEQ = 0.58

  11. Proposed Approach (contd…) Manager’s View: Table 4: Managerial quality attributes

  12. Proposed Approach (contd…) • We compute the value of schedule pressure by following Equation. • Schedule Pressure = (Team estimated cycle-time -Management mandated cycle-time) / Team estimated cycle-time • Cycle time is measured as the number of calendar days that elapse from the date the baseline requirements are delivered until the date the software passes customer-acceptance testing [12]. The maximum value of Schedule pressure can be 1 and the minimum is 0 (but the zero value of schedule pressure is not possible in real life situations). Value of schedule pressure will get an entry in Table 4 as follows: • 0.01– 0.2 = Very high (0.2) • 0.21 – 0.4 = High (0.4) • 0.41 – 0.6 = Normal (0.6) • 0.61 – 0.8 = Low (0.8) • 0.81 – 1.0 = Very Low (1.0) Total Managerial Quality Value (MQ) = 2.0 Total Number of Managerial Quality Factors (MEQ) = 3 Hence Average Managerial Quality Value = MQ / MEQ = 0.66

  13. Proposed Approach (contd…) • final value of quality for software under consideration can be computed by following equation. • Total Quality (in %) = (sum (Valuei * Weighti)) *100

  14. Proposed Approach (contd…) To obtain the value for total Quality we assign weights to each of the internal, external and managerial quality obtained previously, such that the sum of these weights equals 1 and the weights are assigned on the basis of the relative importance of these quality characteristics as explained below:( These weights should be decided by the quality assurance team of the development organization) Table 4: Total quality value Hence Total Quality = Weighted Sum of All Quality Characteristics * 100 = .621 = 62.1 %

  15. References 1. Sivamuni Kalaimagal, and RengaramanujamSrinivasan.: A Retrospective on Software Component Quality Models. SIGSOFT Software Engineering Notes, November 2008, Volume 33 Number 5 2. Joseph P. Cavano and James A. Mccall.: A Framework for the Measurement of Software Quality 3. Arun Sharma, Rajesh Kumar, P. S. Grover.: Estimation of Quality for Software Components – an Empirical Approach. SIGSOFT Software Engineering November 2008, Volume 33, Number 5 4. LjerkaBeusDukic and Jorgen Boegh.: COTS Software Quality Evaluation. In the proceedings of ICCBSS, Ottawa, Canada, (February2003) 5. Luigi Buglione and AlianAbran.: A Quality Factor for Software 6. Sandra A. Slaughter, Donald E. Harter, and Mayuram S. Krishnan.: Evaluating the Cost of Software Quality 7. Justin M Beaver and Guy A. Schiavone.: The Effects of Development Team Skill on Software Product Quality. ACM SIGSOFT Software Engineering Notes, Volume 31 Number 3 (2006) 8. Dr. Mark C. Paulk.: Factors affecting Personal Software Quality 9. SPAWAR Systems center San Deigo.: SOFTWARE MANAGEMENT FOR EXECUTIVES GUIDE BOOK, PR-SPTO-03-v1.8a (Dec 1, 2003) 10. J. E. Gaffney: Metrics in Software Quality Assurance 11. Fritz Henglien, DIKU.: An Introduction to Software Quality 12. Manish Agrawal, and Kaushal Chari: Software Effort, Quality, and Cycle Time: A Study of CMM Level 5 Projects. IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. 33, NO. 3, (2007) 13.Praveen Ranjan Srivastava et al,Integrated Software Quality Evaluation: Multi-Criteria Approach”, Journal of Information Processing System (JIPS), Vol 7, No 3, PP 473-518(2012).

  16. Future Work Soft computing techniques can evaluate software quality assessment which may ultimately help software organization, end users in a greater extent. A number of extensions and applications of the model may be possible by using techniques like artificial neural networks, evolutionary computation and combination of neuro-fuzzy approach. In fact there is considerable need for applied research and strategy evaluation in this area using these techniques which is further scope of this research paper and will be dealt in the subsequent work.

  17. Thanks !

More Related