1. Software Project Planning

2. Software Engineering Estimation Estimation The SPM begins with a set of activities that are collectively called Project planning The SPM begins with a set of activities that are collectively called Project planning Whenever estimates are are made we look into future concern and so there is some degree of uncertainty in estimation Whenever estimates are are made we look into future concern and so there is some degree of uncertainty in estimation

3. Software Engineering Observation on Estimation Observation on Estimation PM manager must have the ability to estimate PM manager must have the ability to estimate PM with the ability to know what will go wrong before it actually does PM with the ability to know what will go wrong before it actually does Estimation of resources, cost and schedule for a software requires experience of past projects and access to historical data Estimation of resources, cost and schedule for a software requires experience of past projects and access to historical data

4. Software Engineering Project complexity has a strong effect on uncertainty that is inherent in planning. Project complexity has a strong effect on uncertainty that is inherent in planning. Complexity is affected by familiarity with past efforts Complexity is affected by familiarity with past efforts Real time projects are always complex Real time projects are always complex Project size also effect the accuracy of the estimates Project size also effect the accuracy of the estimates

5. Software Engineering If the requirements have been solidified estimation is easy but if the requirement are keep on changing estimation is affects If the requirements have been solidified estimation is easy but if the requirement are keep on changing estimation is affects

6. Software Engineering Project Planning objectives Project Planning objectives The objectives of software project planning is to provides the reasonable estimates of cost, effort and schedule The objectives of software project planning is to provides the reasonable estimates of cost, effort and schedule These estimates are made at the beginning of the project and must be updated wit the passage of time. These estimates are made at the beginning of the project and must be updated wit the passage of time.

7. Software Engineering Software Scope Software Scope Estimation of scope Estimation of scope Functional, non functional requirements. Constraints Functional, non functional requirements. Constraints

8. Software Engineering Obtaining information necessary for scope Obtaining information necessary for scope Things are always hazy at the start of the project Things are always hazy at the start of the project There must be some meeting between customer and analyst for obtaining the scope of project There must be some meeting between customer and analyst for obtaining the scope of project

9. Software Engineering 1 st meeting question 1 st meeting question 2 nd meeting question 2 nd meeting question 3 rd meeting question and so on 3 rd meeting question and so on

10. Software Engineering Resources Resources The 2 nd task of software planning is the estimation of resources required to accomplish the software development effort The 2 nd task of software planning is the estimation of resources required to accomplish the software development effort Pyramid Pyramid The development environment-----Hardware and software tools, Reusable components and people The development environment-----Hardware and software tools, Reusable components and people

11. Software Engineering Human Resource: Human Resource: The no. of people required for a software project can be determined only after an estimate of development effort. Reusable Software component Reusable Software component Off the shelf components Full experience components Partial experience components New components

12. Software Engineering Guidelines Guidelines

13. Software Engineering Software Sizing Software Sizing Fuzzy logic sizing Function point sizing Standard component sizing

14. Software Engineering Problem based estimation Problem based estimation EV is calculated as EV= (S opt +4S m +S pess )/6 There is a very small probability that the actual size result will fall outside the EV

15. Software Engineering Example Example

16. Software Engineering COCOMO Model COCOMO Model Constructive Cost model Three model Model 1 Model 2 Mode3

17. Software Engineering Model 1 is called Basic COCOMO Model 1 is called Basic COCOMO It has three level It has three levelOrganicSemi-detachedEmbedded

18. Software Engineering E= a b KLOC bb E= a b KLOC bb D= c b E dd D= c b E dd N= E/D N= E/D Where E is the development effort in PM and D is the development effort time in months and N is the no of people

19. Software Engineering Make Buy decision: Make Buy decision: The software managers are often faced with the problem of make buy decision. In some cases it is cost effective to acquire rather than internal development