Managing Architecture Debt in Software Systems

architecture debt l.w
1 / 5
Embed
Share

Explore the concept of architecture debt and its impact on software systems, focusing on the challenges of handling changes, detecting change, and addressing architectural antipatterns such as unstable interfaces and modularity violations.

  • Architecture Debt
  • Software Systems
  • Change Management
  • Architectural Antipatterns
  • Technology Refresh

Uploaded on | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. Architecture Debt SWEN-440 SOFTWARE SYSTEM REQUIREMENTS AND ARCHITECTURE

  2. Change Happens New Requirements: Updates to functionality Updates to quality attributes Technology Refreshes: Hardware Software Bugs Entropy No one is minding the architecture Decline into disorder

  3. Detecting Change

  4. Impact of Architecture Debt

  5. Hotspots / Architectural Antipatterns Unstable Interfaces An interface should be stable low rate of change, stability is a key attribute of interfaces Modularity Violation Unhealthy Inheritance Cyclic Dependency (Clique) Package Cycle Crossing

Related


More Related Content