Systems Development Life CycleWhat's wrong with COCOMO II, the toolICM/RUP -- ICM for software systemsICM for Software Intensive Systems & Systems of SystemsWhat's Not Right with the COCOMO II.2003 Tool- No Inception (or Exploration+Valuation); no Transition- Name-space pollution- No way to easily play what if's (remembering)- Written in C; hard to extend; only for Windows- No incremental/multi-build: single Elaboration/Construction--RUP & ICM Anchor Points Enable Concurrent Eng'gICM LC Processes for Systems (Hw, Sw & Pw)ICM Activity Categories and Level of EffortWhy Multiple Build Software SystemsSimplest: Early Functionality in the hands of ALL users- Architecture/Core plus some functionality in first build- Implies Architecture covers Evolution Requirements Full Qualification/Acceptance Testing each buildIncreasingly Complex- Multiple, diverse "platforms"- Different "foci" of functionality- Network Centric Systems Operation Evolution/federation of legacy systems System of Systems by designOverlaps across Software BuildsICM Showing Multi-Build Software in SystemsICM Showing Multi-Build Software in SIS Systems with Competitive PrototypingOutlineCOINCOMO BackgroundAlready accomplished, but clumsy:- COCOMO + COPSEMO (done in 2000)- DBA DBA COCOMO (done in 2003)COINCOMO Vision (completed in 2007)COCOMO II with COPSEMO (for I&T)COPSEMO: Phased Schedule and Effort Dist.VisionCOINCOMO Direction – 1aCOCOMO + COPSEMOCOINCOMO Direction – 1bCOCOMO + COPSEMO:COINCOMO Direction – 2Multiple Build Capability from DBA COCOMOMulti-Build COCOMO II COINCOMO Sums Across Builds For Est.Multiple SubSystems' Overlapping BuildsCOINCOMO Structures/Models (UML)COCOMO + COPSEMOMultiple types per moduleCOCOMO Models Represented in UMLCOCOMO.II.2003 (the software package)COINCOMO.2008 version of COCOMO.II.2003- Has concept of stored alternatives for Components (AKA Project) [shown] EAF and SF Driver sets [not shown] Sub-Components (AKA Modules) [not shown]- Has four SLOC sources: SLOC or FP converted to SLOC: New & New Open Source Adaptation Only: New Reused & Previous Build ReusedCOINCOMO version of COCOMO.II.2003 with COPSEMOCOCOMO.II.2003 in UMLCOINCOMO's COCOMO.II.2003 in UMLCOINCOMO's COCOMO + COPSEMO in UMLAccomplishments So FarPostgress database; Java front endCOCOMO+COPSEMO (spreadsheet output easing overlaps)COSECMO extension (but base model has now changed)Starting on CORADMO (a base for COAGLMO?)Demonstrated using gedanken multi-build F6So WhatAn opportunity for Directed Research involvement in- New development- Testing- Generating user manuals- ...University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO COINCOMOA Winsor [email protected] by Marilee Wheaton© 2005-09 AWBrown BES/MSEE & USC CSSE 1 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO Systems Development Life CycleWhat's wrong with COCOMO II, the toolICM/RUP -- ICM for software systemsICM for Software Intensive Systems & Systems of Systems© 2005...2009 AWBrown BES/MSEE & USC CSSE 2 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO What's Not Right with the COCOMO II.2003 Tool- - - - - - - © 2005...2009 AWBrown BES/MSEE & USC CSSE 3 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO RUP & ICM Anchor Points Enable Concurrent Eng'g11 (efforts not to scale)© 2005...2009 AWBrown BES/MSEE & USC CSSE 4 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO ICM LC Processes for Systems (Hw, Sw & Pw)© 2005...2009 AWBrown BES/MSEE & USC CSSE 5 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO ICM Activity Categories and Level of Effort© 2005...2009 AWBrown BES/MSEE & USC CSSE 6 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO Why Multiple Build Software SystemsSimplest: Early Functionality in the hands of ALL users- Architecture/Core plus some functionality in first build- Implies  Architecture covers Evolution Requirements Full Qualification/Acceptance Testing each buildIncreasingly Complex- Multiple, diverse "platforms"- Different "foci" of functionality- Network Centric Systems Operation  Evolution/federation of legacy systems System of Systems by design© 2005...2009 AWBrown BES/MSEE & USC CSSE 7 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO Overlaps across Software BuildsInception Elaboration Construction TransitionInception Elaboration Construction TransitionEvolve During Transition [After Sw IOC]Possible Overlapping Software Development SpiralsEvolve After Architecture CompleteIncept. Elaboration Construction TransitionInception Elaboration with Evol. Req. Construction TransitionI. Elab. Construction Transition. . .Traditional Deliver And EnhanceInception Elaboration Construction TransitionInception Elaboration Construction Transition© 2005...2009 AWBrown BES/MSEE & USC CSSE 8 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO ICM Showing Multi-Build Software in Systems© 2005...2009 AWBrown BES/MSEE & USC CSSE 9 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO ICM Showing Multi-Build Software in SIS Systemswith Competitive Prototyping© 2005...2009 AWBrown BES/MSEE & USC CSSE 10 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO OutlineFundamentalsCurrent VisionCOINCOMO© 2005...2009 AWBrown BES/MSEE & USC CSSE 11 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO COINCOMO BackgroundAlready accomplished, but clumsy:- COCOMO + COPSEMO (done in 2000)- DBA DBA COCOMO (done in 2003)COINCOMO Vision (completed in 2007)© 2005...2009 AWBrown BES/MSEE & USC CSSE 12 of 27 1/14/2019University of Southern CaliforniaCenter for Systems and Software Engineering Constructive Incremental COCOMO COCOMO II