Fundamentals of Software Architecture, 2nd Edition

Chapter 3. Component-Based Thinking

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 8th chapter of the final book. Please note that the GitHub repo will be made active later on.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

In Chapter 2, we introduced the concept of a module as a collection of related code. In this chapter, we dive much deeper into this concept, focusing on the architectural aspect of modularity in terms of logical components–the building blocks of a system.

Identifying and managing logical components is a part of architectural thinking (see Chapter 1), so much so that we call this activity component-based thinking. Component-based thinking is seeing the structure of a system as a set of logical components, all interacting to perform certain business functions. It’s at this level (not the class level) that an architect “sees” the system.

In this chapter we define logical components within software architecture, how to identify them, and how to arrive at an appropriate level of granularity through analyzing what’s known as cohesion (we define what that means a little later on in this chapter). We also ...