Understanding the Detailed Kokomo Model

Hello everyone, in this lecture I am going to discuss about the third Kokomo model. As you know that we have already learned to models, the basic and intermediate Kokomo model and we have computed the effort and development time with the help of basic and intermediate formulas. Now today I am going to discuss in this lecture about the detailed Kokomo model. So this detailed Kokomo model will compute the effort and development time with the help of the formula of the intermediate Kokomo model. model but it will also provide you the effort and development time according to the phase so whatever the phases we are having in the software development lifecycle models that you have learned already so now you will be able to compute the effort and development time for each and every phase This model will be applied to three type of projects organic, semi-detached and embedded mode projects. Here these are the development phases. So for the plan and requirements. phase the effort will be 6% to 8% for a project and development time will be 10% to 40% of the project. So this phase will take less effort and less time which will depend on the mode and size of the project. Now if we talk about the design phase, so design phase will require the 16% to 18% effort for the project completion and time will be taken by it 19% to 30% So if we come to the programming or coding phase, this will require the 16% to 20% effort. will require more effort so that is a 48% to 68% and time will be taken as a 24% to 64% now if you talk about the integration and test it will have the effort 16% to 34% and time duration will be 18% to 34% so how we will process how we will compute the cost how we will estimate the cost with the help of the detailed model. So if you see the formula here phase wise formula you are able to compute the phase wise effort and phase wise duration with the help of this formula mu p into e and tau p into d. So what is e? e is your effort and d is your development time. So this is your total effort of the project and this is your total development time of the project. So first how you will compute the time of the project? So first how you will compute the total effort and total development time of the project. So you have to use the formula of intermediate model that is E equal to AI 1000 lines of code to power VI into EAF. So you have studied about the effort adjustment factors and there were 15 cost drivers. So these values will be given to you and you will multiply these cost drivers and then you will be able to find out the EAF and and then you will multiply this Eaf by the Ai thousand line of code 2 power Bi. From where Ai and Bi you will get, Ai and Bi coefficients or constants you will get from the table of intermediate model. Now then you will be able to compute the development time. So if you have computed effort you will put this effort into the formula of development time. And Ci and Di you will take from the intermediate table. Now A, B, C, D these four coefficients will depend on the type of the project. Whether it is organic, semi-detached or embedded. After that you require the Mu P and To P to divide this total effort into effort for the different phases and total development time into time for the different phases. So we have a table that is mu p. If we multiply the computed effort by 0.16 then it will give you the effort of the system design phase. If you will multiply the total effort by 0.26 then it will give you the detail and if you will multiply this effort by 0.42 then you will have the effort for the module code and test and if you will multiply 0.16 by this total effort then you will get the effort for the integration and testing phase so these are the phases are having the values according to their sizes so whatever the size of the project given to you according to that you will take the value from this table and specifically you can find out the phasewise effort now we take the table of the topic so this topic will be used for the development time you should always remember the new table will be used for the effort estimation phasewise effort estimation and this topic table will be utilized for the development time according to the phase so what you will do if you have computed the total development time then you have to multiply this total development time by 0.19 or 0.24, 0.39, 0.18 to get the phase wise development time. So these are the four different phases that we have in software life cycle. And now we have one question that we will try to solve. Consider a project to double. of a full screen editor so there is a full screen editor you have to implement you have to develop and there are few components whose size is given to you so screen edit command language interpreter file input and output cursor movement screen movement so all these components are having the size that has been already estimated four thousand lines of code two thousand lines of code one thousand lines of code two thousand lines of code and three thousand lines of code respectively so how we will get the total size we will sum up all these so it will give you the total size of the project now overall cost and schedule you have to estimate and cost and schedule estimates for the different phases So, one thing if you are going to utilize the intermediate formula, so you need the Eaf. So, Eaf will be given to you, but in this question the question is saying you have to assume, you can assume. So, any value you can assume on the basis of the table of the cost drivers. So, here at least the question is saying at least three values you have to take the different and rest of the values you have to take the one. In this question, I am taking the four values different and remaining 11 values one. So that is the nominal values. So first, we will compute the total size that is 12,000 lines of code. Then EAF. So EAF. First, I have taken required software reliability is high and product complexity is high. So these are the product attributes. These two are the product attributes. So you can see in the table we have taken one. 1.15, 1.15 how we have taken you can see this is product attributes reliability and complexity. Reliability is high so you have 1.15 complexity is high you are having 1.15. Another two values are the analyst capability is high and programming language experience is low so if you remember it is the part of personal attributes so you should go for the personal. attributes and there is an analyst capability is a high so analyst capability and you should go for the high column so that you will get the 0.86 and next is the programming language experience is low so language experience is this one and you will go for the low value 1.07 and rest of the values the question is saying you have to assume nominal so all the remaining 11 values will be the one So there is no effect of after multiplying these one. So we will multiply these four values for the effort adjustment factors. So now you know the question of intermediate E equal to AI thousand lines of code to power BI into EAF. EAF you have already computed. You can put here thousand lines of code you have computed by summing all the size of all the modules. that is 12,000 lines of code now a and b i you will take from the table of intermediate for the basic model okay so for that for the organic model so for the organic mode project you will take this value and for the c and di also you will take the organic value and after computation of effort you will put this value into the formula of development time then you will find out the total development time so now you have the total effort and total development time now how you will categorize how you will find out the phase wise effort and phase wise development time So here EP equal to mu p into E. So effort you have 52.91. Now 52.91 first time you will multiply 0.16 or 0.06 you will get the plan and requirements effort. 0.16 into 52.91 system design effort. 0.26 into 52.91 detail design effort. 0.42 into 52.91 module code and test effort. 0.46 into 52.91 52.91 into 0.16 integration and test effort okay now for the development time again you have the 11.29 the total development time so you will start to multiply 11.29 into 1.0.10 so that is the development time for plan and requirements Then 0.19 into 11.29 that will give you the system design development time. Then 0.24 detailed design into 0.24 into 11.29 that will give you the development time for detailed design phase. then 0.39 into 11.29 that will give you the module code and test time and then integration and testing 0.18 into 11.29 so overall you will get the phase wise effort as well as the development time so you can see we have computed here this is the organic small model so there is a size 12,000 lines of code we have already computed on the basis of this your effort so effort is there so every time effort will be multiplied by the given phase wise values of the mu p so mu p you should remember always mu p will be used for the effort estimation so there 0.16 for system design 0.26 for detail design 0.42 for module code and test and 0.16 for integration test you will multiply then you will get the phase wise effort so if you will sum up all these you will will get the total 52.91 and for the phase wise development time again you have to take the toppy values for the system design value 0.19 0.24 0.39 0.18 and you will multiply by these values by 11.29 and you will get the total phase wise development time and if you will sum up this you will find out the total development time. So this is the distribution of your effort according to the phase. and this is the development time according to the phase. So on the basis of this method you can find out the phase wise effort as well as the development time for any project. Thank you. Keep Learning.

