Reducing Technical Debt in Software Architecture

•

4 likes•338 views

"Having legacy software is often a sign of success" (Sam Newman) - The success of many companies is based on domain knowledge hidden in legacy systems. But was is a legacy system and how does it relate to technical debt? In this talk, we explore a possible way to approach legacy systems and technical debt. As an example, we look at the transformation of a platform where changes were expensive into a system designed for evolving with the business strategy.

Reducing Technical Debt
in Software Architecture
Florian Stefan ● @f_s_t_e_f_a_n

Reducing Technical Debt
in Software Architecture

Reducing Technical Debt
in Software Architecture
Platform Business Model

Linear Business Model
Reducing Technical Debt
in Software Architecture

Screaming Architecture
“Just as the plans for a house or a library scream
about the use cases of those buildings, so should the
architecture of a software application scream about
the use cases of the application.”
(Robert C. Martin)
Reducing Technical Debt
in Software Architecture

Legacy Software
“Having legacy software is often a sign of success.
Your business was successful to last long enough
for your software to become legacy.”
(Sam Newman)
Reducing Technical Debt
in Software Architecture

C
ase
Stud
y
Reducing Technical Debt
in Software Architecture

Reducing Technical Debt
in Software Architecture
Legacy
“Systems & Functions with a design
contrary to architectural principles.”

Reducing Technical Debt
in Software Architecture
Technical Debt
“Legacy Systems & Functions that
could threaten our business success.”

(Dr. Carola Lilienthal)
Reducing Technical Debt
in Software Architecture

Reducing Technical Debt
in Software Architecture
Rigidity Fragility Repetition Complexity

Communicator
Leader
Developer
Systems Focused
Entrepreneur
Strategic
Technologist
(Patrick Kua)
Reducing Technical Debt
in Software Architecture

Strategy Principles Practices
Reducing Technical Debt
in Software Architecture

Architectural
Principles
Technical Debt
Report
Clearance
Commitment
Balanced
Scorecard
Clearance
Sponsoring
Reducing Technical Debt
in Software Architecture

changes for
different reasons
Reducing Technical Debt
in Software Architecture

Principles PracticesStrategy
Organize around Business Capabilities
“Develop a ubiquitous language inside bounded
contexts - the maximal extent of a concept so
that the concept remains consistent.”

Principles PracticesStrategy
Event
Storming
Domain
Storytelling
Organizational
Structure
Customer
Touchpoints

Principles PracticesStrategy
Shared
Kernel
Customer/
Supplier
Published
Language
Anticorruption
Layer
Conformist

changes for
different reasons
changes at
different rates
Reducing Technical Debt
in Software Architecture

Principles PracticesStrategy
DRY Principle
“Every piece of knowledge must have
a single, unambiguous, authoritative
representation within a system.”
(Andy Hunt, Dave Thomas)

Silver Bullets
“A good developer is like a werewolf:
afraid of silver bullets.”
(Jochen Mader)
Reducing Technical Debt
in Software Architecture

Thank you!
Reducing Technical Debt
in Software Architecture

AEC Logic is an engineering software company with over 25 years of experience in civil engineering. Their vision is to become a leader in construction automation through innovation. Their mission is to develop innovative software products to automate infrastructure project planning and execution. They have expertise in cost estimation, planning, CAD tools, and custom software design for architecture, engineering and construction. Their current software products include cost estimation, bidding, buildings, terrain, slope and culverts tools.

Computing Without Computers - Oct08

Ian Page

Mandelstam David

Carl Ford

Open source software has benefits but poses challenges for compliance testing required by standards. Sangoma addresses this by using a mixed open source/proprietary approach where the proprietary components handle certified functionality while open source handles other aspects like interfaces. This allows leveraging open source while ensuring components needing certification can be tested and validated as required.

Organizing Design-Driven Development Using Rational Requirements Composer

Kurt Solarte

This document provides an overview of using Rational Requirements Composer to organize design-driven development. It discusses the importance of requirements and outlines how Rational Requirements Composer can be configured to store requirements, wireframes, cities, categories, and data sources for a project. Real-world examples are shown of how wireframes, requirements, and unique data can be represented in Rational Requirements Composer to facilitate traceability between different project elements.

Basics of se

Revi Shahini

The document provides an overview of software engineering fundamentals including definitions of software and software engineering, a discussion of the software engineering process and how it differs from programming, and a brief history of the evolution of software engineering from the 1950s to the present day focusing on approaches like abstract data types, object-oriented programming, and component-based design.

