University of Southern California Center for Systems and Software Engineering February 13, 2007©USC-CSSE1 Acquisition and Contracting Mismatches Barry.

Slides:



Advertisements
Similar presentations
Chapter 22 Product Line Engineering Week 1 CIS 673.
Advertisements

University of Southern California Center for Systems and Software Engineering A Look at Software Engineering Risks in a Team Project Course Sue Koolmanojwong.
University of Southern California Center for Systems and Software Engineering Design-Code Review Preparation Pongtip Aroonvatanaporn CSCI577b Spring 2012.
University of Southern California Center for Systems and Software Engineering SoS Engineering and the ICM Workshop Overview Jo Ann Lane USC CSSE
NDIA Software Industry Experts Panel Paul R. Croll, Chair NDIA Systems Engineering Division Meeting 24 June 2008.
Proposed Way Forward for SERC EM Task Barry Boehm, USC-CSSE 30 January 2009.
University of Southern California Center for Systems and Software Engineering USC CSSE Research Overview Barry Boehm Sue Koolmanojwong Jo Ann Lane Nupul.
University of Southern California Center for Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 3/18/08 (Systems and) Software Process Dynamics Ray Madachy USC.
University of Southern California Center for Systems and Software Engineering Issues and Recommendations Emanating from the Management Issues Group of.
University of Southern California Center for Software Engineering CSE USC 12/6/01©USC-CSE CeBASE: Opportunities to Collaborate Barry Boehm, USC-CSE Annual.
Software and System Engineering Integration Sponsor Overview Kristen Baldwin Deputy Director, Software Engineering and System Assurance Office of the Under.
University of Southern California Center for Systems and Software Engineering Integrating Systems and Software Engineering (IS&SE) with the Incremental.
Pratt & Whitney National Workshop on Aviation Software Systems for the Second Century of Flight: Design for Certifiably Dependable Systems October 5-6,
University of Southern California Center for Software Engineering CSE USC ©USC-CSE 10/23/01 1 COSYSMO Portion The COCOMO II Suite of Software Cost Estimation.
Affiliate Feedback and Discussion 1. Future Research: COSYSMO Updated data collection effort Quantifying the effect of schedule Harmonizing across software.
May 11, 2004CS WPI1 CS 562 Advanced SW Engineering Lecture #5 Tuesday, May 11, 2004.
USC Annual Research Review - March 2006 University of Southern California Center for Software Engineering Software Architecting On the Acquisition Side.
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy, Barry Boehm USC Center for Systems and Software Engineering.
2/13/07(c) USC-CSSE1 An Empirical Study on MBASE and LeanMBASE Supannika Koolmanojwong Center for Systems and Software Engineering CSSE- Annual Research.
University of Southern California Center for Systems and Software Engineering SoS Engineering and the ICM Workshop Overview Jo Ann Lane USC CSSE
Introduction Wilson Rosa, AFCAA CSSE Annual Research Review March 8, 2010.
University of Southern California Center for Systems and Software Engineering Assessing the IDPD Factor: Quality Management Platform Project Thomas Tan.
1 CORADMO in 2001: A RAD Odyssey Cyrus Fakharzadeh 16th International Forum on COCOMO and Software Cost Modeling University of Southern.
1 COSYSMO Workshop - Survey on Intuitive Judgments (Part III) COSYSMO = 1,000 PM Historical data = 1,100 PM COSYSMO = 100 PM Historical data = 110 PM.
University of Southern California Center for Systems and Software Engineering 1 November 2010 Mauricio Peña Dr. Ricardo Valerdi CHARACTERIZING THE IMPACT.
1 Software Testing and Quality Assurance Lecture 14 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
University of Southern California Center for Systems and Software Engineering Decision Support for Value-Based Software Testing Framework Qi Li, Barry.
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 Reuse and Maintenance Estimation Vu Nguyen March 17, 2009.
Recent Trends in DoD Systems and Software Engineering Processes Bruce Amato Acting Deputy Director, Software Engineering and Systems Assurance Office of.
University of Southern California Center for Software Engineering CSE USC 9/14/05 1 COCOMO II: Airborne Radar System Example Ray Madachy
USC CSSE Top 10 Risk Items: People’s Choice Awards Barry Boehm, Jesal Bhuta USC Center for Systems & Software Engineering
University of Southern California Center for Systems and Software Engineering July 2008ICM and CP Workshop © USC-CSSE1 Initial Competitive Prototyping.
University of Southern California Center for Software Engineering C S E USC Agile and Plan-Driven Methods Barry Boehm, USC USC-CSE Affiliates’ Workshop.
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 An Analysis of Changes in Productivity and COCOMO Cost.
University of Southern California Center for Systems and Software Engineering Integrating Systems and Software Engineering: Complex Systems Workshop 29.
 Software Software  Program vs Software Products Program vs Software Products  Software Characteristics Software Characteristics  Software Crisis.
