• Software Engineering Tutorial Notes

Center for Systems and Software Engineering COCOMO® Models Research Web-Based Tools Other Tools COCOMO® II C Onstructive COst MOdel II (COCOMO® II) is a model that allows one to estimate the cost, effort, and schedule when planning a new software development activity. COCOMO® II is the latest major extension to the original COCOMO® () model published in 1981. It consists of three submodels, each one offering increased fidelity the further along one is in the project planning and design process. Listed in increasing fidelity, these submodels are called the Applications Composition, Early Design, and Post-architecture models.

Cost Estimation Tutorial. Since software engineering aims to provide cost-effective software. 5- Using COCOMO Model to directly estimate efforts and time. University of Southern California - S IE Center for Software Engineering Tutorial: Software Cost Estimation with COCOMO 2.0 Barry Boehrn, USC COCOMOISCM Forum 1996 October 9.1996 l Barry Boehm - 1.

Basic MODEL [ ] Basic COCOMO computes software development effort (and cost) as a function of program size. Program size is expressed in estimated thousands of source lines of code (, ). COCOMO applies to three classes of software projects: • Organic projects - 'small' teams with 'good' experience working with 'less than rigid' requirements • Semi-detached projects - 'medium' teams with mixed experience working with a mix of rigid and less than rigid requirements • Embedded projects - developed within a set of 'tight' constraints. It is also combination of organic and semi-detached projects.(hardware, software, operational.) The basic COCOMO equations take the form Effort Applied (E) = a b(KLOC) b b [ ] Development Time (D) = c b(Effort Applied) d b [months] People required (P) = Effort Applied / Development Time [count] where, KLOC is the estimated number of delivered lines (expressed in thousands ) of code for project. The coefficients a b, b b, c b and d b are given in the following table (note: the values listed below are from the original analysis, with a modern reanalysis producing different values): Software project a b b b c b d b Organic 2.4 1.05 2.5 0.38 Semi-detached 3.0 1.12 2.5 0.35 Embedded 3.6 1.20 2.5 0.32 Basic COCOMO is good for quick estimate of software costs. However it does not account for differences in hardware constraints, personnel quality and experience, use of modern tools and techniques, and so on. Intermediate COCOMOs [ ] Intermediate COCOMO computes software development effort as function of program size and a set of 'cost drivers' that include subjective assessment of product, hardware, personnel and project attributes.

The job pattern of an IT company engaged in software development can be seen split in two parts: • Software Creation • Software Project Management A project is well-defined task, which is a collection of several operations done in order to achieve a goal (for example, software development and delivery). A Project can be characterized as: • Every project may has a unique and distinct goal.

The tasks are scheduled on day-to-day basis or in calendar months. The sum of time required to complete all tasks in hours or days is the total time invested to complete the project. • Cost estimation This might be considered as the most difficult of all because it depends on more elements than any of the previous ones. For estimating project cost, it is required to consider - • Size of software • Software quality • Hardware • Additional software or tools, licenses etc. • Skilled personnel with task-specific skills • Travel involved • Communication • Training and support Project Estimation Techniques We discussed various parameters involving project estimation such as size, effort, time and cost. Project manager can estimate the listed factors using two broadly recognized techniques – Decomposition Technique This technique assumes the software as a product of various compositions.

Project Communication Management Effective communication plays vital role in the success of a project. It bridges gaps between client and the organization, among the team members as well as other stake holders in the project such as hardware suppliers. Communication can be oral or written. Communication management process may have the following steps: • Planning - This step includes the identifications of all the stakeholders in the project and the mode of communication among them.

•, Chris Abts, A. Winsor Brown, Sunita Chulani, Bradford K. Clark, Ellis Horowitz, Ray Madachy, Donald J.

Software Engineering Tutorial Notes

• Embedded – A software project with requiring the highest level of complexity, creativity, and experience requirement fall under this category. Such software requires a larger team size than the other two models and also the developers need to be sufficiently experienced and creative to develop such complex models.

30 (5): 416–42. External links [ ] • on tera-PROMISE • obtains a different value for the Organic exponent.

The Constructive Cost model was developed by Barry Boehm; this is a type of software that is used to determine cost estimate. It works by combining a regression formula with predetermined parameters that are derived through the data of a particular project. The main cocomo model advantage is that you can determine the costs that will be incurred when investing in a particular project. Another cocomo model advantage is that the estimates and all other related information that is obtained is factual, so your results are always accurate.

Or use it to find and download high-quality how-to PowerPoint ppt presentations with illustrated or animated slides that will teach you how to do something new, also for free. Or use it to upload your own PowerPoint slides so you can share them with your teachers, class, students, bosses, employees, customers, potential investors or the world.

