This link has been bookmarked by 40 people . It was first bookmarked on 23 Jul 2008, by alm.
-
04 May 17
-
29 Sep 14
-
08 Aug 13
-
19 Sep 11
-
14 Feb 11
smostafakMat Wall and Nik Silver explain how their has been using Domain-Driven Design in an evolving and Agile environment, at high traffic news site guardian.co.uk.
-
17 Oct 10
-
11 Oct 10
-
27 Sep 10
-
Domain driven design can be most readily applied to stable domains in which the key activity is for developers to capture and model what is in users' heads. But it becomes more challenging when the domain itself is in a state of flux and development. This is common in Agile projects, and happens also when the business itself is trying to evolve. This article examines how we used DDD in the context of a two-year programme of work to rethink and rebuild guardian.co.uk. We show how we ensured the evolving perceptions of our end-users were reflected in the software architecture, and how we implemented that architecture to ensure future changes. We provide details of important project processes and of specific evolutionary steps in the model.
-
There is a danger that this approach to domain modelling could lead to a monolithic model that becomes expensive to change if the business domain is very large. We are aware of this, and as our domain is constantly growing we need to ensure that this layer does not become too unwieldy. Currently this is not causing us a problem and the domain layer is quite large and complex. Working in an Agile environment we look to perform full production rollouts of all our applications every two weeks anyway. However, we are constantly looking at the cost of change of the code in this layer. If it begins to rise to an unacceptable level we will probably have to look at splitting the single model into multiple smaller models and providing adaption layers between each sub-model. We did not do this at the start of the project though, favouring the simplicity of a single model over the more complex dependency management issues that we would have to resolve with multiple models.
-
Very early on in the project, long before anyone reached for a computer keyboard and started working on code, we had decided that we would co-locate our developers, QAs, BAs and business people in the same room for the duration of the project. At this stage we had a small team of business and technical people, and we required only a modest first release. This ensured our model and our process were both fairly simple.
-
Our first objective was to get as clear an understanding of what our editors (a key constituent of our business representatives) were expecting for the first few iterations of the project
-
Although quite slow at first the process was fun. The editors found it very hands on; they were able to scribble things out and move objects around and then get immediate feedback from the developers as to whether the resulting model would meet their requirements. The technical people were all quite surprised and pleased with how quickly everyone became proficient in the process and all felt confident that the resulting system was going to satisfy their clients.
-
- The nature of writing software to a new and uncertain business model;
- Being tied to an old model;
- Business people going native.
Unfortunately, we have found particular challenges with applying DDD in the planning process, and particularly in an Agile environment where planning is continual. These problems are:
-
-
27 Nov 09
-
19 Nov 09
-
Domain driven design can be most readily applied to stable domains in which the key activity is for developers to capture and model what is in users' heads. But it becomes more challenging when the domain itself is in a state of flux and development.
-
over 18 million unique users and 180 million page impressions a month.
-
-
27 Oct 09
-
26 Mar 09
-
21 Mar 09
-
12 Mar 09
-
09 Feb 09
-
20 Nov 08
alexcuestaHow The Guardian rebuilt their sites
howto article articulo como TheGuardian periodico newspaper sites rebuilding development java web desarrollo guardian ddd domaindrivendesign domain-driven-design
-
25 Aug 08
-
Domain-Driven Design in an Evolving Architecture
-
-
16 Aug 08
Alex JonesMat Wall and Nik Silver explain how their has been using Domain-Driven Design in an evolving and Agile environment, at high traffic news site guardian.co.uk.
-
10 Aug 08
-
06 Aug 08
-
01 Aug 08
-
30 Jul 08
-
29 Jul 08
-
22 Jul 08
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.