EBOOK
About
Software engineering is not a collection of concepts to memorize; it is a sequence of decisions to make. This textbook is built around that conviction.
Written for graduate and upper-division undergraduate students, Software Engineering: A Practice-Driven Introduction guides readers through the complete arc of a real software project: from the first requirements conversation to a deployed, containerized, production-ready application. Each chapter introduces a concept, then immediately puts it to work. There are no ideas here that do not have a job to do.
The book is organized around three phases that mirror industry practice. The Foundations section covers requirements engineering, systems modeling and UML, software architecture and design patterns, UI/UX design, and Agile methodology, the thinking work that determines whether a project succeeds before a line of code is written. The Construction section addresses version control workflows, continuous integration and deployment, API and data management, and cloud deployment, the building work of turning a plan into working software. The Operations and Stewardship section tackles containerization, software security, technical debt, professional ethics, and the long-term craft of maintaining systems that outlive their original authors.
Three commitments shape every chapter. Immediate application means every concept is paired with a concrete artifact that students can produce the same week they encounter it. Progressive depth means topics introduced early in the semester return later with greater complexity, so students see how engineering decisions compound over time. Honest craft means the book does not pretend software development is cleaner or more predictable than it actually is; it prepares students for the real conditions of professional practice.
Designed as an Open Educational Resource, this textbook is freely adaptable for course adoption. It is appropriate for any course in which students are expected to build, document, deploy, and reflect on a real software system.
Students who finish this book will not just understand software engineering. They will have practiced it.
Written for graduate and upper-division undergraduate students, Software Engineering: A Practice-Driven Introduction guides readers through the complete arc of a real software project: from the first requirements conversation to a deployed, containerized, production-ready application. Each chapter introduces a concept, then immediately puts it to work. There are no ideas here that do not have a job to do.
The book is organized around three phases that mirror industry practice. The Foundations section covers requirements engineering, systems modeling and UML, software architecture and design patterns, UI/UX design, and Agile methodology, the thinking work that determines whether a project succeeds before a line of code is written. The Construction section addresses version control workflows, continuous integration and deployment, API and data management, and cloud deployment, the building work of turning a plan into working software. The Operations and Stewardship section tackles containerization, software security, technical debt, professional ethics, and the long-term craft of maintaining systems that outlive their original authors.
Three commitments shape every chapter. Immediate application means every concept is paired with a concrete artifact that students can produce the same week they encounter it. Progressive depth means topics introduced early in the semester return later with greater complexity, so students see how engineering decisions compound over time. Honest craft means the book does not pretend software development is cleaner or more predictable than it actually is; it prepares students for the real conditions of professional practice.
Designed as an Open Educational Resource, this textbook is freely adaptable for course adoption. It is appropriate for any course in which students are expected to build, document, deploy, and reflect on a real software system.
Students who finish this book will not just understand software engineering. They will have practiced it.