![]() Indeed, there are countless legacy systems like what I described still in existence in any number of industries. Software systems of prior eras had a peculiar, and not especially user-friendly design: think a specialized technician punching numbers into a 1980's monochrome, text-based user interface and you get the picture. This is important, especially in SaaS systems, because the business rules and processes represent the very problem that your solution is trying to solve. Think, real world rules and objects of the business. This means business complexity: that which is introduced of necessity by trying to model what the business actually does. Behavior-Centric ApplicationsÄomain-Driven Design was first articulated by Eric Evans in 2003 in his seminal book, Domain-Driven Design: Tackling Complexity in the Heart of Software. In a nutshell, he describes it as a methodology for tackling complexity in the heart of business applications (remember what I said two posts ago about managing complexity?). As before, I will periodically refer back to the demo application to elaborate on certain concepts. In this entry, I give a brief overview of Domain-Driven Design (DDD) and discuss its importance in modern software development. What is Domain-Driven Design? It is a software design methodology which seeks to efficiently create business logic components and functionality from business requirements, typically by working closely with domain experts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |