Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Modern Programming: Object Oriented Programming and Best Practices

You're reading from   Modern Programming: Object Oriented Programming and Best Practices Deconstruct object-oriented programming and use it with other programming paradigms to build applications

Arrow left icon
Product type Paperback
Published in Jun 2019
Publisher Packt
ISBN-13 9781838986186
Length 266 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Graham Lee Graham Lee
Author Profile Icon Graham Lee
Graham Lee
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

About the Book 1. Part One – OOP The Easy Way FREE CHAPTER
2. Antithesis 3. Thesis 4. Synthesis 5. Part Two – APPropriate Behavior
6. Tools That Support Software Development 7. Coding Practices 8. Testing 9. Architecture 10. Documentation 11. Requirements Engineering 12. Learning 13. Critical Analysis 14. Business 15. Teamwork 16. Ethics 17. Philosophy

Domain-Driven Design

Domain-Driven Design (DDD) is a term introduced in the 2004 book of the same namehttp://domaindrivendesign.org/books/evans_2003, though most of its principles have been around quite a bit longer among practitioners of object-oriented analysis and design. Indeed, the core of DDD can be thought of as deriving from the simulation techniques employed in Simula 67 – a language that influenced the design of C++.

Simply put, much software (particularly "enterprise" software) is created as a solution to a particular problem. Therefore, software should be designed by software experts in conjunction with domain experts. They should use a shared model of the problem domain, so that it's clear the whole team is trying to solve the same problem.

In an attempt to reduce communication problems, a "ubiquitous language" is defined – a common glossary of terms that's used throughout the documentation and the software. This includes the...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime