Salary surveys worldwide regularly place software architect in the top 10 best jobs, yet no real guide exists to help developers become architects. Until now. This book provides the first comprehensive overview of software architecture's many aspects. Aspiring and existing architects alike will examine architectural characteristics, architectural patterns, component determination, diagramming and presenting architecture, evolutionary architecture, and many other topics.

Mark Richards and Neal Ford--hands-on practitioners who have taught software architecture classes professionally for years--focus on architecture principles that apply across all technology stacks. You'll explore software architecture in a modern light, taking into account all the innovations of the past decade.

This book examines:

• Architecture patterns: The technical basis for many architectural decisions
• Components: Identification, coupling, cohesion, partitioning, and granularity
• Soft skills: Effective team management, meetings, negotiation, presentations, and more
• Modernity: Engineering practices and operational approaches that have changed radically in the past few years
• Architecture as an engineering discipline: Repeatable results, metrics, and concrete valuations that add rigor to software architecture

What are the attitudes and actions that make great principals stand out? In this internationally renowned bestseller, Todd Whitaker reveals the 20 keys to effective school leadership.

This essential third edition features helpful new strategies for recruiting talent through better interview and reference questions, as well as tips for retaining talent. It also offers a new section on how leadership is not an event, but rather requires a consistent approach to affect the climate and eventually shape the culture of your school.

Perfect for new and experienced principals, for independent professional reading or for leadership courses, this practical book will leave you feeling inspired and ready to do the things that matter most for the people who ultimately matter most--the students.

Improve Your Creativity, Effectiveness, and Ultimately, Your Code

In Modern Software Engineering, continuous delivery pioneer David Farley helps software professionals think about their work more effectively, manage it more successfully, and genuinely improve the quality of their applications, their lives, and the lives of their colleagues.

Writing for programmers, managers, and technical leads at all levels of experience, Farley illuminates durable principles at the heart of effective software development. He distills the discipline into two core exercises: learning and exploration and managing complexity. For each, he defines principles that can help you improve everything from your mindset to the quality of your code, and describes approaches proven to promote success.

Farley's ideas and techniques cohere into a unified, scientific, and foundational approach to solving practical software development problems within realistic economic constraints. This general, durable, and pervasive approach to software engineering can help you solve problems you haven't encountered yet, using today's technologies and tomorrow's. It offers you deeper insight into what you do every day, helping you create better software, faster, with more pleasure and personal fulfillment.

• Clarify what you're trying to accomplish
• Choose your tools based on sensible criteria
• Organize work and systems to facilitate continuing incremental progress
• Evaluate your progress toward thriving systems, not just more legacy code
• Gain more value from experimentation and empiricism
• Stay in control as systems grow more complex
• Achieve rigor without too much rigidity
• Learn from history and experience
• Distinguish good new software development ideas from bad ones

Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.

This practical guide seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties.

Overview

Simple SysML for Beginners: Using CATIA No Magic Products is for beginners. This book is for beginning modelers who have just purchased a CATIA No Magic product that supports SysML modeling and are anxious to get started, but otherwise don't know too much about SysML and don't have much experience using SysML tools. The purpose of this book is to help the reader get through the initial learning curve and start the reader on the way to becoming proficient at SysML modeling.

The book is designed to be a tool companion for two of the more comprehensive books on SysML:

- SysML Distilled: A Brief Guide to the Systems Modeling Language by Lenny Delligatti.

- A Practical Guide to SysML, Third Edition: The Systems Modeling Language by Sanford Friedenthal et al..

The techniques shown in this book will work for any of the Dassault Systèmes CATIA Magic and CATIA No Magic products that support SysML modeling, including:

- MagicDraw with the SysML plugin.

- Cameo Systems Modeler.

- Cameo Enterprise Architecture.

- CATIA Magic System of Systems Architect.

- CATIA Magic Cyber-Systems Engineer.

CATIA(R), NoMagic(R), and Cameo(R) are trademarks of Dassault Systèmes.

Limitations

• Requirements Engineering - This book is not an exhaustive text on requirements engineering. However, the Further Reading appendix does list a number of excellent books for deeper understanding of this topic.
• Tool Version - The first edition of this book was authored primarily on Cameo Systems Modeler version 19. There may be minor differences in the procedures for later versions of the tool.
• Tool Manual - This is a beginner's introduction and is not a comprehensive reference for every feature of the tool.

Incorporate effective domain modeling into the software development process

