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
Technical Program Manager's Handbook

You're reading from   Technical Program Manager's Handbook Unlock your TPM potential by leading technical projects successfully and elevating your career path

Arrow left icon
Product type Paperback
Published in Sep 2024
Publisher Packt
ISBN-13 9781836200475
Length 368 pages
Edition 2nd 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 (21) Chapters Close

Preface 1. Section 1: What Is a Technical Program Manager? FREE CHAPTER
2. Fundamentals of a Technical Program Manager 3. Pillars of a Technical Program Manager 4. Career Paths 5. Section 2: Fundamentals of Program Management
6. An Introduction to Program Management Using a Case Study 7. Driving Toward Clarity 8. Plan Management 9. Risk Management 10. Stakeholder Management 11. Managing a Program 12. Emotional Intelligence in Technical Program Management 13. Section 3: Technical Toolset
14. The Technical Toolset 15. Code Development Expectations 16. System Design and Architecture Landscape 17. Harnessing the Power of Artificial Intelligence in Technical Program Management 18. Enhancing Management Using Your Technical Toolset 19. Other Books You May Enjoy
20. Index

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 $19.99/month. Cancel anytime
Banner background image