A project manager closely monitors the development process, prepares and executes various plans, arranges necessary and adequate resources, maintains communication among all team members in order to address issues of cost, budget, resources, time, quality and customer satisfaction. Let us see few responsibilities that a project manager shoulders - Managing People • Act as project leader • Liaison with stakeholders • Managing human resources • Setting up reporting hierarchy etc. Managing Project • Defining and setting up project scope • Managing project management activities • Monitoring progress and performance • Risk analysis at every phase • Take necessary step to avoid or come out of problems • Act as project spokesperson Software Management Activities Software project management comprises of a number of activities, which contains planning of project, deciding scope of software product, estimation of cost in various terms, scheduling of tasks and events, and resource management.

• Manage - Analyze the probability of occurrence of risks at various phases. Make plan to avoid or face risks. Attempt to minimize their side-effects. • Monitor - Closely monitor the potential risks and their early symptoms. Also monitor the effects of steps taken to mitigate or avoid them. Project Execution & Monitoring In this phase, the tasks described in project plans are executed according to their schedules. Execution needs monitoring in order to check whether everything is going according to the plan.

The cocomo 2 model classifies all factors that can determine the outcome of a project and is also more accurate in helping you to scale these factors. The cocomo 2 model also makes it easier to choose the best project metrics.

Monitoring is observing to check the probability of risk and taking measures to address the risk or report the status of various tasks. These measures include - • Activity Monitoring - All activities scheduled within some task can be monitored on day-to-day basis.

• Execution - If the previous phase determines to execute the change request, this phase take appropriate actions to execute the change, does a thorough revision if necessary. • Close request - The change is verified for correct implementation and merging with the rest of the system.

We'll even convert your presentations and slide shows into the universal Flash format with all their original multimedia glory, including animation, 2D and 3D transition effects, embedded music or other audio, or even video embedded in slides. All for free.

It is measured in person-months units. • Schedule: Simply means the amount of time required for the completion of the job, which is, of course, proportional to the effort put.

• Validation - Validity of the change request is checked and its handling procedure is confirmed. • Analysis - The impact of change request is analyzed in terms of schedule, cost and required efforts.

There is truly something for everyone!

Boehm’s definition of organic, semidetached, and embedded systems: • Organic – 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 in the past and also the team members have a nominal experience regarding the problem. • Semi-detached – A software project is said to be a Semi-detached type if the vital characteristics such as team-size, experience, knowledge of the various programming environment lie in between that of organic and Embedded. The projects classified as Semi-Detached are comparatively less familiar and difficult to develop compared to the organic ones and require more experience and better guidance and creativity. Eg: Compilers or different Embedded Systems can be considered of Semi-Detached type. • Embedded – A software project with requiring the highest level of complexity, creativity, and experience requirement fall under this category. Such software requires a larger team size than the other two models and also the developers need to be sufficiently experienced and creative to develop such complex models. All the above system types utilize different values of the constants used in Effort Calculations.

These are types of COCOMO model: • Basic COCOMO Model • Intermediate COCOMO Model • Detailed COCOMO Model The first level, Basic COCOMO can be used for quick and slightly rough calculations of Software Costs. Its accuracy is somewhat restricted due to the absence of sufficient factor considerations. Intermediate COCOMO takes these Cost Drivers into account and Detailed COCOMO additionally accounts for the influence of individual project phases, i.e in case of Detailed it accounts for both these cost drivers and also calculations are performed phase wise henceforth producing a more accurate result. These two models are further discussed below. Estimation of Effort: Calculations – • Basic Model – The above formula is used for the cost estimation of for the basic COCOMO model, and also is used in the subsequent models. The constant values a and b for the Basic Model for the different categories of system: Software Projects a b Organic 2.4 1.05 Semi Detached 3.0 1.12 Embedded 3.6 1.20 The effort is measured in Person-Months and as evident from the formula is dependent on Kilo-Lines of code. These formulas are used as such in the Basic Model calculations, as not much consideration of different factors such as reliability, expertise is taken into account, henceforth the estimate is rough.

The coefficients a b, b b, c b and d b are given in the following table (note: the values listed below are from the original analysis, with a modern reanalysis producing different values): Software project a b b b c b d b Organic 2.4 1.05 2.5 0.38 Semi-detached 3.0 1.12 2.5 0.35 Embedded 3.6 1.20 2.5 0.32 Basic COCOMO is good for quick estimate of software costs. However it does not account for differences in hardware constraints, personnel quality and experience, use of modern tools and techniques, and so on. Mac os x 10 6 8 torrent.