Software design thought leader and founder of Domain Language, Eric Evans, provides a systematic approach to domain-driven design, presenting an extensive set of design best practices, experience-based techniques, and fundamental principles that facilitate the development of software projects facing complex domains. Intertwining system design and development practice, this book incorporates numerous examples based on actual projects to illustrate the application of domain-driven design to real-world software modeling and development.

• Domain Model: Part I outlines the goals of domain-driven development, defines terms, and gives an overview of the implications of using the domain model to drive communication and design
• Model-Driven Design: Part II condenses a core of best practices in object-oriented domain modeling into a set of basic building blocks and focuses on the kinds of decisions that keep the model and implementation aligned with each other, each reinforcing the other's effectiveness
• Refactoring: Part III delves into modeling principles that can guide choices along the way, and techniques that help direct the search
• Strategic Design: Part IV explores a triad of principles that apply to the system as a whole: context, distillation, and large-scale structure

Throughout the book, discussions are illustrated not with over-simplified, problems, but with realistic examples adapted from actual projects. With this book in hand, object-oriented developers, system analysts, and designers will have the guidance they need to organize and focus their work, create rich and useful domain models, and leverage those models into quality, long-lasting software implementations.

The book is a fun read. Eric has lots of interesting stories, and he has a way with words. I see this book as essential reading for software developers--it is a future classic.

--Ralph Johnson, author of Design Patterns

Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering.

How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the world's leading practitioners construct and maintain software. This book covers Google's unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization.

You'll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code:

• How time affects the sustainability of software and how to make your code resilient over time
• How scale affects the viability of software practices within an engineering organization
• What trade-offs a typical engineer needs to make when evaluating design and development decisions

Today, investment in financial technology and digital transformation is reshaping the financial landscape and generating many opportunities. Too often, however, engineers and professionals in financial institutions lack a practical and comprehensive understanding of the concepts, problems, techniques, and technologies necessary to build a modern, reliable, and scalable financial data infrastructure. This is where financial data engineering is needed.

A data engineer developing a data infrastructure for a financial product possesses not only technical data engineering skills but also a solid understanding of financial domain-specific challenges, methodologies, data ecosystems, providers, formats, technological constraints, identifiers, entities, standards, regulatory requirements, and governance.

This book offers a comprehensive, practical, domain-driven approach to financial data engineering, featuring real-world use cases, industry practices, and hands-on projects.

You'll learn:

The data engineering landscape in the financial sector

Specific problems encountered in financial data engineering

The structure, players, and particularities of the financial data domain

Approaches to designing financial data identification and entity systems

Financial data governance frameworks, concepts, and best practices

The financial data engineering lifecycle from ingestion to production

The varieties and main characteristics of financial data workflows

How to build financial data pipelines using open source tools and APIs

Tamer Khraisha, PhD, is a senior data engineer and scientific author with more than a decade of experience in the financial sector.

Methods of delivering software are constantly evolving in order to increase speed to market without sacrificing reliability and stability. Mastering development end to end, from version control to production, and building production-ready code is now more important than ever. Continuous deployment takes it one step further. This method for delivering software automates the final step to production and enables faster feedback and safer releases.

Based on years of work with medium to large organizations at Thoughtworks, author Valentina Servile explains how to perform safe and reliable deployments with no manual gate to production. You'll learn a framework to perform incremental, safe releases during everyday development work, structured exclusively around the challenges of continuous deployment in nontrivial, distributed systems. Complete with interviews and case studies from fellow industry professionals.

Close the feedback loop and leverage the production environment to manage your end-to-end development lifecycle efficiently. This book helps you:

• Take observability, performance, test automation, and security into account when splitting work into increments
• Create a daily development plan that takes immediate deployments to production into account
• Deploy work in progress to production incrementally without causing regressions
• Use patterns to refactor live functionality and alter persistence layers
• Test and release features in production using different feature toggle configurations

Software is everywhere today, but countless software products and projects die a slow death without ever making any impact. The result is a tremendous amount of time and money wasted due to wrong assumptions, lack of focus, poor communication of objectives, lack of understanding and misalignment with overall goals. There has to be a better way to deliver This handbook is a practical guide to impact mapping, a simple yet incredibly effective method for collaborative strategic planning that helps organisations make an impact with software. Impact mapping helps to create better plans and roadmaps that ensure alignment of business and delivery, and are easily adaptable to change. Impact mapping fits nicely into several current trends in software product management and release planning, including goal-oriented requirements engineering, frequent iterative delivery, agile and lean software methods, lean startup product development cycles, and design thinking. About the Author Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. Gojko won the 2012 Jolt Award for the best book, was voted by peers as the most influential agile testing professional in 2011, and his blog won the UK Agile Award for the best online publication in 2010.

