You're reading from Enterprise Architecture with .NET Expert-backed advice for information system design, down to .NET and C# implementation

Product type Paperback

Published in May 2024

Publisher Packt

ISBN-13 9781835085660

Length 772 pages

Edition 1st Edition

Languages

Tools

.NET

Concepts

Application Development

Author (1):

Jean-Philippe Gouigoux

View More author details

Table of Contents (30) Chapters

Preface

1. Part 1: Business-Aligned Architecture and the Problems It Solves

2. Chapter 1: The Sad State of Information Systems FREE CHAPTER

3. Chapter 2: Applying Industrial Principles to Software

4. Chapter 3: Reaching Business Alignment

5. Chapter 4: Dealing with Time and Technical Debt

6. Chapter 5: A Utopic Perfect IT System

7. Part 2: Architecture Frameworks and Methods

8. Chapter 6: SOLID Principles, from Code to Systems

9. Chapter 7: C4 and Other Approaches

10. Chapter 8: Service Orientation and APIs

11. Chapter 9: Exploring Domain-Driven Design and Semantics

12. Chapter 10: Master Data Management

13. Chapter 11: Business Processes and Low Code

14. Chapter 12: Externalization of Business Rules

15. Chapter 13: Externalization of Authorization

16. Part 3: Building a Blueprint Application with .NET

17. Chapter 14: Decomposing the Functional Responsibilities

18. Chapter 15: Plugging Standard External Modules

19. Chapter 16: Creating a Write-Only Data Referential Service

20. Chapter 17: Adding Query to the Data Referential Service

21. Chapter 18: Deploying Data Referential Services

22. Chapter 19: Designing a Second Data Referential Service

23. Chapter 20: Creating a Graphical User Interface

24. Chapter 21: Extending the Interfaces

25. Chapter 22: Integrating Business Processes

26. Part 4: Validating the Architecture

27. Chapter 23: Applying Modifications to the System

28. Index

Why subscribe?

29. Other Books You May Enjoy

The concept of technical debt

Technical debt may be one of the most discussed concepts related to IT management in the past decade. As the quality of software is a fundamental goal of this book, it is something we have to clearly describe.

The general definition of technical debt

If you are reading this book, you are certainly interested in software quality and how to architect things correctly, so you most certainly have a good grasp of the concept of technical debt, or at least have been exposed to it. Nonetheless, I will give a quick definition of it so that you can try and formalize it.

What is technical debt?

Technical debt is the amount of accidental complexity you have allowed to enter your project, together with its increase in intrinsic complexity.

Let’s decompose this a little. When you develop a software project, it always aims at producing a function on a given business domain perimeter. There is an inner, definite, stable complexity that comes from...