مقاله انگلیسی رایگان در مورد مدیریت استراتژیک نقص فنی – IEEE 2017

The goal of the tutorial is to give the attendees a better appreciation of the rather fuzzy concept of Technical Debt, articulate the differences between technical debt at the code level, versus technical debt at the architectural or structural level, or at the process level. It will give attendees techniques and tools to reason about technical debt: identify it, and manage it, that is, decide when and why it is wise to ”repay” some of that technical debt. II. AUDIENCE & SCOPE This tutorial is primarily intended for: • Software project managers, • product managers, product owners • and software architects Level basic; no required prerequisites. This presentation is of value for both practitioners and for academics/researchers, but mostly targeted at practitioners. III. OUTLINE OF TUTORIAL This half day tutorial will have the following structure: 1. Introduction to Technical Debt (80 minutes) a. Game: hard choices b. Definitions of technical debt c. Examples of various types of debt 2. Practical measures (60 minutes) a. Examples, results of interviews from industry b. Tools and techniques c. Requirements for support (tool or otherwise), metrics and measures of success 3. Future Directions (30 minutes) a. Agile architecting and technical debt b. Vision for technical debt analysis framework c. Discussion on key problems and challenges faced by practicing software engineers who need to elicit, communicate, and manage technical debt at different facets of their projects.

IV. PRESENTER

Philippe Kruchten is professor of software engineering at the University of British Columbia in Vancouver, Canada, which he joined in 2004 after a 30+ year career in the software industry, developing systems in telecommunications, defense and aerospace. His main interests are in software architecture, software project management and software development processes. During his time with Rational Software (now IBM) he led the development of the RUP, which embeds an architecture-centric method. He is the co-founder and secretary of the IFIP WG2.10 on Software Architecture (1998), Chair of the ICSA steering committee, and co-founder and chair of Agile Vancouver (2004). He’s a senior member of IEEE CompSoc and of ACM.