1 / 7

COCOTS Presentation for CSCI 577 Fall 2006

COCOTS Presentation for CSCI 577 Fall 2006. Jesal Bhuta jesal@usc.edu. Outline. Modeling Context COCOTS Cost Sources Current Status Tool Demo. (COTS Components as Application Elements, Infrastructure, or Tools). COTS and Custom. Applications Components.

brendan-welch
Download Presentation

COCOTS Presentation for CSCI 577 Fall 2006

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. COCOTS Presentation for CSCI 577 Fall 2006 Jesal Bhuta jesal@usc.edu

  2. Outline • Modeling Context • COCOTS Cost Sources • Current Status • Tool Demo

  3. (COTS Components as Application Elements, Infrastructure, or Tools) COTS and Custom Applications Components ---------------- New Modeling Problem ---------------- COTS as Infrastructure COTS as Tools ( ( COCOMO II parms PVOL , PLEX ) COCOMO II parms LTEX , TOOL) Cost Modeling Currently Addressed Within COCOMO II: COTS as Infrastructure and Tools COTS Modeling Problem Context 1

  4. LCA LCO IOC ( preliminary ( re quirements ( system design review) review) delivery) 3. COTS Glue Code Development 2. COTS 1. COTS Tailoring Assessment Staffing Application Code Development, Integration, and Test Separate from COTS Effects Time COCOTS Effort Estimate LCO – Lifecycle Objectives LCA – Lifecycle Architecture IOC – Initial Operational Capability COCOMO II Effort Estimate COCOTS Cost Sources

  5. About COCOTS • Three Sub-models • Assessment sub-model • Tailoring sub-model • Glue code sub-model • Mathematical form of each sub-model is different • However, a common feature is estimates based upon classes of COTS components being examined • Example COTS classes: GUI builders, operating systems, databases, word processors, etc • See demo later

  6. COCOTS Architecture

  7. Current Status • Calibrated on 20 data points • Project Domains • Air Traffic Management • Business (including databases) • Communication, Navigation, & Surveillance • Logistics • Mission Planning • Operations • Web-based Maps

More Related