Like all technical debt, enterprise technical debt consists of choices expedient in the short term, but often problematic over the long term. In enterprise technical debt, the impact reaches beyond the scope of a single system or project. Because ignoring enterprise technical debt can have significant consequences, software and systems architects should be alert for it, and they should not let it get overlooked or ignored when they come across it. Enterprise technical debt often results in multi-project or organization-wide risks that increase the organization’s cost, efficiency, or security risks. Remediation of enterprise technical debt requires intervention by governance structures whose scope is broader than that of individual teams or projects. In this podcast from the Carnegie Mellon University Software Engineering Institute (SEI), Stephany Bellomo, a principal engineer in the SEI’s Software Solutions Division, talks with principal researcher Suzanne Miller about identifying and remediating enterprise technical debt.
Moving Target Defense
Improving Cybersecurity Through Cyber Intelligence
A Requirement Specification Language for AADL
Becoming a CISO: Formal and Informal Requirements
Predicting Quality Assurance with Software Metrics and Security Methods
Network Flow and Beyond
A Community College Curriculum for Secure Software Development
Security and the Internet of Things
The SEI Fellow Series: Nancy Mead
An Open Source Tool for Fault Tree Analysis
Global Value Chain – An Expanded View of the ICT Supply Chain
Intelligence Preparation for Operational Resilience
Evolving Air Force Intelligence with Agile Techniques
Threat Modeling and the Internet of Things
Open Systems Architectures: When & Where to Be Closed
Effective Reduction of Avoidable Complexity in Embedded Systems
Toward Efficient and Effective Software Sustainment
Quality Attribute Refinement and Allocation
Is Java More Secure Than C?
Identifying the Architectural Roots of Vulnerabilities
Create your
podcast in
minutes
It is Free