
Handbook of Software Engineering Methods - 2nd Edition
![]()
![]()
![]()
![]()
![]()
Lara Letaw, Oregon State University
Copyright Year:
Publisher: Oregon State University
Language: English
Formats Available
Conditions of Use
Attribution-NonCommercial
CC BY-NC
Reviews
Reviewed by Dana Nelson, Adjunct Faculty, Oregon Institute of Technology on 12/30/25
There is no index, however, there is a table of contents and a glossary. read more
![]()
![]()
![]()
![]()
![]()
Reviewed by Dana Nelson, Adjunct Faculty, Oregon Institute of Technology on 12/30/25
Comprehensiveness
There is no index, however, there is a table of contents and a glossary.
Content Accuracy
The content appears to be accurate error-free and unbiased.
Relevance/Longevity
The topics covered are not rapidly evolving. They are presented in a way that doesn’t shorten the lifetime. I suspect that near-term future updates would generally be additional topics which could easily be added as additional chapters.
Clarity
The text is approachable. There are summaries in each chapter. Terms are defined in the chapter and in the glossary.
Consistency
The materials have internally consistent terminology and formatting throughout.
Modularity
Chapters are generally no more than 15 pages and are divided into smaller sections. The book could easily be divided into smaller reading sections. Largely, the chapters are about independent topics that could readily be reordered/reorganized.
Organization/Structure/Flow
The ordering of the book overall and within individual chapters seems logical.
Interface
I didn’t notice any interface, navigation issues or other display feature problems. Images/charts are acceptable. At least in the PDF version, the internal links (e.g. links in the table of contents) and external links (e.g. links to web resources) seem to be functional/correct.
Grammatical Errors
I didn’t notice any grammatical issues.
Cultural Relevance
I didn't notice any issues
Table of Contents
- Introduction
- Agile
- Project Management and Teamwork
- Requirements
- Unified Modeling Language Class and Sequence Diagrams
- Monolith versus Microservice Architectures
- Paper Prototyping
- Inclusivity Heuristics
- Code Smells and Refactoring
- Conclusion
- Glossary
- References
- Accessibility and Versioning
About the Book
Software engineering can help people create sustainable, extensible programs that solve problems people care about.
I won’t tell you how to be a software engineer; you’ll learn that over time by doing it. Instead, this book is about software engineering methods: Ways people achieve specific objectives in software engineering—that can save your project. My hope is that, after reading this book (or parts of it), you’ll feel better equipped for software engineering.
About the Contributors
Author
Lara Letaw is an Ecampus computer science instructor who, after working as a software engineer and UI designer, entered academia to research and develop software inclusivity innovations through her graduate work in computer science. She graduated from OSU in 2018 with an M.S. in computer science (Software Innovation). She currently teaches and develops undergraduate and graduate-level courses for the online CS program. She is an OSU Ecampus Research Fellow (2020-21), wrote a free and open software engineering textbook through the OSU Ecampus Open Educational Resources (OER) Affordable Learning Grant program (2020-21), and was awarded an OSU College of Engineering Online Teaching Award in 2021. In addition, she has co-authored multiple publications on inclusive technology design.