Tracking change and innovation in the enterprise software development community
Rule your SOA
with CentraSite
standards-based
registry/repository
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Plan-driven dev
Environments and
Agile tutorials at the
Better Software
Conference & Expo!
Create REST
-enabled Web Apps
with Project Zero
from IBM.
Introducing the
SpringSource
Application Platform:
Next-gen Java
AppServer
In this interview, Jimmy focuses on LINQ to SQL and ORM. Jimmy has tried to create a similar technology to LINQ to SQL in the past, but without similar results. While LINQ to SQL is a step in the right direction, .NET still lags behind other programming languages in object-relational mapping capabilities.
Peter Ritchie raised concern about TDD and BDD keeping practitioners from writing good unit tests. He cites an over-reliance on “interaction testing", a core mantra and essence of TDD and BDD, as a driver with tendency to result in incomplete unit testing.
Naked Objects is an architectural pattern and a framework for developing applications where domain objects takes a central role. Naked Objects recently released version 3.0 with support for Java 1.5, injection, an alternate UI, Hibernate object store, integrated security and contributed actions. InfoQ took the opportunity to speak with Richard Pawson, inventor of the Naked Objects pattern.
Using a domain model is rarely as easy as just creating the actual domain model classes and then using them. Soon enough one discovers that sizable amounts of infrastructure code will also be required in support of the domain model. In this article, Mats Helander explains how to use Domain Model Management to handle this complexity in a simple way.
InfoQ has decided to bring you what we think is one of the best books on the subject: Applying Domain-Driven Design and Patterns by Jimmy Nilsson. Don't let the subtitle fool you; this book is on domain-driven design with techniques and discussions suitable for any object oriented programming language. InfoQ has arranged for a sample chapter from courtesy of Addison Wesley Professional.
Business users doing programming? In this interview, Charles Simonyi presents a radical new way of building software that separates business knowledge from software engineering knowledge. The claim is to simplify the creation process for software as business experts directly contribute using their customary domain description which results in accelerated innovation.
Ever since Eric Evans wrote the book Domain-Driven Design in 2004 he has been a significant voice advancing domain modeling and design concepts. In this interview with Floyd Marinescu he talks about some of the recent refinements in Domain-Driven Design and how people are advancing the field today.
This talk introduces two broad principles for strategic design. 'Context mapping' addresses the fact that different groups model differently. 'Core domain' distills a shared vision of the system's "core domain" and provides a systematic guide to when "good enough" is good enough versus when to push for excellence.
This talk will outline some of the foundations of domain-driven design:How models are chosen and evaluated;How multiple models coexist;How the patterns help avoid the common pitfalls, such as overly interconnected models;How developers and domain experts together in a DDD team engage in deeper exploration of their problem domain and make that understanding tangible as a practical software design.
Domain Driven Design is a vision and approach for designing a domain model that reflects a deep understanding of the business domain. This book is a short, quickly-readable summary and introduction to the fundamentals of DDD; it does not introduce any new concepts; it attempts to concisely summarize the essence of what DDD is, drawing mostly Eric Evans' book, as well other sources since published such as Jimmy Nilsson's Applying Domain Driven Design, and various DDD discussion forums.