In just five years, Kubernetes has radically changed the way developers and ops personnel build, deploy, and maintain applications in the cloud. With this book's updated third edition, you'll learn how this popular container orchestrator can help your company achieve new levels of velocity, agility, reliability, and efficiency--whether you're new to distributed systems or have been deploying cloud native apps for some time.

Brendan Burns, Joe Beda, Kelsey Hightower, and Lachlan Evenson--who have worked on Kubernetes at Google and beyond--explain how this system fits into the life cycle of a distributed application. Software developers, engineers, and architects will learn ways to use tools and APIs to automate scalable distributed systems for online services, machine learning applications, or even a cluster of Raspberry Pi computers.

This guide shows you how to:

• Create a simple cluster to learn how Kubernetes works
• Dive into the details of deploying an application using Kubernetes
• Learn specialized objects in Kubernetes, such as DaemonSets, jobs, ConfigMaps, and secrets
• Explore deployments that tie together the lifecycle of a complete application
• Get practical examples of how to develop and deploy real-world applications in Kubernetes

As the digital economy changes the rules of the game for enterprises, the role of software and IT architects is also transforming. Rather than focus on technical decisions alone, architects and senior technologists need to combine organizational and technical knowledge to effect change in their company's structure and processes. To accomplish that, they need to connect the IT engine room to the penthouse, where the business strategy is defined.

In this guide, author Gregor Hohpe shares real-world advice and hard-learned lessons from actual IT transformations. His anecdotes help architects, senior developers, and other IT professionals prepare for a more complex but rewarding role in the enterprise.

This book is ideal for:

• Software architects and senior developers looking to shape the company's technology direction or assist in an organizational transformation
• Enterprise architects and senior technologists searching for practical advice on how to navigate technical and organizational topics
• CTOs and senior technical architects who are devising an IT strategy that impacts the way the organization works
• IT managers who want to learn what's worked and what hasn't in large-scale transformation

As a Quick Guide to Business Analysis, the book explains international techniques and tools such as:

- User stories
- Use cases
- MVP (minimum viable product)
- Requirements documents
- User interface prototypes
- Lean UX (user experience) design
- Vision and scope documents
- Business cases
- Feasibility analysis
- Personas and user profiles
- Product backlogs
- Usability tests
- Value proposition

that can be used in developing and releasing:

- Software,
- Business solutions,
- Technological products,
- Mobile applications,
- E-businesses and,
- Business processes

within tight project deadlines by applying lean principles.

A real life case study with sample project documents and diagrams is used to more practically explain these international tools, techniques, and lean principles to a broad range of practitioners, including:

- Business analysts, systems analysts, developers and project managers
- Entrepreneurs, product owners and product managers
- Consultants, UX designers and marketing specialists
- C-suite executives, investors and managers of companies of all sizes.

Design and build Internal Developer Platforms (IDPs) with future-oriented design strategies, using the Platform as a Product mindset

Key Features:

- Comprehensive guide to designing platforms that create value and drive user adoption

- Expert insights on shifting to a product-centric mindset for architects and platform teams

- Best practices for managing platform complexity, reducing technical debt, and ensuring continuous evolution

Book Description:

As technology evolves, IT talent shortages and system complexity make it essential to have structured guidance for building scalable, user-focused platforms. This book provides platform engineers and architects with practical strategies to develop internal development platforms that enhance software delivery and operations.

You'll learn how to identify end users, understand their needs, and define platform goals with a focus on self-service solutions for cloud-native environments. Using real-world examples, the book demonstrates how to build platforms within and for the cloud, leveraging Kubernetes. It also explores the benefits of a product-centric approach to platform engineering, emphasizing early end-user involvement and flexible design principles that adapt to future requirements.

Additionally, the book covers techniques for maintaining a sustainable platform while minimizing technical debt. By the end, you'll have the knowledge to design, define, and implement platform capabilities that align with your organization's goals.

What You Will Learn:

- Make informed decisions aligned with your organization's platform needs

- Identify missing platform capabilities and manage that technical debt effectively

- Develop critical user journeys to enhance platform functionality

- Define platform purpose, principles, and key performance indicators

- Use data-driven insights to guide product decisions

- Design and implement platform reference and target architectures

