1. By Manish Shrotriya CSE300 2014MS Software Estimation Effort Estimation: how much effort is required to complete an activity. (How to define efforts: Line of Code) Time Estimation: how much time is required to complete an activity. (efforts * productivity) Productivity: Rate at which useful functionality is produced by a programmer Price of software: Total Cost of all activities + overheads

2. By Manish Shrotriya CSE300 2014MS Activity determination ( Functional Points) Using Functional Points Varies software to software Number of inputs required Number of output Number of files read Number of DB calls Weight is given to each type of activity Total count of FP = sum ( FP * weight) LOC = language factor * Total FP count

3. By Manish Shrotriya CSE300 2014MS Activity determination ( Object Points) Using Object Points (output objects) Varies software to software Number of Screens and category of screens Number of Reports and category of reports DSL or 4GL is required to output object Dev cost of DSL (Eg: Tag library) Weight is given to each type and category of Object Total OP count is summation of OP * type weight * category weight LOC = language factor * Total OP count

4. By Manish Shrotriya CSE300 2014MS Functional points vs Object Points Object points are converted directly from requirements (easier to determine) Functional points require technical expertise Use both Ex: Constructive Cost model (COCOMO 2) Early Prototyping (Proof of concept) phase: use OP Early Design phase: calculate based in FP Post Design: Directly calculate based in LOC required for Design

5. By Manish Shrotriya CSE300 2014MS Estimation Technique Expert Judgment ( Bottom up Approach) Based on expertise Tentative efforts Their complexity Efforts are converted into Dev time Advantage Detailed approach Disadvantage Very subjective Tend to underestimate integration and configuration

6. By Manish Shrotriya CSE300 2014MS Estimation Technique Analogy based ( Top down approach) Based on experience on similar project or part Activity and complexities are determined by correlation to previous project Estimates are directly taken from previous actuals Advantage High accuracy if analogy is close Cheap technique Disadvantage Tend to underestimate low level activity Dependent on fixed team

7. By Manish Shrotriya CSE300 2014MS Estimation Technique Mathematical Models Ex: COCOMO Efforts = a x (LOC) * b x M Value of a and b is given by Project complexity Simple(2.4, 1.05) Moderate(3, 1.12) Complex(3.6, 1.12) M is factor for developer capability. It has many component

8. By Manish Shrotriya CSE300 2014MS Estimation in Agile: Estimations are shared: based on collective responsibility Estimation scale (1,2,3,5,8) User stories are independent of Dev pair Planning Poker: Every member participate Story is read Secretly everyone selects a card On show call, cards are displayed Discrepancies are discussed

9. By Manish Shrotriya CSE300 2014MS Three point estimation: For each story three opinions are sought. Ideal, likely and worst. Then weighted mean is calculated Ex: Today’s game (Library) Library has many books, they are listed on library home page. Admin can login and add new books or copies. User can login and borrow a book or return a book.

10. By Manish Shrotriya CSE300 2014MS Ex: Today’s game (Library) User stories: 1.Admin is able to see lists of existing books on home page 2.Admin is able to log in admin page from home page 3.Admin is able to create new book with some copies on admin page 4.Admin is able to update number of copies of a given book 5.Admin is able to remove all copies of a given book 6.Admin is able to log out back to home page.

11. By Manish Shrotriya CSE300 2014MS Success of Projects till now.