000 | 00549nam a2200169Ia 4500 | ||
---|---|---|---|
999 |
_c14256 _d14256 |
||
008 | 161214s9999 xx 000 0 und d | ||
020 |
_a9780321125217 _c(hbk) |
||
082 |
_a005.1 _bEVA |
||
100 | _aEvans, Eric | ||
245 | 0 | _aDomain-driven design: Tackling complexity in the heart of software | |
260 |
_aBoston: _bAddison-Wesley, _c2003 |
||
300 |
_a529 p.; _bIllus. Index.: _c24 cm. |
||
365 |
_aINR _b2399.52 |
||
520 | _a "This is not a book about specific technologies. It offers readers 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 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 development.". "Readers learn how to use a domain model to make a complex development effort more focused and dynamic. A core of best practices and standard patterns provides a common language for the development team. A shift in emphasis - refactoring not just the code but the model underlying the code - in combination with the frequent iterations of Agile development leads to deeper insight into domains and enhanced communication between domain expert and programmer. Domain-Driven Design then builds on this foundation, and addresses modeling and design for complex systems and larger organizations." "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. | ||
650 | _aComputer software-Development | ||
650 | _aDomain-driven design | ||
650 | _aObject-Oriented programming | ||
650 | _aCrunching Knowledge | ||
650 | _aModel Integrity | ||
942 |
_2ddc _cBK |