cosysmo reuse extension cosysmo workshop usc csse annual research review march 17 2008 l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
COSYSMO Reuse Extension COSYSMO Workshop – USC CSSE Annual Research Review March 17, 2008 PowerPoint Presentation
Download Presentation
COSYSMO Reuse Extension COSYSMO Workshop – USC CSSE Annual Research Review March 17, 2008

Loading in 2 Seconds...

play fullscreen
1 / 10

COSYSMO Reuse Extension COSYSMO Workshop – USC CSSE Annual Research Review March 17, 2008 - PowerPoint PPT Presentation


  • 114 Views
  • Uploaded on

COSYSMO Reuse Extension COSYSMO Workshop – USC CSSE Annual Research Review March 17, 2008. Overview. Background COSYSMO currently assumes all system components are new …but most systems are not entirely new, have a significant amount of reuse

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 'COSYSMO Reuse Extension COSYSMO Workshop – USC CSSE Annual Research Review March 17, 2008' - katherine


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
overview
Overview

Background

  • COSYSMO currently assumes all system components are new
    • …but most systems are not entirely new, have a significant amount of reuse
  • Current goal is to develop an approach for handling reuse
    • Organizations can adapt to their own business model

Objectives

  • Provide an overview of research
    • Proposed terminology
    • Possible methodology
  • Identify next steps
background on software reuse
Background on Software Reuse

Main size driver = KSLOC

  • Adapted Source Lines of Code (ASLOC)
  • Percent of Design Modification (DM)
  • Percent of Code Modification (CM)
  • Percent of Integration Required for Modified Software (IM)
  • Percentage of reuse effort due to Software Understanding (SU)
  • Percentage of reuse effort due to Assessment and Assimilation (AA)
  • Programmer Unfamiliarity with Software (UNFM)

AAF

From COCOMO II Model Definition Manual (p. 7-11)

proposed reuse terminology
Proposed Reuse Terminology
  • New:
    • Items that are completely new, generally unprecedented and with low level of familiarity
  • Modified:
    • Items that are inherited, but require a limited amount of tailoring to be incorporated
  • Adopted:
    • Items that are incorporated unmodified, “black-box” reuse
  • Deleted:
    • Items that are removed from a system (in legacy but not current system)
  • Managed:
    • Items incorporated unmodified and untested (subcontractor effort)
reuse continuum
Reuse Continuum

1.0

New

Modified

Deleted

Adopted

Reuse weight

Managed

0

approaches for handling reuse in cosysmo
Approaches for Handling Reuse in COSYSMO

Reuse

Capture reuse-class cost parameters

for different classes of reuse

Calculate equivalent requirements

weights for size drivers

Activity-based/Bottoms up

(requires effort data by activity)

Solve for the weights

(requires data from projects)

next steps
Next Steps
  • Reach conclusion on reuse weights
    • Thoughts on bottoms up calculations vs. solving for weights?
  • Determine scalability of reuse
    • How to deal with commonalities across multiple projects/organizations?
  • Examine effect of SE “designed” for reuse
    • What are the penalty/savings? Where do they occur in lifecycle?
  • Apply methodology
    • Who else has reuse data?
author contact information
Author Contact Information

Ricardo Valerdi, MIT

rvalerdi@MIT.edu

Gan Wang, BAE Systems gan.wang@baesystems.com

Garry Roedler, Lockheed Martingarry.j.roedler@lmco.com

John Rieff, RaytheonJohn_E_Rieff@raytheon.com

Jared Fortune, USC

fortune@usc.edu