English Deutsch Français Italiano Español Português 繁體中文 Bahasa Indonesia Tiếng Việt ภาษาไทย
All categories

Software qulaity metrics

2007-01-30 17:26:03 · 4 answers · asked by unni 1 in Computers & Internet Software

4 answers

Software metrics is ways to measure the software application. It involves calculating the size of the application, the errors encountered while developing etc.

Typically software metrics consists of the Number of Lines of Code that has been written. There could be additional statistics like the average function size, average class size, average number of methods in the class, number of inputs/outputs in the application and lots many others.

The metrics also consists of the bugs/errors found when the software was tested. The bugs themselves are then classified as high, medium, and low priority. They are classified by the cause i.e. design problem, coding problem, data problem.

All this information put together can be used to determine the quality of the software in terms of bugs per line of code in the simplest of terms and one could do more complicated analysis based on this data.

2007-01-30 18:05:25 · answer #1 · answered by Sundarraj K 2 · 1 0

5%. Your question qualifies as software. Usability is extremely limited and contains significant errors, including spelling problems in 33.3% of the unique words.

2007-01-30 17:35:12 · answer #2 · answered by sspade30 5 · 0 0

utility metrics are utilized by potential of managers to degree the overall performance of their programmers. besides the undeniable fact that this has been widely criticized interior the utility progression field by using fact it measures the quantity of code created, no longer the time-honored of the code. the easy utility could be to degree the overall performance of your programmers on your team. it is going to help you observe somebody who for sure isn't powerfuble or lags at the back of the commonplace time-honored of your different programmers. those techniques might want for use with different administration recommendations to evaluate your utility progression team. case in point, peer assessment is additionally worth observing. velocity isn't the only degree you somewhat desire to care approximately. case in point, in case you one slow programmer who creates very stable code that individual could be extra advantageous for optimising code or writing code this is severe to overall performance.

2016-12-16 17:28:12 · answer #3 · answered by ? 4 · 0 0

um yeh

2007-01-30 17:45:39 · answer #4 · answered by conan 4 · 0 0

fedest.com, questions and answers