So this detailed Kokomo model will compute the effort and development time with the help of the formula of the intermediate Kokomo model. model but it will also provide you the effort and development time according to the phase so whatever the phases we are having in the software development lifecycle models that you have learned already so now you will be able to compute the effort and development time for each and every phase This model will be applied to three type of projects organic, semi-detached and embedded mode projects. Here these are the development phases. So for the plan and requirements. phase the effort will be 6% to 8% for a project and development time will be 10% to 40% of the project.

So this phase will take less effort and less time which will depend on the mode and size of the project. Now if we talk about the design phase, so design phase will require the 16% to 18% effort for the project completion and time will be taken by it 19% to 30% So if we come to the programming or coding phase, this will require the 16% to 20% effort. will require more effort so that is a 48% to 68% and time will be taken as a 24% to 64% now if you talk about the integration and test it will have the effort 16% to 34% and time duration will be 18% to 34% so how we will process how we will compute the cost how we will estimate the cost with the help of the detailed model.

So if you see the formula here phase wise formula you are able to compute the phase wise effort and phase wise duration with the help of this formula mu p into e and tau p into d. So what is e? e is your effort and d is your development time. So this is your total effort of the project and this is your total development time of the project.

So first how you will compute the time of the project? So first how you will compute the total effort and total development time of the project. So you have to use the formula of intermediate model that is E equal to AI 1000 lines of code to power VI into EAF. So you have studied about the effort adjustment factors and there were 15 cost drivers.

So these values will be given to you and you will multiply these cost drivers and then you will be able to find out the EAF and and then you will multiply this Eaf by the Ai thousand line of code 2 power Bi. From where Ai and Bi you will get, Ai and Bi coefficients or constants you will get from the table of intermediate model. Now then you will be able to compute the development time. So if you have computed effort you will put this effort into the formula of development time.

And Ci and Di you will take from the intermediate table. Now A, B, C, D these four coefficients will depend on the type of the project. Whether it is organic, semi-detached or embedded.

