slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
COCOMO II: Airborne Radar System Example PowerPoint Presentation
Download Presentation
COCOMO II: Airborne Radar System Example

Loading in 2 Seconds...

play fullscreen
1 / 19

COCOMO II: Airborne Radar System Example - PowerPoint PPT Presentation


  • 223 Views
  • Uploaded on

COCOMO II: Airborne Radar System Example. Barry Boehm CSCI 510 Fall 2012. Outline. Overview the Airborne Radar System (ARS) Demonstrate progressive usage of different COCOMO sub-models within an evolutionary spiral development process

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'COCOMO II: Airborne Radar System Example' - sonia-roy


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1

COCOMO II: Airborne Radar System Example

Barry Boehm

CSCI 510

Fall 2012

outline
Outline
  • Overview the Airborne Radar System (ARS)
  • Demonstrate progressive usage of different COCOMO sub-models within an evolutionary spiral development process
  • Cover estimation of reuse, modification, COTS, and automated translation
  • Show how an aggregate estimate is refined in greater detail
ars estimation
ARS Estimation
  • Use Applications Composition, Early Design and Post-Architecture submodels
  • Two Post-Architecture estimates are demonstrated: top-level and detailed
    • scale drivers apply to overall system in both estimates
    • cost drivers are rated for the aggregate system in the top-level estimate (17 ratings)
    • cost drivers are refined for each individual software component in the detailed estimate (17*6 components=102 ratings)
software components
Software Components
  • Radar Unit Control
    • controls radar hardware
  • Radar Item Processing
    • extracts information from returned radar to identify objects
  • Radar Database
    • maintains radar object tracking data
  • Display Manager
    • high level displays management
  • Display Console
    • user input device interface and primitive graphic processing
  • Built In Test
    • hardware monitoring and fault localization
cocomo coverage in evolutionary lifecycle process
COCOMO Coverage in Evolutionary Lifecycle Process

* both top-level and detailed estimates shown

prototype size and effort
Prototype Size and Effort

Productivity is “high” at 25 NAP/PM

Effort = NAP/ Productivity = 136.3/25 = 5.45 PM (or 23.6 person-weeks)

Personnel = 23.5 person-weeks/6 weeks ~ 4 full-time personnel

scale factors for breadboard
Precedentedness (PREC)

Development Flexibility (FLEX)

Risk/Architecture Resolution (RESL)

Team Cohesion (TEAM)

Process Maturity (PMAT)

Nominal

Low

High

Nominal

Nominal

Scale Factors for Breadboard

Factor Rating

early design cost drivers for breadboard
High

Very High

High

High

Nominal

Nominal

Nominal

Product Reliability and Complexity (RCPX)

Required Reuse (RUSE)

Platform Difficulty (PDIF)

Personnel Capability (PERS)

Personnel Experience (PREX)

Facilities (FCIL)

Schedule (SCED)

Early Design Cost Drivers for Breadboard

Factor Rating

ars full development for ioc
ARS Full Development for IOC
  • Use Post-Architecture estimation model
    • same general techniques as the Early Design model for the Breadboard system, except for elaborated cost drivers
  • Two estimates are demonstrated: top-level and detailed
    • scale drivers apply to overall system in both estimates
    • cost drivers are rated for the aggregrate system in the top-level estimate (17 ratings)
    • cost drivers are refined for each individual software component in the detailed estimate (17*6 components=102 ratings)
summary and conclusions
Summary and Conclusions
  • We provided an overview of the ARS example provided in Chapter 3
  • We demonstrated using the COCOMO sub-models for differing lifecycle phases and levels of detail
    • the estimation model was matched to the known level of detail
  • We showed increasing the level of component detail in the Post-Architecture estimates
  • Incremental development was briefly covered