University of Southern California Center for Systems and Software Engineering COSYSMO 3.0: Workshop Results Annual Research Review March 17, 2016 03/16.

Slides:



Advertisements
Similar presentations
ISPA 4/5/04 1 Systems Engineering Sizing Via Requirements Ricardo Valerdi, USC Center for Software Engineering Viterbi School of Engineering ISPA Southern.
Advertisements

Exam and revision techniques. 1. To describe the main EU institutions. 2. To identify the differing sources of EU law and their impacts. 3. To explain.
Planning at CMM level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements Engineering.
1 Chapter 2: Product Development Process and Organization Introduction Importance of human resources: Most companies have similar technology resources.
Effective Teamwork Farrokh Alemi, Ph.D.. What do you like about teams? What needs improvement? Takes too much time Rewards popularity not good ideas Many.
MEETINGS. Commonly used words/expressions: call call arrange arrange schedule schedule hold hold cancel cancel postpone (put off) postpone (put off) reschedule.
3GPP TSG RAN WG 4 Meeting #1 Howard Benn Convenor Tdoc TSG R4#1(99)018.
University of Southern California Center for Systems and Software Engineering Next Generation Estimation Methods and Management Metrics: Working Group.
COSYSMO 2.0 Workshop Summary (held Monday, March 17 th 2008) USC CSSE Annual Research Review March 18, 2008 Jared Fortune.
The Comparison of the Software Cost Estimating Methods
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy, Ricardo Valerdi USC Center for Systems and Software.
3/14/2006USC-CSE1 Ye Yang, Barry Boehm Center for Software Engineering University of Southern California COCOTS Risk Analyzer and Process Usage Annual.
March 2002 COSYSMO: COnstructive SYStems Engineering Cost MOdel Ricardo Valerdi USC Annual Research Review March 11, 2002.
University of Southern California Center for Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.
11/08/06Copyright 2006, RCI1 CONIPMO Workshop Out-brief 21 st International Forum on COCOMO and Software Cost Modeling Donald J. Reifer Reifer Consultants,
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.
1 Introduction to Software Engineering Lecture 42 – Communication Skills.
Self Evaluation and Reporting using TDM CA Anne Abramson Center for Social Services Research UC Berkeley Jana Rickerson Technical Assistant (TDM) Annie.
1 CORADMO in 2001: A RAD Odyssey Cyrus Fakharzadeh 16th International Forum on COCOMO and Software Cost Modeling University of Southern.
System-of-Systems Cost Modeling: COSOSIMO July 2005 Workshop Results Jo Ann Lane University of Southern California Center for Software Engineering.
1 Discussion on Reuse Framework Jared Fortune, USC Ricardo Valerdi, MIT COSYSMO COCOMO Forum 2008 Los Angeles, CA.
Estimating System of Systems Engineering (SoSE) Effort Jo Ann Lane, USC Symposium on Complex Systems Engineering January 11-12, 2007.
Expert COSYSMO Update Raymond Madachy USC-CSSE Annual Research Review March 17, 2009.
COCOMO II Database Brad Clark Center for Software Engineering Annual Research Review March 11, 2002.
“Annual” Report u Section 1: Mission Statement v v State the original mission statement of company (include markets served, how served, and key resources.
COSOSIMO* Workshop Outbrief 14 March 2006 Jo Ann Lane University of Southern California Center for Software Engineering CSE.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 An Analysis of Changes in Productivity and COCOMO Cost.
12/9-10/2009 TGDC Meeting TGDC Recommendations Research as requested by the EAC John P. Wack National Institute of Standards and Technology
CH07: Writing the Programs Does not teach you how to program, but point out some software engineering practices that you should should keep in mind as.
District Improvement Facilitators Network January 30,
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Software Design Processes and Management.
Estimation Chapter 3 Applied Software Project Management, Stellman & Greene.
University of Southern California Center for Systems and Software Engineering COSATMO/COSYSMO Workshop Jim Alstad, USC-CSSE Gan Wang, BAE Systems Garry.
Wideband Delphi Technique George Ukkuru. Introduction Consensus based approach for estimation Developed in the 1940’s at Rand Corporation Team of experts.
HIGH SCHOOL PROJECT PLANNING MEETING October 14, 2013 Crabtree, Rohrbaugh & Associates, Architects Agenda Schematic Design Concept D Option – 1 Site Floor.
Doc.: IEEE /012r0 Submission March 2003 Jim Lansford, MobilianSlide 1 Project: IEEE P Coexistence TAG Submission Title: March 2003 SEC Meeting.
Introduction to Requirements Eng. Copyright, 2001 © Jerzy R. Nawrocki Requirements.
G544 – Practical project SELF REPORT. Revision  Socrative quiz  In pairs – answer each question.  We will then discuss each answer given.
2016 Caucus Training Pooled Caucuses PCO Hosted Caucuses.
JACTest Monitoring Center Test Monitoring Center Report to the Mack Test Surveillance Panel June 17, 2002 Montreal.
Doc.: IEEE /224r3 Submission May 2001 Tom Siep, TMS ConsultantsSlide 1 TG3 Review Procedure Proposal NOTE: All of these recommendations do not.
Overview of Addressing Risk with COSYSMO Garry Roedler & John Gaffney Lockheed Martin March 17, 2008.
University of Southern California Center for Systems and Software Engineering Core Capability Drive-Through Preparation Pongtip Aroonvatanaporn CSCI 577b.
Standard Design Process Overview
Chapter 11: Project Risk Management Information Technology Project Management, Fifth Edition.
Proprietary and confidential. Do not distribute.Deck Title1 May, 2016 DG CONNECT European Catalogue KEY RULES & DECISION MAKING Trilateral: Monica Lagazio,
Committee Ballots for Documents Shannon Banchero, Manager, Technical Documents Jerzy Zemajtis, Senior Engineer.
9101 Forms July 20-21, Revision Team Paul Dionne
SRA Memory Grabber Product Description.
Management & Planning Tools
COSYSMO 3.0: The Expert-Based Model with Workshop Report
Status Report Jim VanGaasbeek Ricardo Valerdi
Unit 36: Internet Server Management
2018/9/ /9/14 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: TG4i May 2011 Closing report Date.
BUS 308 HELPS Education for Service-- bus308helps.com.
CMGT 431 STUDY Education for Service- -cmgt431study.com.
Progressive Shift Parameters Worksheet
ServiceNow Assessments
COCOMO II Security Extension Workshop Report
Software Cost estimation
OREGON Ballot Measure Process
COSYSMO Delphi Round 2 Results
How to Run an Annual General Meeting
TG3 Review Procedure Proposal
Our Patient Participation Group needs YOUR views!
Working Group Meeting Report
University of Southern California Center for Software Engineering
COSYSMO: Constructive Systems Engineering Cost Model
Center for Software and Systems Engineering,
Presentation transcript:

University of Southern California Center for Systems and Software Engineering COSYSMO 3.0: Workshop Results Annual Research Review March 17, /16 1 Jim AlstadUSC Center for Systems and Software Engineering Jim

University of Southern California Center for Systems and Software Engineering Workshop Agenda 03/162 Tentative agenda: 13:00 Attendee introductions 13:15 Detailed introduction to the model and to workshop techniques 13:30 Delphi round 1 15:00 Break 15:30 Delphi round 2 16:30 Closing discussions 17:00 End

University of Southern California Center for Systems and Software Engineering Workshop Materials 03/163 Main presentation (from this morning) Workshop presentation (this presentation) Model document Delphi voting form

University of Southern California Center for Systems and Software Engineering Wideband Delphi Procedure 03/164 Ballots available via: – (Excel) –Memory stick (Excel) –Paper Round 1 –Moderator goes over the parameters in the model –Each voter fills in a ballot with her opinion as to the correct value of the parameter –Ballots are anonymous –No discussion –When complete, ballots are turned in to moderator Later round –Moderator assembles results of voting and presents to group –Moderator leads group discussion of results –Voters fill in a new ballot with possibly revised parameter values

University of Southern California Center for Systems and Software Engineering Context for this Delphi (1/2) 03/165 Productivity range (“EMR”): –Ratio of the numerically highest value for a cost driver to its numerically lowest value –Is a measure of the impact of the cost driver –Recommended voter concept: “Considering the project with the best rating on this parameter to the project with the worst rating, what is the productivity ratio due to this parameter?” Some commentators have suggested that the EMRs as a group are too large –I.e., the product of all EMRs is too large –Consequence can be that, for example, going from Nominal to High (one step) causes too big a change in the estimate

University of Southern California Center for Systems and Software Engineering Context for this Delphi (2/2) 03/166 One commentator suggests that a low capability team (Personnel/Team Capability) may also have low CONOPS and Requirements Understanding and low Architecture Understanding, leading to an unwarranted high value for the product of these. –Currently, product of EMRs = 19.66

University of Southern California Center for Systems and Software Engineering Discussion Topix 03/167 Jim/Winsor: With/without Interoperability –Jim: Nominal should be the same Resolved: Jim’s misunderstanding: two “separate” tables –Winsor: No further discussion needed Jim: Somebody lowered all Cost Drivers –Resolve: We’ve discussed this. Our opinions will go into Round 2 Winsor/Hunter: Scale factors: Lower base, increase RV –Resolve: Allow scale factors to be +/-, including RV. Allow for asymmetry. Marilee: # Recursive Levels –Not for group resolution Jim: Statement for RV –Resolve: Use perdcentages