Managing technical debt, which refers to the rework and degraded quality resulting from overly hasty delivery of software capabilities to users, is an increasingly critical aspect of producing cost-effective, timely, and high-quality software products. A delicate balance is needed between the desire to release new software capabilities rapidly to satisfy users and the desire to practice sound software engineering that reduces rework. This blog post at the SEI blog by Ipek Ozkaya discusses how an architecture-focused analysis approach helps manage technical debt by enabling software engineers to decide the best time to rearchitect—in other words, to pay down the technical debt.
Connect with SATURN
Join SATURN Network mailing List here:Get UpdatesFor Email Marketing you can trust.
Subscribe to our feed:
Topicsagile release planning architecture evaluation architecture review Architecture Tradeoff Analysis Method ATAM Carnegie Mellon cloud computing documentation enterprise architecture non-functional requirements SATURN 2010 SATURN 2011 SATURN 2012 SATURN 2013 SATURN 2014 SATURN 2015 SATURN Conference SEI SOA software architecture software architecture evaluation software architecture requirements software architecture review software design software development software engineering Software Engineering Institute system architecture systems architecture technical debt