Embracing Failure - AzureDay Rome

Alberto Acerbis

Software engineering

Fahe Em

The document describes a course on software engineering that covers basic design principles and techniques like structured programming, object-oriented programming, and data structures. It aims to give students an understanding of how to produce well-structured, maintainable code. Examples will be shown in MATLAB and C/C++. Key concepts covered include abstraction, modularity, procedural and object-oriented programming, functions, classes, and arrays.

Introduction to Software Reverse Engineering

Teodoro Cipresso

près de 60% de leur temps à essayer de comprendre comment fonctionnent les applications sur lesquelles ils travaillent ? CAST Imaging est un logiciel de Software Intelligence qui produit automatiquement la documentation/base de connaissances techniques de n’importe quelle application. Celle-ci prend la forme de blueprints interactifs – dont les données sont stockées dans Neo4j – qui cartographient en détail tous les éléments d’une application et toutes leurs dépendances. Peu importe qu’ils soient en train de développer, maintenir, moderniser ou simplement monter en compétence, les utilisateurs de CAST Imaging trouvent en quelques minutes les réponses aux questions qu’ils se posent sur le fonctionnement de l’application, sans passer des heures à fouiller dans le code !

01 the big_idea

Majong DevJfu

The document discusses some of the origins and challenges of software engineering. It describes Brooks' classification of software difficulties as either accidental, which have solutions that can be discovered, or essential, which can only have partial solutions or none at all. Examples of essential difficulties include complexity, conformity to changing requirements, and the intangible nature of software. The document advocates that software architecture is key to addressing these difficulties and outlines some similarities and limitations between software and building architecture.

EuroPython 2019: Modern Continuous Delivery for Python Developers

Peter Bittner

Deployment automation, cloud platforms, containerization, short iterations to develop and release software—we’ve progressed a lot. And finally it’s official: Kubernetes and OpenShift are the established platforms to help us do scaling and zero downtime deployments with just a few hundred lines of YAML. It’s a great time. Can we finally put all our eggs into one basket? Identify the cloud platform that fits our needs, and jump on it? That could well backfire: Vendor lock-in is the new waterfall, it slows you down. In future you’ll want to jump over to the next better platform, in a matter of minutes. Not months. This talk is about The Art of Writing deployment pipelines that will survive Kubernetes, OpenShift and the like. It’s for Python developers and Kubernetes enthusiasts of all levels – no domain specific knowledge required, all you need to understand will be explained. You’ll learn how to separate application-specific and deployment-specific configuration details, to maximize your freedom and avoid vendor lock-in. Come see a demo of a Django project setup that covers everything from local development to automatic scaling, flexible enough to be deployed on any of your favorite container platforms. Take home a working, future-proof setup for your Python applications. See the original presentation at https://slides.com/bittner/modern-continuous-delivery/

Angel_Blancheth_Resume

Angel Blancheth

Why Enterprises Should Invest Money in EA Transformation Frameworks

Nathaniel Palmer

1. Enterprises should invest in business architecture transformation to address long-standing problems in IT like high costs, low business agility, and difficulties changing legacy systems. 2. These problems stem from the way IT has developed over 20+ years with an application-centric and point-to-point integration approach, leading to complex and rigid architectures. 3. Computer science offers a solution in Enterprise Service Orchestration Architecture (ESOA) which addresses these problems by standardizing integration through an enterprise service bus and implementing business processes as executable flows.

Why Enterprises Should Invest Money in EA Transformation Frameworks

Nathaniel Palmer

Enterprise architecture transformation is essential for businesses to reduce costs and increase agility. The current state of most enterprise IT architectures, with hundreds of isolated applications integrated through APIs, leads to high costs, low business agility, and difficulties changing or exiting legacy systems. Computer science provides the solution of enterprise service-oriented architecture (ESOA) which standardizes integration and allows reusable components. The ESOA Framework (ESOAFTM) is a reference architecture that guides enterprises along a gradual transition from their current application-centric "Legacy Enterprise" state to the desired fully ESOA-based "Elegant Enterprise" state. This transformation is expected to reduce total cost of ownership by 30% within a year.

Cs 1023 lec 1 big idea (week 1)

stanbridge

This document provides an introduction to software architecture. It discusses how software engineers have long employed architectures without realizing it and how architecture addresses issues identified by researchers. It differentiates between accidental difficulties that have been solved through advances like programming languages and essential difficulties like complexity, conformity, changeability and intangibility that cannot be fully solved. It uses an analogy to building architecture to illustrate key parallels and roles. Examples of the World Wide Web and Unix architectures are provided to demonstrate architecture in action.

