University of Southern California Center for Systems and Software Engineering Enablers and Inhibitors for Expediting Systems and Software Engineering &

Slides:



Advertisements
Similar presentations
Course: e-Governance Project Lifecycle Day 1
Advertisements

Systems Development Environment
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
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 Process Decision Frameworks for DoD and e-Services Projects ASRR 2011 Supannika.
University of Southern California Center for Systems and Software Engineering A Look at Software Engineering Risks in a Team Project Course Sue Koolmanojwong.
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Thammanoon Kawinfruangfukul CSSE MS, ID:
© 2004 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Holistic View of the Enterprise Business Development Operations.
2003 Indigo Technology, Inc. All Rights Reserved Alliance Portfolio Computing Infrastructure Services Customer Relationship Management Engineering Services.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 8: Post-Project Analysis.
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 Issues and Recommendations Emanating from the Management Issues Group of.
University of Southern California Center for Systems and Software Engineering Integrating Systems and Software Engineering (IS&SE) with the Incremental.
University of Southern California Center for Systems and Software Engineering Next Generation Estimation Methods and Management Metrics: Working Group.
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.
Process Synchronization Workshop Summary Report Jo Ann Lane University of Southern California Center for Software Engineering.
© Copyright Richard W. Selby and Northrop Grumman Corporation. All rights reserved. 0 Systems of Systems Acquisition and Management Critical Success.
Valuing System Flexibility via Total Ownership Cost Analysis Barry Boehm, JoAnn Lane, USC Ray Madachy, NPS NDIA Systems Engineering Conference October.
System-of-Systems Cost Modeling: COSOSIMO July 2005 Workshop Results Jo Ann Lane University of Southern California Center for Software Engineering.
USC CSSE Top 10 Risk Items: People’s Choice Awards Barry Boehm, Jesal Bhuta USC Center for Systems & Software Engineering
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
University of Southern California Center for Software Engineering C S E USC Agile and Plan-Driven Methods Barry Boehm, USC USC-CSE Affiliates’ Workshop.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Systems Development Planning Lifecycle.
Applying MDA in the ATM: A practical approach Teodora Bozheva, Terry Bailey (ESI) Julia Reznik, Tom Ritter (Fraunhofer FOKUS)
Software Evolution Planning CIS 376 Bruce R. Maxim UM-Dearborn.
Chapter : Software Process
University of Southern California Center for Systems and Software Engineering Enablers and Inhibitors for Expediting Systems and Software Development Sue.
CPTE 209 Software Engineering Summary and Review.
Software Project Management
Chapter 2 The process Process, Methods, and Tools
Chapter 2 The Process.
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.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
University of Southern California Center for Systems and Software Engineering Technical Debt CS 577 Software Engineering Barry Boehm Supannika Koolmanojwong.
University of Southern California Center for Systems and Software Engineering Rapid Fielding Projects in CSCI 577 Supannika Koolmanojwong Barry Boehm CS.
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
Software Processes n What is a process?  Sequence of steps required to develop or maintain software n Characteristics  prescribes major activities 
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
University of Southern California Center for Systems and Software Engineering Top Enablers and Inhibitors of Affordable Systems Supannika Koolmanojwong,
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Software Engineering - I
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)
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Developed by Reneta Barneva, SUNY Fredonia The Process.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Requirements Validation
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
University of Southern California Center for Systems and Software Engineering Technical Debt CS 577 Software Engineering Supannika Koolmanojwong.
Illuminating Britelite’s Internal Services for Success Strategy for Process Improvement.
University of Southern California Center for Systems and Software Engineering Aug. 26, 2010 © USC-CSE Page 1 A Winsor Brown CS 577a Lecture Fall.
March 2004 At A Glance The AutoFDS provides a web- based interface to acquire, generate, and distribute products, using the GMSEC Reference Architecture.
April 15, 2013 Atul Kwatra Principal Engineer Intel Corporation Hardware/Software Co-design using SystemC/TLM – Challenges & Opportunities ISCUG ’13.
CLE Introduction to Agile Software Acquisition
Software Configuration Management
CS 577b Software Engineering II -- Introduction
Single Point of Entry (SPOE)
CS 577b: Software Engineering II
Comparison between each special case
Enterprise Architecture at Penn State
Center for Software and Systems Engineering,
Systems Engineering Technical Debt Workshop Outbrief
Presentation transcript:

University of Southern California Center for Systems and Software Engineering Enablers and Inhibitors for Expediting Systems and Software Engineering & Estimating Agile Project Schedule Acceleration Sue Koolmanojwong and Dan Ingold COCOMO Forum October 17, 2012

University of Southern California Center for Systems and Software Engineering Workshop Participants Facilitators –Sue Koolmanojwong –Dan Ingold Participants –Bob Epps, Lockheed Martin –Diana Baklizky, TI Metricas –Quan Keenan, BAE Systems –Linda Esker, Fraunhofer –Tony Abolfotoah, Robbins Gioia –Kai Maetzel, IBM 2

University of Southern California Center for Systems and Software Engineering Summary Review the list of enablers and inhibitors Add, Refine the factors How each factor contribute to –Technical Debt –Flexibility 3

University of Southern California Center for Systems and Software Engineering Enablers - by ICSM life cycle phases Exploration & Valuation FoundationsDevelopment & Operations COTS Customer /tech requirements flexibility Small focused set of requirements Requirements Validation, clarification + Prioritization (Value- Based) Domain knowledge Rapid Prototyping Reusing assets, building blocks, frameworks Understanding of the existing system and interfaces Operational Analysis Building the common architecture/foundation Common standard, interface COTS Model-based engineering Reusing assets Automated testing to discover architectural problems Incremental Delivery & feedback Incremental test and feedback Mature configuration management Overnight build Target hardware lab / test like you fly & simulation 4 Text – New additions from the workshop

University of Southern California Center for Systems and Software Engineering Enablers - by ICSM life cycle phases All phases Optimize along the way Smell detection Agile/lean approach Best people / personnel capability Business process reengineering / process streamlining Colocation of hw & sw engineers Common standard and protocol Constituent Documentation Crowdsourcing Decision making authority Development process tailoring/adjustment Feasibility Evidence, Milestone review Flexible / tailorable rules Less context switching when doing multiple projects Mature configuration management Model-based engineering Outsourcing / surge support Risk Management Synchronization and Stabilization Team cohesion Tools and automation (Code generation) 5 Text – New additions from the workshop

University of Southern California Center for Systems and Software Engineering Inhibitors - by ICSM life cycle phases Exploration & Valuation FoundationsDevelopment & Operations Architecture constraint / heritage Backpropagation Bad documentation Bad RFP Contracting limitation Delayed authority to proceed/start with fixed milestone Embedded poor quality software fear to protest the contract award resulting in poor requirements -ilities standard Lack of Domain Experience Lack of understanding of the existing system and interfaces Outdated / stovepipe technology Overspecified requirements Poor / unknown heritage/pedigree Requirements Volatility System understanding Technical debt Technology Immaturity Technology Volatility Vague Requirements Design for reuse High number of external interfaces -ilities standard Interoperability / compatibility Lack of / incompatible standard & protocol Poor extendability Technology Immaturity Technology Volatility Functional dependency Inability and unavailability to test across systems Lack of development infrastructure Multiple operational sites with different configuration / platform / OS Functional dependency Unspecified / incompatible constraints of constituent systems 6 Text – New additions from the workshop

University of Southern California Center for Systems and Software Engineering Enablers - by ICSM life cycle phases All phases Classification / sensitivity Conflicting Stakeholders contracting limitation delayed authority to proceed/start with fixed milestone Developers / subcontractors not co-located Embedded poor quality software fear to protest the contract award resulting in poor requirements forced to use unfamiliar process infeasible schedule/staffing profile Lack of communication between teams Lack of constituent expert Lack of decision making at lower levels Lack of decision making authority Lack of program empowerment large number of subcontractors / stakeholders Personnel Turnover Process immaturity Rules and Regulations Sequential Development Under average people / Personnel Capability Unprecedentedness Infrastructure Debt 7 Text – New additions from the workshop

University of Southern California Center for Systems and Software Engineering Relationship between factors to Technical Debt & Flexibility Identify whether each factor hurts or helps the technical debt & flexibility –Challenges Definition of technical debt is mature yet Situation dependent 8