Book Image

Software Architecture for Busy Developers

By : Stéphane Eyskens
Book Image

Software Architecture for Busy Developers

By: Stéphane Eyskens

Overview of this book

Are you a seasoned developer who likes to add value to a project beyond just writing code? Have you realized that good development practices are not enough to make a project successful, and you now want to embrace the bigger picture in the IT landscape? If so, you're ready to become a software architect; someone who can deal with any IT stakeholder as well as add value to the numerous dimensions of software development. The sheer volume of content on software architecture can be overwhelming, however. Software Architecture for Busy Developers is here to help. Written by Stéphane Eyskens, author of The Azure Cloud Native Mapbook, this book guides you through your software architecture journey in a pragmatic way using real-world scenarios. By drawing on over 20 years of consulting experience, Stéphane will help you understand the role of a software architect, without the fluff or unnecessarily complex theory. You'll begin by understanding what non-functional requirements mean and how they concretely impact target architecture. The book then covers different frameworks used across the entire enterprise landscape with the help of use cases and examples. Finally, you'll discover ways in which the cloud is becoming a game changer in the world of software architecture. By the end of this book, you'll have gained a holistic understanding of the architectural landscape, as well as more specific software architecture skills. You'll also be ready to pursue your software architecture journey on your own - and in just one weekend!
Table of Contents (14 chapters)
Section 1: Introduction
Section 2: The Broader Architecture Landscape
Section 3: Software Design Patterns and Architecture Models
Section 4: Impact of the Cloud on Software Architecture Practices
Section 5: Architectural Trends and Summary

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