This link has been bookmarked by 73 people . It was first bookmarked on 24 Jun 2006, by Eoin Lane.
-
23 Aug 16
-
25 Aug 15
-
27 Nov 14
-
27 Dec 13
-
04 Jun 13
-
22 May 12
-
02 Feb 12
-
06 Jun 11
-
22 Mar 11
-
08 Feb 11
-
20 Oct 10
-
19 Apr 10
-
07 Apr 10
-
07 Mar 10
-
01 Mar 10
-
16 Sep 09
-
23 Jul 09
-
04 Jun 09
-
09 May 09
-
13 Jan 09
-
25 Dec 08
-
21 Nov 08
-
05 Sep 08
-
MDD is an approach to software development where extensive models are created before source code is written
-
as the RUP/EUP
-
The difference with AMDD is that instead of creating extensive models before writing source code you instead create agile models which are just barely good enough that drive your overall development efforts.
-
The envisioning effort is typically performed during the first week of a project, the goal of which is to identify the scope of your system and a likely architecture for addressing
-
isn't to write detailed specifications, that proves incredibly risky in practice,
-
what you think the system should do
-
At the beginning of each Construction iteration the team must plan the work that they will do that iteration
-
work required for each requirement
-
you must be able to accurately estimate the
-
vast majority of modeling sessions involve a few people, usually just two or three
-
13 Aug 08
-
05 Aug 08
-
10 Jul 08
-
06 Mar 08
-
21 Sep 07
-
your goal is to build a shared understanding, it isn’t to write detailed documentation. A critical success factor is to use inclusive modeling techniques which enable active stakeholder participation.
-
AMDD is a critical strategy for scaling agile software development beyond the small, co-located team approach
-
Through initial, high-level modeling you can gain the knowledge that you need to guide the project but choose to wait to act on it.
-
The secret is to keep things simple. You don’t need to model a lot of detail, you simply need to model enough
-
Why does model storming on a JIT basis work much better than trying to model everything up front? First, like it or not, the requirements are going to change throughout the project. Second, by waiting to analyze the details JIT, you have much more domain knowledge than if you had done so at the beginning of a project. For example, if a requirement is to be implemented three months into a project, if you explore the details of that requirement at that point you have three months more domain knowledge than if you had done so at the beginning of the project, therefore you can ask more intelligent questions. Third, if you've been delivering working software on a regular basis your stakeholders now have three months worth of experience with the system that you've built. In other words, they can give you better answers. Fourth, modeling everything up front appears to result in significant wastage.
-
test-driven design (TDD) is the combination of TFD and refactoring
-
where your team will spend the majority of its time,
-
-
13 Sep 07
-
12 Sep 07
-
11 Sep 07
Leandro Rodrigo Saad Cruzotes confirmatory testing of your application c
-
23 Nov 06
-
04 Oct 06
-
20 Sep 06
-
27 Aug 06
-
24 Jun 06
-
17 Feb 06
-
08 Jul 05
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.