Please enable JavaScript.
Coggle requires JavaScript to display documents.
Measuring software size - Coggle Diagram
Measuring software size
-
-
-
-
-
Using LOC counts
It would be poor practice to mingle LOC for code, support code, and product code. More LOC means more functionality but not always mean is a better program.
You want to use program size for the following: To deal with programs packaging. To measure, evaluate or predict work on the product. To asses the program quality
-
Packaging
Total packaging cost often exceed developtment cost, another issue is the physical memory space required to hold a running program
-
Reuse consideratios
You can use developed programs rather than do it again from scratch, you need to decide how to treat them if you do it as the same way from new code your productivity numbers must reflect this practice
Calculating productivity
You divide the amount of products produce to the amount of hours you spend that give us the volume of product produce per hour
There could be a variation solely by our choice of how to count LOC, you should also consider the amount of work involved
LOC counters
Physical LOC counters
Here you either ignore comments and blank lines or count them separately. Its normal to count all source lines in a given program unit, is also desirable to ount the various program element.
Logical LOC counters
You must establish a logical line coun standard, the key is to be precise and consistent. this departs from a personal preference due to the fact that there is no better way than other.
-
-