Cs 1023 lec 1 big idea (week 1)

stanbridge

This document introduces the concept of software architecture and discusses its origins and importance. It describes some of the unique difficulties of software engineering, including complexity, conformity, changeability, and intangibility. It argues that software architecture can help address these difficulties by providing intellectual control, conceptual integrity, and a basis for knowledge reuse. The document uses examples like the World Wide Web and product line architectures to illustrate how architectural design influences software properties and facilitates reuse.

Software Development Life Cycle

Dr. Ranjan Kumar Mishra

The document discusses software engineering and the software development life cycle (SDLC). It defines key terms like system software, application software, and network-based software. It describes the characteristics of well-engineered software and lists the typical phases in the SDLC: analysis, design, coding, testing, implementation, maintenance, and re-engineering. The advantages of following the SDLC are also highlighted.

1. ch 1-introduction

Delowar hossain

This document provides an overview of software and software engineering. It defines software, discusses the characteristics of software, and describes different types of software applications. It then defines software engineering as the application of a systematic approach to the development and maintenance of software. Some key aspects of software engineering discussed include software quality, stakeholders, layered technology, software processes, umbrella activities, and principles of practice. Common myths in software development are also addressed.

New Software Design Proposal PowerPoint Presentation Slides

SlideTeam

Slowing down to Speed up: Agile & Technical Debt - SGPRG 2015

Taghi Paksima

1. Introduction

Ashis Kumar Chanda

The document discusses the goals and challenges of software engineering. It notes that the goals of producing software that is correct, with minimal effort and cost, and in the least time are difficult to fully achieve. Large software involves many people and millions of dollars over many years. Real-life examples like Eclipse have over 1.35 million lines of code and cost over $54 million to develop. The document outlines why software engineering is important to avoid costly failures and ensure efficient development. It also discusses myths and the need for different approaches like formal processes for large software.

Service oriented cloud computing

Mandar Pathrikar

This document discusses service oriented cloud computing. It defines cloud computing as dynamically scalable shared resources accessed over a network that users only pay for what they use. The architecture of cloud computing involves communication between clouds. An example is given of an industrial cloud containing a software control system, database storage, application server, and computer network that allows clients to access the site from anywhere in the world. Requirements for implementing a service oriented cloud computing application are provided.

"Why Micro Services adoption is crucial for SaaS companies?"

Vignesh Manivannan

SaaS companies are now looking for ways to leverage the DevOps/Cloud to optimize the development and release of new features with minimal overhead for collaboration among multiple (sometimes distributed) teams. It’s also important to note that operational complexity is directly proportional to the size of the SaaS application. Therefore, it becomes critical for SaaS companies to switch to Micro Services model to streamline their development/operations and be future ready. Key takeaways: • Challenges in monolithic architecture • Key factors driving Micro Services adoption • SOA vs. Micro Services • Benefits of Micro Services • Templatized way of creating Micro Services using Techcello

Connecting Apps, Devices and Services

Damir Dobric

Cast cloud april_2019

SPIN Chennai

The document discusses legacy monolithic applications and the challenges of migrating them to the cloud. It notes that 80% of actively used code is in COBOL and that enterprise applications are large, complex, and long-lived. Many organizations expect cloud migrations to take over a year to complete. The document recommends analyzing the application portfolio and individual applications using CAST software to understand architecture and define a migration roadmap. CAST software can reverse engineer applications, provide insights into architecture and data flow, and identify remediation opportunities to enable the transformation journey.

Importance of Software architecture

Steve Essich

Introduction to Chaos Engineering

Raymond Adrian (Rad) Butalid

Prompt Engineering in Software Development.ppt

WeblineIndia

Artificial Intelligence for XMLDevelopment

Octavian Nadolu

In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject. We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup. Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved. The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring. The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise. By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.

20240607 QFM018 Elixir Reading List May 2024

Matthew Sinclair

Similar to Reducing Technical Debt in Software Architecture

CAST Imaging: Map & Master Your Software

Neo4j

01 the big_idea

Majong DevJfu

EuroPython 2019: Modern Continuous Delivery for Python Developers

Peter Bittner

Angel_Blancheth_Resume

Angel Blancheth

Why Enterprises Should Invest Money in EA Transformation Frameworks

Nathaniel Palmer

Why Enterprises Should Invest Money in EA Transformation Frameworks

Nathaniel Palmer

Cs 1023 lec 1 big idea (week 1)

