Download
SOFTWARE ENGINEERING Presentation Transcript:
1.SOFTWARE ENGINNERING
2. THE CONSTRUCTIVE COST MODEL
(COCOMO MODEL)
3.OUTLINE OF PRESENTATION
OVERVIEW
ARCHITECTURE OF COCOMO MODEL
BASIC CONCEPT OF COCOMO MODEL?
TYPES OF COCOMO MODEL
INTERMEDIATE COCOMO
ADVANTAGE OF COCOMO
DISADVANTAGE OF COCOMO
MULTIPLERS
COST DRIVERS
LIMITATIONS
CHARACTERISTICS OF COCOMO
CONCULSION
4.OVERVIEW
The Constructive Cost Model (COCOMO) is an algorithmic software cost estimation model developed by Barry W. Boehm
COCOMO was first published in Boehm's 1981 book Software Engineering Economics[1] as a model for estimating effort, cost, and schedule for software projects
5.ARCHITECTURE OF COCOMO MODEL
6.BASIC CONCEPT OF COCOMO MODEL
computes software development effort (and cost) as a function of program size. Program size is expressed in estimated thousands of source lines of code (SLOC)
COCOMO applies to three classes of software projects:
7.BASIC COCOMO EQUATION TAKE FORM
Effort Applied (E) = ab(KLOC)bb [ man-months ]
Development Time (D) = cb(Effort Applied)db [months]
People required (P) = Effort Applied / Development Time [count]
8.TYPES OF COCOMO MODEL
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, ...)
9.ITERATIONS COCOMO MODEL
10.INTERMEDIATE COCOMO
PRODUCT ATRIBUTES
HARDWARE ATRIBUTES
PERSONAL ATRIBUTES
PROJECT ATRIBUTES
11.PRODUCT ATRIBUTES
Required software reliability
Size of application database
Complexity of the product
12.HARDWARE ATRIBUTES
Run-time performance constraints
Memory constraints
Volatility of the virtual machine environment
Required turnabout time
13.PERSONAL ATRIBUTES
Analyst capability
Software engineering capability
Applications experience
Virtual machine experience
Programming language experience
14.PROJECT ATRIBUTES
Use of software tools
Application of software engineering methods
Required development schedule
15.GRAPH
SOFTWARE ENGINEERING Presentation Transcript:
1.SOFTWARE ENGINNERING
2. THE CONSTRUCTIVE COST MODEL
(COCOMO MODEL)
3.OUTLINE OF PRESENTATION
OVERVIEW
ARCHITECTURE OF COCOMO MODEL
BASIC CONCEPT OF COCOMO MODEL?
TYPES OF COCOMO MODEL
INTERMEDIATE COCOMO
ADVANTAGE OF COCOMO
DISADVANTAGE OF COCOMO
MULTIPLERS
COST DRIVERS
LIMITATIONS
CHARACTERISTICS OF COCOMO
CONCULSION
4.OVERVIEW
The Constructive Cost Model (COCOMO) is an algorithmic software cost estimation model developed by Barry W. Boehm
COCOMO was first published in Boehm's 1981 book Software Engineering Economics[1] as a model for estimating effort, cost, and schedule for software projects
5.ARCHITECTURE OF COCOMO MODEL
6.BASIC CONCEPT OF COCOMO MODEL
computes software development effort (and cost) as a function of program size. Program size is expressed in estimated thousands of source lines of code (SLOC)
COCOMO applies to three classes of software projects:
7.BASIC COCOMO EQUATION TAKE FORM
Effort Applied (E) = ab(KLOC)bb [ man-months ]
Development Time (D) = cb(Effort Applied)db [months]
People required (P) = Effort Applied / Development Time [count]
8.TYPES OF COCOMO MODEL
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, ...)
9.ITERATIONS COCOMO MODEL
10.INTERMEDIATE COCOMO
PRODUCT ATRIBUTES
HARDWARE ATRIBUTES
PERSONAL ATRIBUTES
PROJECT ATRIBUTES
11.PRODUCT ATRIBUTES
Required software reliability
Size of application database
Complexity of the product
12.HARDWARE ATRIBUTES
Run-time performance constraints
Memory constraints
Volatility of the virtual machine environment
Required turnabout time
13.PERSONAL ATRIBUTES
Analyst capability
Software engineering capability
Applications experience
Virtual machine experience
Programming language experience
14.PROJECT ATRIBUTES
Use of software tools
Application of software engineering methods
Required development schedule
15.GRAPH
No comments:
Post a Comment