USC CSSE Top 10 Risk Items: People’s Choice Awards Barry Boehm, Jesal Bhuta USC Center for Systems & Software Engineering

Slides:



Advertisements
Similar presentations
Incremental Commitment Spiral Model, Expedited Engineering, and Kanban Jo Ann Lane and Alexey Tregubov USC CSSE Rich Turner Stevens University.
Advertisements

Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
University of Southern California Center for Systems and Software Engineering A Look at Software Engineering Risks in a Team Project Course Sue Koolmanojwong.
W5HH Principle As applied to Software Projects
USC CSSE Workshop Overview: Top 3 Software-Intensive Systems Risk Items Barry Boehm, USC-CSSE February 14, 2007
3/14/2006USC-CSE1 Ye Yang, Barry Boehm Center for Software Engineering University of Southern California COCOTS Risk Analyzer and Process Usage Annual.
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.
OTS Integration Analysis using iStudio Jesal Bhuta, USC-CSE March 14, 2006.
University of Southern California Center for Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
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.
Presentation R. R. Lutz. Analyzing Software Requirements Errors in Safety-Critical Embedded Systems. In Proceedings of the IEEE International Symposium.
Process Synchronization Workshop Summary Report Jo Ann Lane University of Southern California Center for Software Engineering.
System-of-Systems Cost Modeling: COSOSIMO July 2005 Workshop Results Jo Ann Lane University of Southern California Center for Software Engineering.
Estimating System of Systems Engineering (SoSE) Effort Jo Ann Lane, USC Symposium on Complex Systems Engineering January 11-12, 2007.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
University of Southern California Center for Software Engineering CSE USC Distributed Assessment of Risk Tool DART Jesal Bhuta
University of Southern California Center for Software Engineering CSE USC 9/14/05 1 COCOMO II: Airborne Radar System Example Ray Madachy
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
COSOSIMO* Workshop Outbrief 14 March 2006 Jo Ann Lane University of Southern California Center for Software Engineering CSE.
Course Retrospective Richard Anderson CSE 403 Lecture 27.
A METHOD FOR COMPATIBLE COTS COMPONENT SELECTION (BHUTA, J., BOEHM, B., 2005) Nikos Argyropoulos
SVEN FORTUIN ( ) A Method for Compatible COTS Component Selection BARRY BOEHM UNIVERSITY OF SOUTHERN CALIFORNIA JESAL BHUTA UNIVERSITY OF SOUTHERN.
COCOMO-SCORM: Cost Estimation for SCORM Course Development
Organizing Information Technology Resources
Introduction to Software Quality Assurance (SQA)
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
University of Southern California Center for Systems and Software Engineering Incremental Commitment Spiral Model (ICSM) for CS 577 Barry Boehm, Supannika.
University of Southern California Center for Systems and Software Engineering Rapid Fielding Projects in CSCI 577 Supannika Koolmanojwong Barry Boehm CS.
1. 2 Tier I/II $Ks Tier III/IV $Ms Tier V/VI $Bs Create New Vulnerabilities Discover New Vulnerabilities Exploit Known Vulnerabilities.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Topic Cafeteria Management System GROUP : 9 TEAM 1.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Pre-Project Components
Implementing SiteManager in a non-P/L/C State Dawn E. Scheel, P.E. TxDOT.
Project & Risk Management For next class -- Pressman: 3, , 5.8, , 6.6 Introductions Software Development Processes Software Maturity Models.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
Effort Estimation In WBS,one can estimate effort (micro-level) but needed to know: –Size of the deliverable –Productivity of resource in producing that.
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,
CS223: Software Engineering Lecture 2: Introduction to Software Engineering.
Risk Analysis 19 th September, Risk vs. Problem Risk  An “uncertain event that “may” happen with some probability Problem  The above event.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
IT323 - Software Engineering 2 1 Tutorial 4.  List the main benefits of software reuse 2.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
University of Southern California Center for Systems and Software Engineering Enablers and Inhibitors for Expediting Systems and Software Engineering &
© 2016 The Aerospace Corporation Agile Fit Check Framework Outbrief Supannika Koolmanojwong Mobasser The Aerospace Corporation USC CSSE Annual Research.
Estimation Questions How do you estimate? What are you going to estimate? Where do you start?
1 Agile COCOMO II: A Tool for Software Cost Estimating by Analogy Cyrus Fakharzadeh Barry Boehm Gunjan Sharman SCEA 2002 Presentation University of Southern.
Advanced Software Engineering Dr. Cheng
Rick Selby Software Products, Northrop Grumman & Adjunct Faculty, University of Southern California Los Angeles, CA Candidate member Main empirical research.
Introduction to Systems Analysis and Design
CS 577b: Software Engineering II
Project Cost Management
Pragmatics 4 Hours.
Platform as a Service (PaaS)
Top Risks and Prototypes
Using the Incremental Commitment Model (ICM) Process Decision Table
Affordability-Based Engineering
Agile Fit Check Framework Outbrief
Software Systems Cost Estimation
Using the Incremental Commitment Model (ICM) Process Decision Table
COSYSMO Delphi Round 2 Results
More on Estimation In general, effort estimation is based on several parameters and the model ( E= a + b*S**c ): Personnel Environment Quality Size or.
Distributed Assessment of Risk Tool DART
Extreme Programming Frank Bergmann,
Comparison between each special case
Working Group Meeting Report
University of Southern California Center for Software Engineering
Presentation transcript:

USC CSSE Top 10 Risk Items: People’s Choice Awards Barry Boehm, Jesal Bhuta USC Center for Systems & Software Engineering {boehm,

2 Survey: Early Statistics  Number or Surveys: 25  Average Experience: ~28 years (6 years – 51 years)  Area Distribution: –Software: 20 –Systems: 17 –Hardware: 0  Business Domain Distribution: –Aerospace: 18 –Software Infrastructure: 5 –Business: 4 –Telecom: 3 –Others: Secure Apps (1); Safety Critical Apps (1); C4ISR (1)

3 The Nominees are …  Acquisition and contracting process mismatches  Architecture complexity; quality tradeoffs  Budget and schedule constraints  COTS and other independently evolving systems  Customer-developer-user team cohesion  Migration complexity  Personnel shortfalls  Process maturity  Requirements mismatch  Requirements volatility; rapid change  Technology maturity  User interface mismatch

4 And the Winner is….

5 Additional Recommended Risk Item Nominees  Non functional requirements engineering (1)  Risk management (or lack thereof) (2)  Inadequacy of current architecture frameworks and SOE methodologies (1)

6 Risk List & Survey Now Online  Check risk updates at: –  If you know of interested parties who would like to contribute they can survey online at: –