Individuals can benefit from reading this book. The XP process attempts to increase team communication, but model and design choices clarify or confuse communication. But past design choices make refactoring either itself easier or harder. The XP process assumes that you can improve a design by refactoring, and that you will do this often and rapidly. XP works best for developers with a sharp design sense. Developers and domain experts must have a close relationship throughout the entire project. This book will discuss both design and process, and their intersection.Ģ. Complex domain designs should be based on a model.ĭomain driven design is both a way of thinking and a set of priorities, aimed at accelerating software projects. For most software projects, the primary focus should be on the domain and domain logic.Ģ. When complexity gets out of hand, developers can no longer understand the the software well enough to change or extend it easily and safely.ġ. It is a synthesis of widely accepted best practices along with Evans' insights and experiences.ĭomain driven design facilitates the iterative invention/discovery of domain models that simplify software development.Ī poor domain model can doom a project as well as a lack of technical expertise can. This book provides a framework for making design decisions and a techincal vocabulary for discussin domain design.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |