Analysis and Design,Domain Driven Design - Hannes's Mind Maze

Browse by Tags

All Tags » Analysis and Design » Domain Driven Design (RSS)

Jimmy Nilsson is coming to Cape Town by hannes

In collaboration with PBT Group in Cape Town, South Africa, Jimmy Nilsson will be giving a presentation called "Is Domain-Driven Design more than Entities and Repositories?" and Niclas Nilsson will give a presentation called "Dynamic Languages for Statically Typed Minds". Read more here . Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!

More on Domain Driven Design by hannes

If you want to listen to what Eric Evans has to say about Domain Driven Design go download his interview with .Net rocks here . If you want to know more about DDD go the official DDD-site here . Share this post: email it! | bookmark it! | digg it! | reddit! | kick it! | live it!

LINQ promotes DDD by hannes

I think the biggest beneficiary of LINQ will one day be Domain Driven Design. Jimmy Nilsson thinks so too. " What I'm thinking about for instance is LINQ which fast approaching, and I believe it might be a signal to lots of Microsoft-developers wanting to go for DDD. I also see LINQ as a technique that solves what I solved with NWorkspace, but without you having to write your own abstraction." Read Post ADDDP . Share this post: email it! | bookmark it! | digg it! | reddit! | kick it...

Splitting up the work by hannes

I like reading Joel’s blog on software and in his latest post he talks about Apple Safari for Windows: The world's slowest web browser and the possible reason for the lack of performance as explained by Raymond Chen in one of his post, Performance gains at the cost of other components . In the end it all comes down to splitting up the work. Currently I work on a domain driven project which shows the same symptoms, the application start up takes awfully long. I think the reason for our problems...

Why analyst should be building the Domain Layer by hannes

I had a very interesting discussion the other day with some of my fellow analysts about application development in an ideal world using Domain Driven Design. Layering according to Domain Driven Development can loosely be divided into 4 layers. These layers are the User Interface, Application, Domain and Infrastructure layers. On top we have the User Interface layer which is a dumb layer. Next is the Application layer that co-ordinates the system, in other words it controls the flow in the system...
Powered by Community Server (Commercial Edition), by Telligent Systems