Domain-Driven Design encourages to analyse the domain deeply in a process called Supple Design. In his book (the blue book) and in his talks Eric Evans gives some examples of this process, and in this blog in several parts I will suggest some sources of inspirations and some recommendations drawn from my practice in order to help about this process.
Your cross-cutting concerns are someone else core domain
déc 22nd, 2009
Consider a domain, for example an online bookshop project that we call BuyCheapBooks. The Ubiquitous Language for this domain would talk about Book, Category, Popularity, ShoppingCart etc.
Business Domains
From scratch, coding this domain can be quite fast, and we can play with the fully unit-tested domain layer quickly. However if we want to ship, we will [...]
Big battles are won on small details
déc 17th, 2009
Small details matter because you deal with them often. Any enhancement you make thus yields a benefit often, hence a bigger overall benefit. In other words: invest small care, get big return. This is an irresistible proposal!
Examples of small design-level details that I care about because I have experienced great payback from them:
Using Value Objects [...]
Principles for using annotations
déc 14th, 2009
Deciding where and how to place the annotations is not innocent. The last thing we want is to create extra maintenance effort because of the annotations. In other words, we want annotations that are stable, or that change for the same reasons and at the same time than the elements they annotate. This article suggests [...]
Degrees of freedom analysis
déc 1st, 2009
The concept of degrees of freedom looks so relevant to software development that I am wondering why it is not considered more often. Fortunately Michael L. Perry dedicates a full section of his blog to that concept. In this post I will quote a lot, please consider that as a sign of enthusiasm.
A common concept [...]
Many concepts look obvious because they are used often, not because they are really simple.
Small quantities that we encounter all the time in most projects, such as date, time, price, quantity of items, a min and a max… hardly are a subject of interest from developers “as it is obvious that we can represent them [...]
Patterns in general, not just design patterns
oct 18th, 2009
Over time, patterns have appeared on many different topics, not all related to programming. Here is a list of patterns and pointers to other lists of patterns, to illustrate two things:
Knowledge and experience in general can be packaged into patterns, often using the pattern form. Patterns are convenient for reuse, in any domain.
There are already [...]
Toward smarter dependency constraints (patterns to the rescue)
août 30th, 2009
Low coupling between objects is a key principle to help you win the battle against software entropy. Making sure your dependencies are under control matters. Several tools can enforce dependencies restrictions, such as JDepend. However in a real project with many classes, packages and modules, the real issue is how to decide and configure the [...]
The more patterns developers know, the most efficient they become within a team: it only takes one or two words (the pattern name) to communicate a design decision or proposal, instead of 10 mn of explanations. Communication also gets much more accurate and to-the-point (or less fuzzy).
Because patterns often form a pattern language, not only [...]
Sharing a common architecture or vision within a team
jan 21st, 2008
What do you think about when you hear the word “architecture” about software? Fowler defines it: whoNeedsArchitect “In most successful software projects, the expert developers working on that project have a shared understanding of the design system design. This shared understanding is called ‘architecture.’”.
However for most people the word “architecture” comes full of middleware [...]
Categories
- En français (4)
- General (2)
- Leisure (7)
- Music (14)
- Physical Computing (8)
- Programming (45)
- ddd (3)
- Patternity (12)
- Patterns (17)
Keywords
abstraction accessibility analysis api architecture arduino beat classdiagram convention ddd dependencies design domain drum machine education electronic experience hacking instrument intent interactive interface java language library methodology midi Music musical instrument oo pattern patternity problem Programming refactoring research rhythm solution syntax tool trick uml unittest visual xml-
See also
-
License
All original material of whatever nature created by Cyrille Martraire and included in this weblog and any related page, including the weblog's archive, is licensed under a Creative Commons License.