stanbridge

Cs 1023 lec 1 big idea (week 1)

stanbridge

Software Development Life Cycle

Dr. Ranjan Kumar Mishra

1. ch 1-introduction

Delowar hossain

New Software Design Proposal PowerPoint Presentation Slides

SlideTeam

Slowing down to Speed up: Agile & Technical Debt - SGPRG 2015

Taghi Paksima

1. Introduction

Ashis Kumar Chanda

Service oriented cloud computing

Mandar Pathrikar

"Why Micro Services adoption is crucial for SaaS companies?"

Vignesh Manivannan

Connecting Apps, Devices and Services

Damir Dobric

Cast cloud april_2019

SPIN Chennai

Importance of Software architecture

Steve Essich

Introduction to Chaos Engineering

Raymond Adrian (Rad) Butalid

Prompt Engineering in Software Development.ppt

WeblineIndia

Similar to Reducing Technical Debt in Software Architecture (20)

CAST Imaging: Map & Master Your Software

01 the big_idea

EuroPython 2019: Modern Continuous Delivery for Python Developers

Angel_Blancheth_Resume

Why Enterprises Should Invest Money in EA Transformation Frameworks

Cs 1023 lec 1 big idea (week 1)

Software Development Life Cycle

1. ch 1-introduction

New Software Design Proposal PowerPoint Presentation Slides

Slowing down to Speed up: Agile & Technical Debt - SGPRG 2015

1. Introduction

Service oriented cloud computing

"Why Micro Services adoption is crucial for SaaS companies?"

Connecting Apps, Devices and Services

Cast cloud april_2019

Importance of Software architecture

Introduction to Chaos Engineering

Prompt Engineering in Software Development.ppt

Recently uploaded

Artificial Intelligence for XMLDevelopment

Octavian Nadolu

20240607 QFM018 Elixir Reading List May 2024

Matthew Sinclair

Infrastructure Challenges in Scaling RAG with Custom AI models

Zilliz

Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.

Generating privacy-protected synthetic data using Secludy and Milvus

Zilliz

During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.

Programming Foundation Models with DSPy - Meetup Slides

Zilliz

TrustArc Webinar - 2024 Global Privacy Survey

TrustArc

How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024? In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores. See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe. This webinar will review: - The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey - The top challenges for privacy leaders, practitioners, and organizations in 2024 - Key themes to consider in developing and maintaining your privacy program

June Patch Tuesday

Ivanti

Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.

UI5 Controls simplified - UI5con2024 presentation

Wouter Lemaire

Climate Impact of Software Testing at Nordic Testing Days

Kari Kakkonen

My slides at Nordic Testing Days 6.6.2024 Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.

OpenID AuthZEN Interop Read Out - Authorization

David Brossard

Essentials of Automations: The Art of Triggers and Actions in FME

Safe Software

In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation. We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios. Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!

20240605 QFM017 Machine Intelligence Reading List May 2024

Matthew Sinclair

Full-RAG: A modern architecture for hyper-personalization

Zilliz

Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.

みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...

名前です男

Fueling AI with Great Data with Airbyte Webinar

Zilliz

“I’m still / I’m still / Chaining from the Block”

Claudio Di Ciccio

How to Get CNIC Information System with Paksim Ga.pptx

danishmna97

Your One-Stop Shop for Python Success: Top 10 US Python Development Providers

akankshawande

AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdf

Techgropse Pvt.Ltd.

In this blog post, we'll delve into the intersection of AI and app development in Saudi Arabia, focusing on the food delivery sector. We'll explore how AI is revolutionizing the way Saudi consumers order food, how restaurants manage their operations, and how delivery partners navigate the bustling streets of cities like Riyadh, Jeddah, and Dammam. Through real-world case studies, we'll showcase how leading Saudi food delivery apps are leveraging AI to redefine convenience, personalization, and efficiency.

GenAI Pilot Implementation in the organizations

kumardaparthi1024

Recently uploaded (20)

Artificial Intelligence for XMLDevelopment

20240607 QFM018 Elixir Reading List May 2024

Infrastructure Challenges in Scaling RAG with Custom AI models

Generating privacy-protected synthetic data using Secludy and Milvus

Programming Foundation Models with DSPy - Meetup Slides

TrustArc Webinar - 2024 Global Privacy Survey

June Patch Tuesday

UI5 Controls simplified - UI5con2024 presentation

Climate Impact of Software Testing at Nordic Testing Days

OpenID AuthZEN Interop Read Out - Authorization

