Term paper Quantitative Evaluation of Software Quality.docx

Term paper Quantitative Evaluation of Software Quality.docx...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
“Quantitative Evaluation of Software Quality” CIS 635 By: Sushant Arora CSU ID 2505446 Page | 1 
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Table of Content Topic……………………………………………………………………….Page 1.Introduction ………………………………………………………………………………. 3 1.1 Characteristics of Software defects…………………………………………………4 1.2 what used to happen in past?. ......................................................................... 4-5 2. Requirements to evaluate quality……………………………. .................................... 6 2.1Characteristics of code…………………………………………………………….6-9 2.2 To develop a metric………………………………………………………………9-12 3.To evaluate quality…………………………………………………………………. .12-13 4.How to use quality Characteristics……………………………. ............................ 14-15 5.ISO approach to software quality…………………………………………………. .15-16 6.Software testing improves software quality…………………………………………. ..17 7.Conclusion………………………………………………………. ............................ 17-18 References…………………………………………………………………………………19 Page | 2 
Background image of page 2
Sushant Arora CSU ID 2505446 Cleveland State university                 ABSTRACT When an organisation decides to  develop   a   software   product   for  their customers so that it can be  used by number of users across  the   world   the   first   step   that  comes is to have a requirement  analysis   done   where   all  requirements   of   customers   are  taken care of and this is followed  by   designing   where   proper  designing is done for each of the  requirements i.e. how to cover all  the requirements , this is lead by  coding where one uses special  languages and tools to code  and  at last testing is done to satisfy  that code developed is fool proof  and actually serves the needs of  the   customers   and   users.   But  once   we   have   the   product,   in  order   to   ensure   that   products  meets   all   the   requirements   on  contract   we   need   quality  assurance,   i.e.   the   purpose   of  quality assurance is to achieve a  high quality product on time, on  schedule   within   budget     and   it  completely agrees to terms and  conditions of contracts. 1. Introduction
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 04/12/2010 for the course CIS 635 taught by Professor Mcintyre during the Spring '10 term at Cleary University.

Page1 / 24

Term paper Quantitative Evaluation of Software Quality.docx...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online