PSM 1July/ August 2012 P RACTICAL S OFTWARE AND S YSTEMS M EASUREMENT What Does Technical Debt Mean at a System Level 2 August 2012 Bob Epps, Lockheed.

Slides:



Advertisements
Similar presentations
Systems Engineering Technical Debt Bob Epps USC-CSSE COCOMO II Workshop October 16, 2012.
Advertisements

Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.
E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER I NTRODUCTION TO Q UALITY A SSURANCE C OPYRIGHT © 2012 DSR C ORPORATION.
Design Concepts and Principles
Smart Grid - Cyber Security Small Rural Electric George Gamble Black & Veatch
1 Importance of CM/DM in the Current and Emerging DoD Product Support Environment Dr. Marilyn T. Gaska, Chief Engineer and Michael “Bo” Gourley Logistics.
PSM Whitepaper: Systems Engineering Technical Debt Bob Epps Lockheed Martin Corporation March 14, 2012.
W5HH Principle As applied to Software Projects
COSYSMO 2.0 Workshop Summary (held Monday, March 17 th 2008) USC CSSE Annual Research Review March 18, 2008 Jared Fortune.
IBM Business Consulting Services © Copyright IBM Corporation 2006 Unified Process March 27, 2006 Chris Armstrong.
Project Management Outline of Chapters 1-6. Chapter 1 – Project Management Concepts Definition of a project and its attributes Key constraints within.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Dr. L. K. Gaafar The American University in Cairo
University of Southern California Center for Software Engineering CSE USC 12/6/01©USC-CSE CeBASE: Opportunities to Collaborate Barry Boehm, USC-CSE Annual.
1 COSYSMO 3.0: Future Research Directions Jared Fortune University of Southern California 2009 COCOMO Forum Massachusetts Institute of Technology.
SE 555 Software Requirements & Specification Requirements Management.
Welcome and Overview: Annual Research Review 2006 Barry Boehm, USC-CSE March 15, 2006.
Launch Meeting 26 October 2005 Loughborough University.
Nov. 14, 2007 Systems Engineering ä System ä A set or arrangement of things so related as to form a unity or organic whole. ä A set of facts, principles,
SRDR Data Analysis Workshop Summary Brad Clark Ray Madachy Thomas Tan 25th International Forum on COCOMO and Systems/Software Cost Modeling November 5,
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Engineering Systems of.
Opportunities & Implications for Turkish Organisations & Projects
Proposed MITHI Concept Paper
Ipek Ozkaya, COCOMO Forum © 2012 Carnegie Mellon University Affordability and the Value of Architecting Ipek Ozkaya Research, Technology.
Work Breakdown Structure
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Change Management “Getting from where you are, to where you want to be”
Business Analysis and Essential Competencies
The Challenge of IT-Business Alignment
INTOSAI Public Debt Working Group Updating of the Strategic Plan Richard Domingue Office of the Auditor General of Canada June 14, 2010.
E MBEDDED S YSTEMS S OFTWARE T RAINING C ENTER S OFTWARE D ESIGN C OPYRIGHT © 2011 DSR C ORPORATION.
Esri UC2013. Technical Workshop. Technical Workshop 2013 Esri International User Conference July 8–12, 2013 | San Diego, California What you Need to Know.
Risk Management for Technology Projects Geography 463 : GIS Workshop May
Relationships July 9, Producers and Consumers SERI - Relationships Session 1.
National ITS Architecture Deployment Support and FHWA Resources.
Page 1 ISO/IEC JTC 1/SC 7/WG 7 N Summary of the Alignment of System and Software Life Cycle Process Standards The material in this briefing.
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
University of Southern California Center for Systems and Software Engineering COSATMO/COSYSMO Workshop Jim Alstad, USC-CSSE Gan Wang, BAE Systems Garry.
Overview of Pathways project, key concepts of UHC and translation into an Irish context Steve Thomas Principal Investigator Pathways Project Director,
Planning with Use Cases Extracts from the Lamri Use Case Survival Guide™ Mark Aked Managing Consultant For more information visit or .
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
FNR Foresight: Evaluating Phase 1 and Prospects for Phase 2 Dr. Michael Keenan PREST, University of Manchester, UK FNR Foresight Workshop Luxembourg, 16.
Dr. Young J. Kim.  INCOSE Definition ( ◦ “An interdisciplinary approach & means to enable the realization of successful systems. It focuses.
ISO/IEC JTC1/SC7 WG42 Upcoming NWIP for IS Architecture Evaluation Invitation to IEEE for Early Informal Comments at WICSA 2011 Workshop on Standards.
1 Identify Preferred Alternative and Finalize Plan Planning Steps 7 & 8.
A Strategic Plan for Pavement Engineering NCHRP 20-7(223) AASHTO Joint Technical Committee on Pavements Dan Dawood, P.E. Pennsylvania Department of Transportation.
I Induction E.S. Tunis and Associates Inc. Welcome to ESTA’s learning design workshop. The ideas developed in this workshop will set the foundation for.
1 Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
University of Southern California Center for Systems and Software Engineering Enablers and Inhibitors for Expediting Systems and Software Engineering &
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
Advanced Software Engineering Dr. Cheng
Stacy Kowalczyk WIC Technical Hour 3/30/2005
Software Risk Management
Continuous Delivery- Complete Guide
CS4311 Spring 2011 Process Improvement Dr
Identify the Risk of Not Doing BA
Risk Management for Technology Projects
CS 577b: Software Engineering II
MGT 498 Education for Service-- snaptutorial.com.
MGT 498 TUTORIAL Education for Service--mgt498tutorial.com.
MGT 498 Teaching Effectively-- snaptutorial.com
IT Governance Planning Overview
Project Management Process Groups
CAF Quarterly Meeting Measuring the Value of an EA Practice
Systems Engineering Technical Debt Workshop Outbrief
Presentation transcript:

PSM 1July/ August 2012 P RACTICAL S OFTWARE AND S YSTEMS M EASUREMENT What Does Technical Debt Mean at a System Level 2 August 2012 Bob Epps, Lockheed Martin Practical Software and Systems Measurement Objective Information for Decision Makers

PSM 2July/ August 2012 P RACTICAL S OFTWARE AND S YSTEMS M EASUREMENT Software Technical Debt has been an area of increasing focus and discussion, but we also believe it has application to Systems Engineering, as well. The intent of the workshop is to understand the scope of Technical Debt and what it means with respect to Systems Engineering. What Does Technical Debt Mean at a System Level

PSM 3July/ August 2012 P RACTICAL S OFTWARE AND S YSTEMS M EASUREMENT Objectives of the Workshop Identification and Management of Technical Debt in System Development and O&M phases of the Systems Lifecycle. Discuss how the Decisions made during the System life cycle influence the level of Technical Debt of in the System. Evaluation of Technical Debt’s impact to the Operation & Maintenance (O&M) phase. Discussion on the relationship of Systems Engineering Technical Debt to System Affordability.

PSM 4July/ August 2012 P RACTICAL S OFTWARE AND S YSTEMS M EASUREMENT Workshop Format Agenda -Management of Technical Debt- Steve McConnell -Technical Debt Observations- Jim Highsmith -Types of Debt- Chris Sterling -Workshop Exercise # 1-Identifying Technical Debt -Break -Management of Architectural Debt- Ipek Ozkapa -Workshop Exercise # 2- Architecture Technical Debt -Workshop Exercise # 3- System Design Technical Debt -Break -Operations & Maintenance(O&M) Technical Debt -Workshop Summary/Action Plan

PSM 5July/ August 2012 P RACTICAL S OFTWARE AND S YSTEMS M EASUREMENT Workshop Format Techniques that will be used -We would look at the terms and concepts from Software Technical Debt and then compare and contrast as needed to ensure consistency, yet adapt for the Systems Engineering considerations. In this way we will build from the existing knowledge rather than re-invent the wheel.

PSM 6July/ August 2012 P RACTICAL S OFTWARE AND S YSTEMS M EASUREMENT Technical Debt References Managing Technical Debt -Tom McConnell - The Financial Implications of Technical Debt -Jim Highsmith - technical-debt/ technical-debt/ Second International Workshop on Managing Technical Debt - Technical Debt or Strategic Opportunity - Enabling Agility by Strategically Managing Architectural Technical Debt -Ipek Ozkaya - managing-architectural-technical-debthttp://blog.sei.cmu.edu/post.cfm/enabling-agility-by-strategically- managing-architectural-technical-debt

PSM 7July/ August 2012 P RACTICAL S OFTWARE AND S YSTEMS M EASUREMENT Technical Debt Workshop Action Plan  White paper on Technical Debt applicability to Systems  Outline  Describe Technical Debt in Systems Engineering Vernacular  Identify sources and methods of measurement of Technical Debt within the Systems Engineering Life Cycle Systems Analysis Systems Architecture Systems Design Systems Build Systems Integration & Test System Operation & Maintenance  Identify of implication of System Level Technical Debt to Software and Hardware Elements

PSM 8July/ August 2012 P RACTICAL S OFTWARE AND S YSTEMS M EASUREMENT Read ahead material for the Systems Engineering Technical Debt Workshop Definitions of Technical Debt SE Leading Indicator Guide Architecture Technical Debt debthttp://blog.sei.cmu.edu/post.cfm/strategic-management-of-architectural-technical- debt Assessing and Avoiding Technical Debt, Dr. Barry Boehm, June th International Forum on Systems, Software and COCOMO COST Model, Nov Presentation entitled,” Measurement and Estimating Models for Software Maintenance Workshop” Addressing O&M impact related to Technical Debt sion5_ ppthttp://csse.usc.edu/csse/event/2011/COCOMO/presentations/COCOMO%20Forum_ver sion5_ ppt