Essentials of Automations: The Art of Triggers and Actions in FME

20240605 QFM017 Machine Intelligence Reading List May 2024

Full-RAG: A modern architecture for hyper-personalization

Fueling AI with Great Data with Airbyte Webinar

“I’m still / I’m still / Chaining from the Block”

How to Get CNIC Information System with Paksim Ga.pptx

Your One-Stop Shop for Python Success: Top 10 US Python Development Providers

AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdf

GenAI Pilot Implementation in the organizations

Reducing Technical Debt in Software Architecture

1. Reducing Technical Debt in Software Architecture Florian Stefan ● @f_s_t_e_f_a_n

2. Reducing Technical Debt in Software Architecture

3. Reducing Technical Debt in Software Architecture Platform Business Model

4. Reducing Technical Debt in Software Architecture

5. Linear Business Model Reducing Technical Debt in Software Architecture

6. Screaming Architecture “Just as the plans for a house or a library scream about the use cases of those buildings, so should the architecture of a software application scream about the use cases of the application.” (Robert C. Martin) Reducing Technical Debt in Software Architecture

7. Reducing Technical Debt in Software Architecture

8. Legacy Software “Having legacy software is often a sign of success. Your business was successful to last long enough for your software to become legacy.” (Sam Newman) Reducing Technical Debt in Software Architecture

9. C ase Stud y Reducing Technical Debt in Software Architecture

10. C a se Stu d y Reducing Technical Debt in Software Architecture

11. C a se Stu d y Reducing Technical Debt in Software Architecture

12. C a se Stu d y Reducing Technical Debt in Software Architecture

13. C ase Stud y Reducing Technical Debt in Software Architecture

14. C a se Stu d y Reducing Technical Debt in Software Architecture

15. C a se Stu d y Reducing Technical Debt in Software Architecture

16. Reducing Technical Debt in Software Architecture

17. Reducing Technical Debt in Software Architecture Legacy “Systems & Functions with a design contrary to architectural principles.”

18. Reducing Technical Debt in Software Architecture Technical Debt “Legacy Systems & Functions that could threaten our business success.”

19. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

20. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

21. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

22. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

23. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

24. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

25. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

26. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

27. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

28. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

29. (Dr. Carola Lilienthal) Reducing Technical Debt in Software Architecture

30. C a se Stu d y Reducing Technical Debt in Software Architecture

31. C a se Stu d y Reducing Technical Debt in Software Architecture

32. C a se Stu d y Reducing Technical Debt in Software Architecture

33. C a se Stu d y Reducing Technical Debt in Software Architecture

34. C a se Stu d y Reducing Technical Debt in Software Architecture

35. C a se Stu d y Reducing Technical Debt in Software Architecture

36. C a se Stu d y Reducing Technical Debt in Software Architecture

37. C a se Stu d y Reducing Technical Debt in Software Architecture

38. C a se Stu d y Reducing Technical Debt in Software Architecture

39. C a se Stu d y Reducing Technical Debt in Software Architecture

40. C a se Stu d y Reducing Technical Debt in Software Architecture

41. C a se Stu d y Reducing Technical Debt in Software Architecture

42. Reducing Technical Debt in Software Architecture Rigidity Fragility Repetition Complexity

43. Reducing Technical Debt in Software Architecture Rigidity Fragility Repetition Complexity

44. Reducing Technical Debt in Software Architecture Rigidity Fragility Repetition Complexity

45. Reducing Technical Debt in Software Architecture Rigidity Fragility Repetition Complexity

46. Reducing Technical Debt in Software Architecture Rigidity Fragility Repetition Complexity

47. Reducing Technical Debt in Software Architecture Rigidity Fragility Repetition Complexity

48. Reducing Technical Debt in Software Architecture

49. Communicator Leader Developer Systems Focused Entrepreneur Strategic Technologist (Patrick Kua) Reducing Technical Debt in Software Architecture

50. Strategy Principles Practices Reducing Technical Debt in Software Architecture

51. Reducing Technical Debt in Software Architecture

52. Architectural Principles Technical Debt Report Clearance Commitment Balanced Scorecard Clearance Sponsoring Reducing Technical Debt in Software Architecture

53. Reducing Technical Debt in Software Architecture

54. Reducing Technical Debt in Software Architecture

55. Reducing Technical Debt in Software Architecture

56. changes for different reasons Reducing Technical Debt in Software Architecture

57. changes for different reasons Reducing Technical Debt in Software Architecture

58. changes for different reasons Reducing Technical Debt in Software Architecture

