Explain the COCOMO model in detail, what is it?
Cocomo is a regression model based on the number of lines of code.It is a procedural cost estimate model for software projects that is used to reliably predict the various parameters associated with making a project such as size, effort, cost, time and quality.It was proposed by Barry Boehm in 1970 and is based on the study of 63 projects, which make it one of the best- documented models.Schedule means the amount of time required for the completion of the job, which is proportional to the effort put.Different models of Cocomo have been proposed to predict the cost estimation at different levels based on the amount of accuracy and correctness required.The models can be applied to a variety of projects, whose characteristics determine the value of constant to be used in subsequent calculations.A software project is said to be an organic type if the team size required is adequately small, the problem is well understood and has been solved.The projects classified as Semi-Detached are more difficult to develop than the organic ones because they are less familiar and require more experience and creativity.A software project with requiring the highest level of complexity, creativity, and experience requirement falls under this category.The larger the team size, the more complex the models need to be.
The key parameters which define the quality of any software products, which are also an outcome of the Cocomo are Effort and Schedule.Schedule means the amount of time required for the completion of the job, which is proportional to the effort put.Different models of Cocomo have been proposed to predict the cost estimation at different levels based on the amount of accuracy and correctness required.The models can be applied to a variety of projects, whose characteristics determine the value of constant to be used in subsequent calculations.A software project is said to be an organic type if the team size required is adequately small, the problem is well understood and has been solved.The projects classified as Semi-Detached are more difficult to develop than the organic ones because they are less familiar and require more experience and creativity.A software project with requiring the highest level of complexity, creativity, and experience requirement falls under this category.The larger the team size, the more complex the models need to be.
Depending on the amount of accuracy and correctness required, different models of Cocomo have been proposed.The models can be applied to a variety of projects, whose characteristics determine the value of constant to be used in subsequent calculations.A software project is said to be an organic type if the team size required is adequately small, the problem is well understood and has been solved.The projects classified as Semi-Detached are more difficult to develop than the organic ones because they are less familiar and require more experience and creativity.A software project with requiring the highest level of complexity, creativity, and experience requirement falls under this category.The larger the team size, the more complex the models need to be.
If the team size is small and the problem has been solved in the past, the software project is said to be an organic type.The projects classified as Semi-Detached are more difficult to develop than the organic ones because they are less familiar and require more experience and creativity.A software project with requiring the highest level of complexity, creativity, and experience requirement falls under this category.The larger the team size, the more complex the models need to be.
COCOMO consists of a hierarchy of three increasingly detailed and accurate forms.According to our requirements, any of the three forms can be adopted.The first level, Basic COCOMO, can be used for quick and slightly rough calculations of Software Costs.It's accuracy is somewhat restricted due to the lack of factor considerations.The above formula is used for the cost estimation of the basic COCOMO model and is also used in the subsequent models.The effort is measured in Person-Months and can be seen from the formula.No system can be calculated solely on the basis of lines of code.Reliability, experience, and capability are some of the other factors.The Intermediate Model uses 15 Cost Drivers for cost estimation.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
The first level can be used for quick and rough calculations of software costs.It's accuracy is somewhat restricted due to the lack of factor considerations.The above formula is used for the cost estimation of the basic COCOMO model and is also used in the subsequent models.The effort is measured in Person-Months and can be seen from the formula.No system can be calculated solely on the basis of lines of code.Reliability, experience, and capability are some of the other factors.The Intermediate Model uses 15 Cost Drivers for cost estimation.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
Intermediate COCOMO takes these cost drivers into account and also accounts for the influence of individual project phases in order to produce a more accurate result.The above formula is used for the cost estimation of the basic COCOMO model and is also used in the subsequent models.The effort is measured in Person-Months and can be seen from the formula.No system can be calculated solely on the basis of lines of code.Reliability, experience, and capability are some of the other factors.The Intermediate Model uses 15 Cost Drivers for cost estimation.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
The above formula is used for the cost estimation of the basic COCOMO model and is also used in the subsequent models.The effort is measured in Person-Months and can be seen from the formula.No system can be calculated solely on the basis of lines of code.Reliability, experience, and capability are some of the other factors.The Intermediate Model uses 15 Cost Drivers for cost estimation.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
The above formula is used to estimate the cost of the basic COCOMO model as well as the subsequent models.The effort is measured in Person-Months and can be seen from the formula.No system can be calculated solely on the basis of lines of code.Reliability, experience, and capability are some of the other factors.The Intermediate Model uses 15 Cost Drivers for cost estimation.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
The effort is measured in Person-Months and as evident from the formula is dependent on Kilo-Lines of code.No system can be calculated solely on the basis of lines of code.Reliability, experience, and capability are some of the other factors.The Intermediate Model uses 15 Cost Drivers for cost estimation.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
The estimate is rough because not much consideration of different factors such as reliability, expertise is taken into account.No system can be calculated solely on the basis of lines of code.Reliability, experience, and capability are some of the other factors.The Intermediate Model uses 15 Cost Drivers for cost estimation.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
The Cocomo model assumes that the effort is only a function of the number of lines of code and some constants evaluated according to the different software system.No system can be calculated solely on the basis of lines of code.Reliability, experience, and capability are some of the other factors.The Intermediate Model uses 15 Cost Drivers for cost estimation.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
The complexity of the product and the run-time performance constraints are two Hardware attributes.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
The complexity of the product is related to the software reliability extent and the run-time performance constraints.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
Hardware attributes include run-time performance constraints, memory constraints and the volatility of the virtual machine environment.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
Personnel attributes includealyst capability, software engineering capabilityApplications experienceVirtual machine experienceProgramming language experience, project attributes, use of software tools, and software reliability.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
Project attributes include the use of software tools, a development schedule, and software reliability.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.
The project manager has 15 different parameters to rate on a scale of one to three.The appropriate cost driver values are taken from the above table.The EAF is calculated by taking the 15 values and adding them up.The Intermediate COCOMO formula uses the values of a and b in case of the intermediate model.Each cost driver attribute uses different effort multipliers.The six phases of detailed cocomo are planning and requirements, system design, module code, test integration and test cost constructive model.