The document discusses different techniques for estimating the size, cost, and effort of software projects. It describes methods like lines of code counting and functional point analysis to estimate project size based on requirements. Cost is estimated as a function of effort and expenses. Effort estimation techniques include the holistic COCOMO model which estimates effort based on project attributes in basic, intermediate and detailed levels, and the activity based model which uses metrics from past projects.

1. Prepared & Presented by: Shashank Jain Software Estimation Techniques

2. Software Estimation Size Estimation Cost Estimation Effort Estimation 2 Prepared and presented by Shashank Jain

3. Size Estimation Based upon known system requirements Two methods for size estimation: KSLOC Functional Points By using some constants functional points are converted into KSLOC. 3 Prepared and presented by Shashank Jain

4. Techniques for Size estimation Developers opinion Experts estimation -Guessing based on experience 4 Prepared and presented by Shashank Jain

5. Techniques for Size estimation Previous years’ experience Using the Size Estimating Template: help to make estimates of how big a new software project will be or how long it will take to create the project (seize and time estimation) 5 Prepared and presented by Shashank Jain

6. Techniques for Size estimation Counting functional blocks - relies on the fact that most software systems decompose into roughly the same number of "levels". After decomposing it into functions and sub-functions it is multiplied with previous size estimates. In case of no previous estimates we multiply as: Functional blocks = 41.6 KSLOC Sub functional blocks = 4.16 KSLOC 6 Prepared and presented by Shashank Jain

7. Techniques for Size estimation Functional Point analysis: -Instead of counting the lines of code that make up a system, count the number of externals (inputs, outputs, inquiries and interfaces) that make up the system. 7 Prepared and presented by Shashank Jain

8. Functional Point analysis external inputs - data or control inputs (input files, tables, forms, screens, messages, etc.) to the system. 2. external outputs - data or control outputs from the system 3. external inquiries - I/O queries which require a response (prompts, interrupts, calls, etc.) 8 Prepared and presented by Shashank Jain

9. Functional Point analysis 4. external interfaces - libraries or programs which are passed into and out of the system (I/O routines, sorting procedures, math libraries, run-time libraries, etc.) 5. internal data files - groupings of data stored internally in the system (entities, internal control files, directories) 9 Prepared and presented by Shashank Jain

10. Application Size Estimation UCP = UUCP * TCF * EF TCF= 0.6+ (0.01* T-FACTOR) EF= 1.4 + (-0.03* E-FACTOR) UUCP = Weightage Value 10 Prepared and presented by Shashank Jain

11. Software cost analysis Cost is the function of Software development cost Cost of equipments and supplies So Cost= Effort * Fixed labor cost 11 Prepared and presented by Shashank Jain

12. Effort Estimation Holistic model For new development where relative rates are not available Activity based model When relative rates are available 12 Prepared and presented by Shashank Jain

13. Popular holistic model SDM (Software Development Model - Putnam - 1978) SLIM (Software Lifecycle Management - Putnam - 1979) COCOMO (Constructive Cost Model - Boehm - 1981) COPMO (Cooperative Programming Model - Conte, 13 Prepared and presented by Shashank Jain

14. COCOMO COCOMO comes in 3 levels with increased accuracy in each level: Basic Intermediate Detail 14 Prepared and presented by Shashank Jain

15. 15 Prepared and presented by Shashank Jain

16. Basic COCOMO Basic COCOMO is provided for three operational modes: organic, semi-detached, and embedded Organic: small experienced team in small project Embedded: large project with many constraints Semi-detached: somewhere in between 16 Prepared and presented by Shashank Jain

17. Basic COCOMO equations 17 Prepared and presented by Shashank Jain

18. The activity-based model uses data from the metrics database to determine the labour rates For this reason, you can only apply it once the metrics database is established and there is a baseline from which to work Activity based model: 18 Prepared and presented by Shashank Jain

19. - THANK YOU 19 Prepared and presented by Shashank Jain