After that you require the Mu P and To P to divide this total effort into effort for the different phases and total development time into time for the different phases. So we have a table that is mu p. If we multiply the computed effort by 0.16 then it will give you the effort of the system design phase. If you will multiply the total effort by 0.26 then it will give you the detail and if you will multiply this effort by 0.42 then you will have the effort for the module code and test and if you will multiply 0.16 by this total effort then you will get the effort for the integration and testing phase so these are the phases are having the values according to their sizes so whatever the size of the project given to you according to that you will take the value from this table and specifically you can find out the phasewise effort now we take the table of the topic so this topic will be used for the development time you should always remember the new table will be used for the effort estimation phasewise effort estimation and this topic table will be utilized for the development time according to the phase so what you will do if you have computed the total development time then you have to multiply this total development time by 0.19 or 0.24, 0.39, 0.18 to get the phase wise development time. So these are the four different phases that we have in software life cycle.

And now we have one question that we will try to solve. Consider a project to double. of a full screen editor so there is a full screen editor you have to implement you have to develop and there are few components whose size is given to you so screen edit command language interpreter file input and output cursor movement screen movement so all these components are having the size that has been already estimated four thousand lines of code two thousand lines of code one thousand lines of code two thousand lines of code and three thousand lines of code respectively so how we will get the total size we will sum up all these so it will give you the total size of the project now overall cost and schedule you have to estimate and cost and schedule estimates for the different phases So, one thing if you are going to utilize the intermediate formula, so you need the Eaf.

So, Eaf will be given to you, but in this question the question is saying you have to assume, you can assume. So, any value you can assume on the basis of the table of the cost drivers. So, here at least the question is saying at least three values you have to take the different and rest of the values you have to take the one.

In this question, I am taking the four values different and remaining 11 values one. So that is the nominal values. So first, we will compute the total size that is 12,000 lines of code. Then EAF.

So EAF. First, I have taken required software reliability is high and product complexity is high. So these are the product attributes. These two are the product attributes. So you can see in the table we have taken one.

1.15, 1.15 how we have taken you can see this is product attributes reliability and complexity. Reliability is high so you have 1.15 complexity is high you are having 1.15. Another two values are the analyst capability is high and programming language experience is low so if you remember it is the part of personal attributes so you should go for the personal. attributes and there is an analyst capability is a high so analyst capability and you should go for the high column so that you will get the 0.86 and next is the programming language experience is low so language experience is this one and you will go for the low value 1.07 and rest of the values the question is saying you have to assume nominal so all the remaining 11 values will be the one So there is no effect of after multiplying these one. So we will multiply these four values for the effort adjustment factors.

So now you know the question of intermediate E equal to AI thousand lines of code to power BI into EAF. EAF you have already computed. You can put here thousand lines of code you have computed by summing all the size of all the modules.

that is 12,000 lines of code now a and b i you will take from the table of intermediate for the basic model okay so for that for the organic model so for the organic mode project you will take this value and for the c and di also you will take the organic value and after computation of effort you will put this value into the formula of development time then you will find out the total development time so now you have the total effort and total development time now how you will categorize how you will find out the phase wise effort and phase wise development time So here EP equal to mu p into E. So effort you have 52.91. Now 52.91 first time you will multiply 0.16 or 0.06 you will get the plan and requirements effort.

0.16 into 52.91 system design effort. 0.26 into 52.91 detail design effort. 0.42 into 52.91 module code and test effort. 0.46 into 52.91 52.91 into 0.16 integration and test effort okay now for the development time again you have the 11.29 the total development time so you will start to multiply 11.29 into 1.0.10 so that is the development time for plan and requirements Then 0.19 into 11.29 that will give you the system design development time. Then 0.24 detailed design into 0.24 into 11.29 that will give you the development time for detailed design phase.

then 0.39 into 11.29 that will give you the module code and test time and then integration and testing 0.18 into 11.29 so overall you will get the phase wise effort as well as the development time so you can see we have computed here this is the organic small model so there is a size 12,000 lines of code we have already computed on the basis of this your effort so effort is there so every time effort will be multiplied by the given phase wise values of the mu p so mu p you should remember always mu p will be used for the effort estimation so there 0.16 for system design 0.26 for detail design 0.42 for module code and test and 0.16 for integration test you will multiply then you will get the phase wise effort so if you will sum up all these you will will get the total 52.91 and for the phase wise development time again you have to take the toppy values for the system design value 0.19 0.24 0.39 0.18 and you will multiply by these values by 11.29 and you will get the total phase wise development time and if you will sum up this you will find out the total development time. So this is the distribution of your effort according to the phase. and this is the development time according to the phase.

So on the basis of this method you can find out the phase wise effort as well as the development time for any project. Thank you. Keep Learning.

Transcript for:Understanding the Detailed Kokomo Model

Transcript for:
Understanding the Detailed Kokomo Model