Hello friends today my topic is on .Line Of Code(LOC) In Software Engineering

2. Group members.
 Abdul Ghafoor
 Sadaam Hussain
 M Salman
 Ali Imran khan
 Saad yousaf

3. Presentation
software engineering

4. Why we do we need metrics and
measure ?
 Software measure are fundamentals need of software engineering .
 To control the software development process and quality of product .
 Metrics and measure use interchangeably .

5. What is measure or measurement ?
 A measurement of is an indication of the size ,quantity
amount or dimensions
of a particular attributes of a products or process .

6. What is metrics
 A metric is a measurement of the degree that
any attributes belongs to a system , product
or process .

7. Measurement vs. metrics
 Software measurement gives rise to software metrics .

8. Common software measurement
 Number of lines of code
 Program load time .
 Program execution time.
 Program size.
 Bugs per line of code and many more .

9. Metrics
Metrics are related to the four functions of management:
 Planning
 Organizing
 Controlling
 improving

10. Metrics Classification
 Product metrics and process metrics.

11. Application
 Product metrics are used to asses the state of the product, tracking risks and
discovering potential problem areas.

12. What is line of code ?
A line of cod is any line of program text that is not a comment or
blank line .regardless of the number of the statement of the code .
it include all line containing header and declaration and executable
and not executable .

13. Example
1. Add( )
2. {
3. int a,b,c;
4. //adding two value
5. C=a+b;
6. Cout<<c;
7. }
the line of code is 6

14. Types of line
 Physical lines
 Logical lines
 Logical lines of code

15. Advantage of LOC
 Using line of code for size estimation
 Very easy to count and calculate from developed code

16. Disadvantage of loc
 Loc is language and technology dependent
 Bad software design may cause excessive line of code

17. Needs of requirement analysis and
specification
 Many software projects fails .
we start implementing the software system without understanding
the requirement of user and product .
so we need requirement analysis and specification to understand the
system requirement in documented .

18. Requirement analysis and specification
 this is phase of SDLC.
 Requirement analysis and requirement specification these are two activities .
 We use requirement analysis and specification techniques to understand the
the requirement and prepare the specification documents .

19. Goals of requirement analysis and
specification
 GOALS …
fully understand the user requirement ,remove in-consistencies
,anomalies ,etc from requirement and prepare documents .

20. activities
 Two activities involve in this phase ….
 Requirement gathering and analysis.
 Specification ( external design)

21. Outputs of requirement analysis and
specification
 SRS = ( software requirement specification )