Is SLOC a good metric?

Is SLOC a good metric?

I think SLOC for defect % is a good metric. Yes the difficulty level comes into play but this is a good parameter that the managers can throw around while doing business.

What does SLOC tell you about software that is being developed?

Source Lines of Code (SLOC) is a software metric frequently used to measure the size and complexity of a software project. It is typically used to predict the amount of effort and time that will be required to develop a program, as well as to estimate the programming productivity once the software is produced.

What is SLOC in software project management?

Source lines of code (SLOC), also known as lines of code (LOC), is a software metric used to measure the size of a computer program by counting the number of lines in the text of the program’s source code.

What is SLOC on github?

SLOC stands for Source Lines of Code – the number of logical lines of code in the file (as opposed to the number of physical lines).

Why is lines of code a bad metric?

This is the reverse of the old project manager’s method of measuring programmer productivity by using lines of code written. A strict use of LOC as a metric could introduce dysfunctional dynamics through people inflating their LOC by not refactoring their code properly and creating future maintenance problems.

What is the major shortcoming of SLOC?

In particular, SLOC is a poor productivity measure of individuals, because a developer who develops only a few lines may still be more productive than a developer creating more lines of code – even more: some good refactoring like “extract method” to get rid of redundant code and keep it clean will mostly reduce the …

What is SLOC army?

Description. The Senior Leader Orientation Course (SLOC) provides executive level individualized force management presentations to senior Army military and civilian leadership. The program is designed to familiarize or update their knowledge of force management topics and processes.

Do lines of code matter?

Readability Martin Fowler, an expert software developer, once said, “Any fool can write code that a computer can understand. So, when programming, the readability of the source code will often be more important than the number of lines of code.

Which is more productive SLOC or reusable code?

Otherwise stated, the production of error prone unmaintainable spaghetti code with lots of copy-pasted parts will be considered as more productive than carefully engineered reusable code. So SLOC is definitively not the best way to measure productivity. What productivity are we considering ? Productivity is measured for a process.

What is the problem with the SLOC metric?

The problem with the SLOC metric is that it measures an approximation of the quantity of code written, without taking into account: the quality of the code (i.e. what if for every 100 SLOC you have to add another 90 SLOC because of bugs, but that you don’t know at the moment your code is delivered ?)

Is it OK to use Loc to measure productivity?

However, LOC should be used with care, since it is misused too often by persons who imagine some correlation between unrelated things. The most humanly disastrous usage of LOCs was in the past the attempt to measure the productivity of an individual developer based on the LOCs written per month.

Why is LOC important in software engineering Stack Exchange?

LOC has a value in some narrow situations. For instance, it could give a hint about the size of the project and parts of the project (and in average correlates with function points, while being often easier to measure), or it could indicate the methods and classes which may need further attention because of their large size.