CS 577b Software Engineering II -- Introduction
Project Management Planning and Control Techniques  5th Edition u ISBN: u Rory Burke.
1 First, some interesting numbers: ~2,000 ~80 2 >200 [To be defined on March 23]
University of Southern California Center for Software Engineering C S E USC August 2001©USC-CSE1 CeBASE Experience Base (eBASE) -Shared Vision Barry Boehm,
University of Southern California Center for Systems and Software Engineering GQM, GQM+ Supannika Koolmanojwong CSCI577 Spring 2013 (C) USC-CSSE1.
Institut Experimentelles Software Engineering Fraunhofer IESE Klaus Schmid Relating Product Line Adoption Mode and Transition Process.
University of Southern California Center for Systems and Software Engineering The Incremental Commitment Spiral Model Electronic Process Guide (EPG) and.
ESA/ESTEC, TEC-QQS August 8, 2005 SAS_05_ESA SW PA R&D_Winzer,Prades Slide 1 Software Product Assurance (PA) R&D Road mapping Activities ESA/ESTEC TEC-QQS.
University of Southern California Center for Systems and Software Engineering 7/19/2013(c) USC-CSSE11 USC e-Services Software Engineering Projects.
What is it? A risk is a potential problem — it might happen, it might not. But, regardless of the outcome, it’s a really good idea to identify it. Assess.
Introduction to availability modelling in ELMAS Arto Niemi.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6 Barry.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
University of Southern California Center for Systems and Software Engineering Metrics Organizational Guidelines [1] ©USC-CSSE1 [1] Robert Grady, Practical.
Review of Software Process Models Review Class 1 Software Process Models CEN 4021 Class 2 – 01/12.
CS 577b Software Engineering II -- Introduction
University of Southern California Center for Systems and Software Engineering Vu Nguyen, Barry Boehm USC-CSSE ARR, May 1, 2014 COCOMO II Cost Driver Trends.
University of Southern California Center for Systems and Software Engineering 7/13/2012(c) USC-CSSE11 USC e-Services Software Engineering Projects.
University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE CSCI577B 2010 Light Weight Sw Engg for Off-the-Books.
University of Southern California Center for Software Engineering CSE USC SCRover Increment 3 and JPL’s DDP Tool USC-CSE Annual Research Review March 16,
Software Project Management Lecture # 6. Outline Recap Remaining Topics of Chapter 23 Project Scheduling (Chapter 24)
Systems/Software ICM Workshop Acquisition and Process Issues Working Group Rick Selby and Rich Turner Systems/Software ICM Workshop July 14-17, 2008 Washington.
SoS Process, Acquisition, Management Critical Success Factors Workshop Jo Ann Lane, Richard Turner, USC.
Engineer Exceptionally Capable Project Teams February 2012.
University of Southern California Center for Systems and Software Engineering ICSM Stage II: Phases and Continuing Project Example Anandi Hira CS 510,
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Fall 2010 Software Planning Guidelines.
Rick Selby Software Products, Northrop Grumman & Adjunct Faculty, University of Southern California Los Angeles, CA Candidate member Main empirical research.
CS 577b: Software Engineering II
Agile Culture Instructor Pilot ISA 301 March 2017 Robert Thomas.
CLE Introduction to Agile Software Acquisition
For University Use Only
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Decision Tree.
Presentation transcript:

University of Southern California Center for Systems and Software Engineering February 13, 2007©USC-CSSE1 Acquisition and Contracting Mismatches Barry Boehm, Roberta Gleiter, Gary Hafen, DeWitt Latimer, Rich Turner Gary Thomas, Glenn Berg

University of Southern California Center for Systems and Software Engineering February 13, 2007©USC-CSSE2 Research Project Ideas A.Taxonomy of software project contract efforts B.Study of successful contracts to find commonalities in software projects C.Top acquisition risk list (acquirer/contractor point of views) D.Inventory current acquisition practices on acquirer and contractor sides E.Map risks to practices to determine coverage and gaps in practice F.Quantify the impact/cost of the turn-over of acquisition personnel G.Look at acquisition risks – do a risk model of what we learn. H.Develop fault tree analysis of to know the probability of success of the program at a given point I.Tool that help you quantify s/w (or system) opportunities and risks over time and impact of missing these J.Do something like “100 Questions for Technical Review” for software intensive systems acquisition K.How often do our acquisition re-use based assumptions work out? L.Is amount of code a part of complexity for acquisition? M.Macro risk project tool – evolve and pilot N.How would an acquisition organization write an acquisition strategy for a development based on MBASE and incremental commitment Blue – High Value/High DifficultyGreen – High Value/Low Difficulty

University of Southern California Center for Systems and Software Engineering February 13, 2007©USC-CSSE3 s1 C A M E D K L B G N J F H I

University of Southern California Center for Systems and Software Engineering February 13, 2007©USC-CSSE4 Transition Projects MBASE to a standard format (for injection into standards bodies) Write a standard around the Incremental Commitment Model