Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Software Architecture for Busy Developers

You're reading from   Software Architecture for Busy Developers Talk and act like a software architect in one weekend

Arrow left icon
Product type Paperback
Published in Oct 2021
Publisher Packt
ISBN-13 9781801071598
Length 174 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Stéphane Eyskens Stéphane Eyskens
Author Profile Icon Stéphane Eyskens
Stéphane Eyskens
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Section 1: Introduction
2. Chapter 1: Introducing Software Architecture FREE CHAPTER 3. Section 2: The Broader Architecture Landscape
4. Chapter 2: Exploring Architecture Frameworks and Methodologies 5. Chapter 3: Understanding ATAM and the Software Quality Attributes 6. Section 3: Software Design Patterns and Architecture Models
7. Chapter 4: Reviewing the Historical Architecture Styles 8. Chapter 5: Design Patterns and Clean Architecture 9. Section 4: Impact of the Cloud on Software Architecture Practices
10. Chapter 6: Impact of the Cloud on the Software Architecture Practice 11. Section 5: Architectural Trends and Summary
12. Chapter 7: Trendy Architectures and Global Summary 13. Other Books You May Enjoy

Summary

After reading this chapter, you should have grasped the essentials of ATAM and its main purpose: discovering sensitivity points, trade-off points, risks, and impactful quality attributes to help you make informed decisions. I strongly encourage you to have a pragmatic (not dogmatic) approach to ATAM because not every asset requires the same level of attention. However, in mission-critical projects, ATAM proves to be efficient and can be credited with raising the right questions at the right time. Flaws resulting from incorrect architectural decisions are very hard to fix and adjust at a later stage. Note that I refer to flaws, not to maturity levels. You can work in an incremental way but you should make sure not to end up with true design flaws in your architecture. ATAM should safeguard you against such adverse situations. In our next chapter, we will review the different architectural styles, from decades ago up to today.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image