The need for the new model came as software development technology moved from mainframe and overnight batch processing to desktop development, code reusability, and the use of off-the-shelf software components. This article refers to COCOMO 81. COCOMO consists of a hierarchy of three increasingly detailed and accurate forms. The first level, Basic COCOMO is good for quick, early, rough order of magnitude estimates of software costs, but its accuracy is limited due to its lack of factors to account for difference in project attributes ( Cost Drivers). Intermediate COCOMO takes these Cost Drivers into account and Detailed COCOMO additionally accounts for the influence of individual project phases. Basic MODEL [ ] Basic COCOMO computes software development effort (and cost) as a function of program size. Program size is expressed in estimated thousands of source lines of code (, ).

This mechanism ensures that input from various stakeholders is coming to the project manager as their feedback. • Closure - At the end of each major event, end of a phase of SDLC or end of the project itself, administrative closure is formally announced to update every stakeholder by sending email, by distributing a hardcopy of document or by other mean of effective communication. After closure, the team moves to next phase or project. Configuration Management Configuration management is a process of tracking and controlling the changes in software in terms of the requirements, design, functions and development of the product. IEEE defines it as “the process of identifying and defining the items in the system, controlling the change of these items throughout their life cycle, recording and reporting the status of items and change requests, and verifying the completeness and correctness of items”.

COCOMO II is the successor of COCOMO 81 and is claimed to be better suited for estimating modern software development projects; providing support for more recent and was tuned using a larger database of 161 projects. The need for the new model came as software development technology moved from mainframe and overnight batch processing to desktop development, code reusability, and the use of off-the-shelf software components. This article refers to COCOMO 81. COCOMO consists of a hierarchy of three increasingly detailed and accurate forms. The first level, Basic COCOMO is good for quick, early, rough order of magnitude estimates of software costs, but its accuracy is limited due to its lack of factors to account for difference in project attributes ( Cost Drivers).

Basic MODEL [ ] Basic COCOMO computes software development effort (and cost) as a function of program size. Program size is expressed in estimated thousands of source lines of code (, ). COCOMO applies to three classes of software projects: • Organic projects - 'small' teams with 'good' experience working with 'less than rigid' requirements • Semi-detached projects - 'medium' teams with mixed experience working with a mix of rigid and less than rigid requirements • Embedded projects - developed within a set of 'tight' constraints. It is also combination of organic and semi-detached projects.(hardware, software, operational.) The basic COCOMO equations take the form Effort Applied (E) = a b(KLOC) b b [ ] Development Time (D) = c b(Effort Applied) d b [months] People required (P) = Effort Applied / Development Time [count] where, KLOC is the estimated number of delivered lines (expressed in thousands ) of code for project. The coefficients a b, b b, c b and d b are given in the following table (note: the values listed below are from the original analysis, with a modern reanalysis producing different values): Software project a b b b c b d b Organic 2.4 1.05 2.5 0.38 Semi-detached 3.0 1.12 2.5 0.35 Embedded 3.6 1.20 2.5 0.32 Basic COCOMO is good for quick estimate of software costs. However it does not account for differences in hardware constraints, personnel quality and experience, use of modern tools and techniques, and so on.

Call.of.duty.modern.warfare.2 - razor1911 torrent password. Putnam model maps time and efforts required with software size. • COCOMO COCOMO stands for COnstructive COst MOdel, developed by Barry W. It divides the software product into three categories of software: organic, semi-detached and embedded. Project Scheduling Project Scheduling in a project refers to roadmap of all activities to be done with specified order and within time slot allotted to each activity. Project managers tend to define various tasks, and project milestones and them arrange them keeping various factors in mind.

Title: COCOMO Tutorial 1 COCOMO Tutorial • Ye Yang, USC-CSE • August 30, 2004 • yangy_at_sunset.usc.edu 2 COCOMO Background • COCOMO - the COnstructive COst MOdel • COCOMO II is the update to COCOMO 1981 • ongoing research with continuous calibrations made available • Originally developed by Dr. PowerShow.com is a leading presentation/slideshow sharing website. Whether your application is business, how-to, education, medicine, school, church, sales, marketing, online training or just for fun, PowerShow.com is a great resource. And, best of all, most of its cool features are free and easy to use. You can use PowerShow.com to find and download example online PowerPoint ppt presentations on just about any topic you can imagine so you can learn how to improve your own slides and presentations for free. Or use it to find and download high-quality how-to PowerPoint ppt presentations with illustrated or animated slides that will teach you how to do something new, also for free.