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
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

Getting started with quality-attribute scenarios

Once you have identified a list of quality attributes applicable to your system, you are ready to define quality-attribute scenarios. The purpose of these scenarios is to connect the dots between the events, their outcome, and the expected answer from the architecture. ATAM describes the following three types of scenarios:

  • Use case
  • Growth
  • Exploratory scenarios

Most of the time, only use case scenarios are considered. They intend to describe possible use cases and the expected response from the architecture. Growth and exploratory scenarios aim to anticipate what could come next. The selection of the appropriate scenario should be done in agreement with the relevant stakeholders, including product owners and project managers. While ATAM provides tools such as utility trees to translate business goals into quality attributes, the reality shows that we often end up with an Excel sheet (or Word document) regrouping...

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