Question

Counting lines of code (LOC) is a popular method for estimating and tracking programmer productivity because

	a.	It has a short acronym
	b.	It is easy to use
	c.	It is a relevant measure of productivity
	d.	All developers have same development style
	e.	There is no other measure available

	a.	Before the project begins
	b.	Early in the project
	c.	Once the team members are assigned
	d.	Later in the project
	e.	When the business case is complete

What are some problems associated with counting LOC as a way of measuring developer productivity?

	a.	Different developers can have different programming verbosity
	b.	LOC doesn’t always reflect programming efficiency and quality
	c.	Using LOC as a productivity measure might encourage developers to write inefficient code
	d.	Different programming languages yield different LOC counts
	e.	All of the above

_____ are rules of thumb used to estimate the current project based on prior project experience.

	a.	Heuristics
	b.	COCOMO
	c.	LOC
	d.	FPA
	e.	Derivatives

Answer 1

I would say that LOC is popular because it is a relevant measure of productivity and LOC are easily measured upon project completion.

But it's not with it's fair share of downfalls. Higher LOC code doesn't necessarily mean it's efficient. For ex: let's take the most basic example in C

Program 1

#include <stdio.h>

int main() {
int a=5;
int b=10;
int c= 15;
int s = a+b+c;
printf("The sum is %d", s);
  return 0;
}

The above program can also be written as

#include <stdio.h>
int main() {
int a,b,c,s=a+b+c;
printf("The sum is %d", s);
return 0;
}

See how the lines decrease? Although not the prettiest when it comes to code readability but sure does reduce the LOC, doesn't it?

You seem to have missed a question there

Coming to the third question, I would say all of the above.