Who this book is for:

This book is for platform engineers, architects, and DevOps professionals responsible for designing and managing internal development platforms. It is also useful for decision-makers involved in optimizing software delivery and operations in cloud-native environments. Familiarity with cloud computing, Kubernetes, and CI/CD concepts is helpful but not required, as the book provides practical guidance on platform engineering, self-service solutions, and managing technical debt.

Table of Contents

- Platform Engineering and the Art of Crafting Platforms

- Understanding Platform Architecture to Build Platform as a Product

- Building the Foundation for Supporting Platform Capabilities

- Architecting the Platform Core - Kubernetes as a Unified Layer

- Integration, Delivery, and Deployment - Automation is Ubiquitous

- Build for Developers and Their Self-Service

- Building Secure and Compliant Products

- Cost Management and Best Practices

- Choosing Technical Debt to Unbreak Platforms

- Crafting Platform Products for the Future

Learn how to get started with Futures Thinking. With this practical guide, Phil Balagtas, founder of the Design Futures Initiative and the global Speculative Futures network, shows you how designers and futurists have made futures work at companies such as Atari, IBM, Apple, Disney, Autodesk, Lufthansa, and McKinsey & Company.

This book demystifies the process of Futures Thinking into a language that's practical and useful for both designers and strategists. You'll learn about Strategic Foresight for using ideas about the future to anticipate and prepare for change; explore Speculative Design to deal with the relationship between science, technology, and humans; and Design Fiction to explore and critique possible futures.

Balagtas also shares stories from his journey to build a global community and describes how he works with clients to reshape the futures vocabulary. With this guide, you'll learn how to:

• Prepare your client, team, and/or audience for futures
• Facilitate and work with the fundamental methods and frameworks
• Gain advocacy and support within your organization
• Provide measurable value from the process and outcomes
• Build a futures culture and team
• Sustain a culture and support system beyond projects

From fundamentals and design patterns to the latest techniques such as generative AI, machine learning and cloud native architecture, gain all you need to be a pro Solutions Architect crafting secure and reliable AWS architecture.

Book Description

Build a strong foundation in solution architecture and excel in your career with the Solutions Architect's Handbook. Authored by seasoned AWS technology leaders Saurabh Shrivastav and Neelanjali Srivastav, this book goes beyond traditional certification guides, offering in-depth insights and advanced techniques to meet the specific needs and challenges of solutions architects today.

This edition introduces exciting new features that keep you at the forefront of this evolving field. From large language models and generative AI to deep learning innovations, these cutting-edge advancements are shaping the future of technology. Key topics such as cloud-native architecture, data engineering architecture, cloud optimization, mainframe modernization, and building cost-efficient, secure architectures remain essential today. This book covers both emerging and foundational technologies, guiding you through solution architecture design with key principles and providing the knowledge you need to succeed as a Solutions Architect. It also sharpens your soft skills, providing career-accelerating techniques to stay ahead.

By the end of this book, you will be able to harness cutting-edge technologies, apply practical insights from real-world scenarios, and enhance your solution architecture skills with the Solutions Architect's Handbook.

What you will learn

• Explore various roles of a solutions architect in the enterprise
• Apply design principles for high-performance, cost-effective solutions
• Choose the best strategies to secure your architectures and boost availability
• Develop a DevOps and CloudOps mindset for collaboration, operational efficiency, and streamlined production
• Apply machine learning, data engineering, LLMs, and generative AI for improved security and performance
• Modernize legacy systems into cloud-native architectures with proven real-world strategies
• Master key solutions architect soft skills

Who this book is for

This book is for software developers, system engineers, DevOps engineers, architects, and team leaders who already work in the IT industry and aspire to become solutions architect professionals. Solutions architects who want to expand their skillset or get a better understanding of new technologies will also learn valuable new skills. To get started, you'll need a good understanding of the real-world software development process and some awareness of cloud technology.

Table of Contents

1. Solutions Architecture in an Organization
2. Principles of Solution Architecture Design
3. Cloud Migration and Cloud Architecture Design
4. Solution Architecture Design Patterns
5. Cloud-Native Architecture Design Patterns
6. Performance Considerations
7. Security Considerations
8. Architectural Reliability Considerations
9. Operational Excellence Considerations
10. Cost Considerations
11. DevOps and Solution Architecture Framework
12. Data Engineering for Solution Architecture
13. Machine Learning Architecture

(N.B. Please use the Read sample option to see further chapters)

