What is LOC, standard, DOD, Functional Point ?

What are the main flaws and variations in Line of code (LOC) metric? How to mitigate those problems?

Flaws and Variations of LOC:

·         Count of physical lines including blank lines.

·         Countof all lines except blank lines and comments.

·         Count of all statements except comments.

·         Count of all lines except blank lines, comments, declarations and headings.

·         Count of only executable statements, not including exception conditions.

·         It is highly dependent on the programming language used as code writing varies from one programming language to another. For example, lines of code written (for a large program) in assembly language are more than lines of code written in C++. 

·          One of the problems with text-based definition of length is that the line of code measurement is increasingly less meaningful as software development turns to more automated tools, such as: Tools that generate code from specifications Visual programming tools

Disadvantages:

·         Vague definition

·         Language dependability

·         Not available for early planning

·         Developers’ skill dependability

What is standard?  Write down the standard format of DOD Data Item Descriptions (DIDs) in table form.

•      The rules which are universally or widely accepted, agreed upon, or established means of determining what something should be. Major classifications of this term include:

Ø   Material or substance whose properties are known with a level of accuracy that is sufficient to allow its use as a physical reference in calibrating or measuring the same properties of another material or substance.

Ø   Concept, norm, or principle established by agreement, authority, or custom, and used generally as an example or model to compare or measure the quality or performance of a practice or procedure.

Ø  Written definition, limit, or rule approved and monitored for compliance (acting according certain accepted standard) by an authoritative agency (or professional or recognized body) as a minimum acceptable benchmark (standard by which something can be measured or judge).

DOD Data Item Description Standards

Data requirements title

1. System segment design document

2. Software development plan

3. Software requirements specification

4. Interface requirements specification

5. Interface design document

6. Software design document

7. Software product specification

8. Version description document

9. Software test plan

10. Software test description

11. Software test report

12. Computer system operator's manual

13. Software user's manual

14. Software programmer's manual

15. Firmware support manual

16. Computer resources integrated support document

17. Engineering change proposal

18. Specification change notice

Distinguish between Adjusted and Unadjusted Function Point.

Adjusted Function Point:

The Function Point Analysis technique is used to assess the functionality delivered by software and a 'function point' is the unit of measurement.

    Adjusted FP Count = Unadjusted FP Count * VAF

Unadjusted Function Point:

The process of performing Function Point Analysis is called a 'Function Point Count' and it involves the identification, classification and weighting of each of these transactions and data components. The weightings are combined to give the functional size as an Unadjusted Function Point Count.

The final Function Point Count is obtained by multiplying the VAF times the Unadjusted Function Point (UAF). FP = UAF * VAF. Summary of benefits of Function Point Analysis. Function Points can be used to size software applications accurately. Sizing is an important component in determining productivity (outputs/inputs)