 Hello, welcome to the session on estimation of project matrix. After gathering the entire requirement specific to the software project, usually we need to think about different solution strategy for the project. So in this session, we will learn how to estimate the cost, effort and duration for a software project. And then we will select one solution approach, which will find suitable to fulfill the organizational goal. So at the end of this session, students they categorize the projects using Kokomo model and estimate the effort and development time required for the project. A software project is not just about writing a few hundred lines of source code to achieve a particular objective. The scope of the software project is comparatively quite large and such a project could take several years to complete project size. What would be the size of the code that is written say in number of lines, files or modules cost, how much would it cost to develop a software, a software may be just a piece of code, but one has to pay to the managers, developers and other project personnel. And how long would it be before the software is delivered to the client, the effort that is how much effort from the team members would be required to create the software. So Kokomo model that is constructive cost model was proposed by the bow. According to him, there could be three categories of the software projects that is organic, semi-detached and embedded. So the classification is done by considering the characteristics of the software, the development team and the environment. The concept of organic, semi-detached and embedded systems are described below. So the organic development project is said to be organic type if the project deals with the developing as well as understood the application, the development team is small, the team members have prior experience in working with similar types of projects. So semi-detached means a development projects can be categorized as a semi-detached type if the team consists of some experience as well as the inexperienced staff. So team members may have some experience on the type of system to be developed. Embedded type of development projects are those which aims to develop a software strongly related to machine hardware and the team size is usually large. So Bohm suggested that estimation of the project parameter should be done through three stages that is the basic Kokomo model, intermediate Kokomo and complete Kokomo. So the basic Kokomo model that helps to obtain a rough estimate of the project parameters it estimates the effort and time required for the development in the following way. So effort is A into the size rise to B that is person month and development time we can calculate is 2.5 into effort rise to C months. So KDSI is the estimated size of the software expressed in kilo delivered source instructions and ABC are the constant that is determined by the category of the software project. But that denotes the total effort required for the software development expressed in person per month and the development time that denotes the estimated time required to develop the software that is expressed in the month. So the value of the constant ABC are given so these are the fixed values that we need to consider for the organic type, semi-detached type and embedded type of the software project. The values are constant. Let us pause the video for a while and try to solve the question for a project type organic and if the A value is 2.4, 1.05 and C is 0.38 so that is taken from the previous year organic type values. So let us find out the effort and time for development and number of developers for the project size with 30 that is it is in the 1000 lines of code for a project size of 30 you need to find the effort and time for development and number of developers. So let us resume the video and the answer for this question is the effort in person per month is 85.35 and the development time in months is 13.55 so the number of developers is 7. So let us pause the video and answer the question according to the Kokomo model a project can be categorized into how many types the answer is three types that is as we discussed in the organic semi-detached and embedded okay three types. Next question consider you are developing a web application which would make use of a lot of web services provided by the Facebook, Google, Flickr would it be wise to make estimate for this project using Kokomo answer the question the answer is not at all not at all it is required. Let us discuss the intermediate Kokomo model in real life there are many other project parameter that influence the development of process the intermediate Kokomo takes those other factors into the consideration by define a set of 15 drivers that is product attributes hardware attributes personal attributes and project attributes project attributes that consist of required software reliability extent size of the application database complexity of the product and in hardware attributes that is a runtime performance constraint memory constraint volatility of the virtual machine environment then required turn about the time the personal attributes the analyst capability software engineering capability application experience virtual machine experience and programming language experience and in the project attributes we use use of software tools application of software engineering methods require the development schedule and all so we need to consider all these attributes that is product attributes hardware personal and project attributes complete Kokomo model both the basic and intermediate Kokomo models consider a software to be a single homogeneous entity an assumption which is really true in fact many real life applications are made up of several small subsystems one might not even develop all the subsystems so just use the available services the complete Kokomo model takes these factors into the account to provide as for more accurate estimate of the project matrix to illustrate this consider a very popular distributed application the ticket booking system of Indian Railway there are computerized ticket counters in most of the railway station of our country so the tickets can be booked or the cancelled from any such counters the reservation for future tickets cancellation of reserved tickets that could be performed on high level the ticket booking system has three main components that is a database and graphical user interface and network facilities so among these the development of the GUI is considered as an organic project type the database module that could be considered as semi-detached software so the networking module that can be considered as embedded software so to obtain a realistic cost one should estimate the cost for each component separately and then add it up so advantages of Kokomo model it is a simple model and it should help one to understand the concept of project matrix estimation the drawbacks are so Kokomo uses the size which is not a proper major of the program size indeed estimating the size of the software is difficult task and any slight miscalculation that could cause a large deviation in the subsequent project estimates so more over Kokomo was proposed in 1981 keeping the waterfall model of project life cycle in mind but it fails to address the other popular approaches like a prototype increments spiral agile models and moreover in present day a software project may not necessary like consistent of coding of every bit of the functionality rather existing software components are often used and glued together towards the development of new software so Kokomo is not suitable in such cases so Kokomo 2 was proposed in the later 2000 to many to address these issues so these are the references I referred thank you