59. changes for different reasons Reducing Technical Debt in Software Architecture

60. changes for different reasons Reducing Technical Debt in Software Architecture

61. changes for different reasons Reducing Technical Debt in Software Architecture

62. Principles PracticesStrategy Organize around Business Capabilities “Develop a ubiquitous language inside bounded contexts - the maximal extent of a concept so that the concept remains consistent.”

63. Principles PracticesStrategy Event Storming Domain Storytelling Organizational Structure Customer Touchpoints

64. Principles PracticesStrategy Event Storming Domain Storytelling Organizational Structure Customer Touchpoints

65. Principles PracticesStrategy Event Storming Domain Storytelling Organizational Structure Customer Touchpoints

66. Principles PracticesStrategy Event Storming Domain Storytelling Organizational Structure Customer Touchpoints

67. Principles PracticesStrategy Event Storming Domain Storytelling Organizational Structure Customer Touchpoints

68. Reducing Technical Debt in Software Architecture

69. Reducing Technical Debt in Software Architecture

70. Reducing Technical Debt in Software Architecture

71. Reducing Technical Debt in Software Architecture

72. Reducing Technical Debt in Software Architecture

73. Principles PracticesStrategy Shared Kernel Customer/ Supplier Published Language Anticorruption Layer Conformist

74. Principles PracticesStrategy Shared Kernel Customer/ Supplier Published Language Anticorruption Layer Conformist

75. Principles PracticesStrategy Shared Kernel Customer/ Supplier Published Language Anticorruption Layer Conformist

76. Principles PracticesStrategy Shared Kernel Customer/ Supplier Published Language Anticorruption Layer Conformist

77. Principles PracticesStrategy Shared Kernel Customer/ Supplier Published Language Anticorruption Layer Conformist

78. Principles PracticesStrategy Shared Kernel Customer/ Supplier Published Language Anticorruption Layer Conformist

79. Reducing Technical Debt in Software Architecture

80. Reducing Technical Debt in Software Architecture

81. Reducing Technical Debt in Software Architecture

82. Reducing Technical Debt in Software Architecture

83. Reducing Technical Debt in Software Architecture

84. Reducing Technical Debt in Software Architecture

85. changes for different reasons Reducing Technical Debt in Software Architecture

86. changes for different reasons Reducing Technical Debt in Software Architecture

87. changes for different reasons Reducing Technical Debt in Software Architecture

88. changes for different reasons Reducing Technical Debt in Software Architecture

89. changes for different reasons Reducing Technical Debt in Software Architecture

90. changes for different reasons Reducing Technical Debt in Software Architecture

91. changes for different reasons changes at different rates Reducing Technical Debt in Software Architecture

92. Principles PracticesStrategy DRY Principle “Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.” (Andy Hunt, Dave Thomas)

93. Reducing Technical Debt in Software Architecture

94. Reducing Technical Debt in Software Architecture

95. Reducing Technical Debt in Software Architecture

96. Reducing Technical Debt in Software Architecture

97. Reducing Technical Debt in Software Architecture

98. Reducing Technical Debt in Software Architecture

99. Reducing Technical Debt in Software Architecture

100. Reducing Technical Debt in Software Architecture

101. changes for different reasons changes at different rates Reducing Technical Debt in Software Architecture

102. changes for different reasons changes at different rates Reducing Technical Debt in Software Architecture

103. changes for different reasons changes at different rates Reducing Technical Debt in Software Architecture

104. changes for different reasons changes at different rates Reducing Technical Debt in Software Architecture

105. changes for different reasons changes at different rates Reducing Technical Debt in Software Architecture

106. changes for different reasons changes at different rates Reducing Technical Debt in Software Architecture

107. changes for different reasons changes at different rates Reducing Technical Debt in Software Architecture

108. changes for different reasons changes at different rates Reducing Technical Debt in Software Architecture

109. changes for different reasons changes at different rates Reducing Technical Debt in Software Architecture

110. Reducing Technical Debt in Software Architecture

111. Silver Bullets “A good developer is like a werewolf: afraid of silver bullets.” (Jochen Mader) Reducing Technical Debt in Software Architecture

112. Thank you! Reducing Technical Debt in Software Architecture

Reducing Technical Debt in Software Architecture

Recommended

Recommended

More Related Content

Similar to Reducing Technical Debt in Software Architecture

Similar to Reducing Technical Debt in Software Architecture (20)

Recently uploaded

Recently uploaded (20)

Reducing Technical Debt in Software Architecture