Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
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
Technical Program Manager's Handbook

You're reading from   Technical Program Manager's Handbook Empowering managers to efficiently manage technical projects and build a successful career path

Arrow left icon
Product type Paperback
Published in Dec 2022
Publisher Packt
ISBN-13 9781804613559
Length 214 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Joshua Alan Teter Joshua Alan Teter
Author Profile Icon Joshua Alan Teter
Joshua Alan Teter
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Part 1: What is a Technical Program Manager?
2. Chapter 1: Fundamentals of a Technical Program Manager FREE CHAPTER 3. Chapter 2: Pillars of a Technical Program Manager 4. Part 2: Fundamentals of Program Management
5. Chapter 3: Introduction to Program Management 6. Chapter 4: Driving Toward Clarity 7. Chapter 5: Plan Management 8. Chapter 6: Risk Management 9. Chapter 7: Stakeholder Management 10. Chapter 8: Managing a Program 11. Chapter 9: Career Paths 12. Part 3: Technical Toolset
13. Chapter 10: The Technical Toolset 14. Chapter 11: Code Development Expectations 15. Chapter 12: System Design and Architecture Landscape 16. Chapter 13: Enhancing Management Using Your Technical Toolset 17. Index 18. Other Books You May Enjoy

Examining an architecture landscape

To get a good understanding of what an architecture landscape is, we’ll compare a system design with an architecture landscape. We’ll follow this up with a look into the implementation of the Mercury messaging application on a corporate network.

There is more in common between a system design and an architectural landscape than not. The design patterns between the two are the same and are often referred to as architectural patterns. They also both describe the relationship between components of an ecosystem that share some relationship either in the data they process and handle or the function that they collectively perform.

Where they can differ is the scope and depth of the design. A system design is limited in scope, as it often covers a single feature or limited data flow between highly related systems. The design may dive into API definitions, as well as illustrate the data model and how it flows through the system.

...
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 €18.99/month. Cancel anytime