Today's HR Information Systems (HRIS) aren't just tools for managing recruitment, payroll, and benefits-they're the lifeline of modern businesses ranging from Retail to Healthcare, Imagine the scale of world's largest private employer with more than 1.8 employees data and helping them stay agile in a fast-changing world. But here's the challenge: how do you ensure all these systems work together without hiccups or inefficiencies? That's the exact question HR Information Systems Integration Patterns by Sudheer Devaraju sets out to answer.Why This Book Matters

This isn't your typical technical manual. It is a practical, user-friendly guide designed to help HR leaders, Domain experts, IT architects, and system implementers build scalable, secure, and future-proof HRIS integrations and user experiences. Using proven strategies and real-world examples, starting from mobile applications, real-time data transfer mechanism to file feeds this book walks you step-by-step through the architecture and implementation process.

Author Bio

Sudheer Devaraju is a distinguished HR Information Systems architect with over 11 years of experience in designing and implementing cutting-edge HR integrations for global organizations, including Fortune 1 companies. Certified in Workday, SAP, and advanced API integration, Sudheer brings a wealth of expertise in creating scalable and efficient HR ecosystems tailored to meet complex organizational needs.

Beyond his consulting work, Sudheer is passionate about sharing his knowledge and driving innovation in the HR technology space. As an author and researcher, he has published insightful books and research papers, contributed as a peer reviewer for industry experts, mentored rising professionals at Walmart, and led impactful workshops. His commitment to advancing HRIS systems continues to inspire and empower professionals worldwide.

Emerging practices, collaboration tools, and effective techniques for incorporating your key stakeholders into the software design process.

Don't spend months building the wrong software! Collaborative Software Design is a unique and practical guide for effectively involving all stakeholders in the design of software to ensure sustainable design decisions.

In Collaborative Software Design you'll learn how to:

- Prepare and facilitate collaborative modeling sessions with tools such as Business Model Canvas, Event Storming, Domain Storytelling, Example Mapping, and Wardley Mapping
- Pick and apply heuristics for modeling software design
- Techniques for getting all needed knowledge from the group
- The influence of ranking
- The impact and opportunities of cognitive bias
- Resistance and conflict resolution
- Practices for following up after a modeling session
- Document the session and report to stakeholders

Collaborative Software Design combines its authors' deep experience in behavioral science, decision-making theory and software architecture into an essential guide for making collaborative design decisions. You'll learn to use process visualizations, engaging sessions, and social dynamic management to ensure every stakeholder is contributing their vital insights to a project. Best of all, the skills you'll learn make it easy for software teams to develop software directly with their stakeholders--no need to rely on a centralized or top-down design.

Forewords by Diana Montalion and Trond Hjorteland.

Purchase of the print book includes a free eBook in PDF and ePub formats from Manning Publications.

About the technology

Delivering high-quality software requires the active participation of all stakeholders in the design process. But how do you align individuals with different roles, perspectives, and priorities to create sustainable software? Collaborative Software Design presents proven strategies that you can use to foster productive decision making, resolve conflicts and uncertainties, and elevate the quality of design outcomes.

About the book

In Collaborative Software Design, you'll explore principles, techniques, and tools to promote safe communication as you discover business problems, formalize requirements, and implement a software project. It highlights established collaborative modeling tools like Event Storming, Example Mapping, Wardley Mapping, and Domain Storytelling, and introduces unique approaches for managing cognitive biases, conflict, and organizational hierarchy. Whether you're a business stakeholder, a technical contributor, or a professional facilitator, you'll learn how to hear and benefit from every voice in the room.

What's inside

- Prepare and lead collaborative modeling sessions
- Turn conflict into innovation
- Make sustainable software design decisions
- Improve software design from a sociotechnical perspective

About the reader

For anyone involved in the software development process.

About the author

Evelyn van Kelle, Gien Verschatse, and Kenny Baas-Schwegler are internationally recognized experts in collaborative modeling and organizational decision making for sociotechnical systems.

The technical editor on this book was Charlie Schafer.

Table of Contents

1 The need for collaborative software design
2 What is collaborative modeling?
3 Using collaborative modeling for design and architecture
4 The ingredients of collaborative modeling
5 Facilitating collaborative modeling
6 The influence of ranking
7 The effect and opportunities of cognitive bias
8 Resistance and conflict resolution
9 Making sustainable design decisions
10 Managing unsolvable problems
11 Communicating and documenting decisions
12 Collaborative modeling beyond software design
Appendix A