*DD
This is a compiled list and relates to this post. In some cases Development and Design are interchangeable and I have only listed one.
- ADD
- Acceptance test Driven Development (aka ATDD) ; Very similar to BDD and you always start with your acceptance tests.
- BDD
- Behavior Driven Development; Link.
- CDD
- Comment Driven Development; Instead of (or as a complement to) your tests you write the comment for your method first and then implement it.
- Contract Driven Design; Another name for Design by Contract.
- DDD
- Domain Driven Design; Link.
- EDD
- Example Driven Development; This is suggested by many to be a better name for TDD since it focuses on what the "tests" really should be - examples.
- FDD
- Feature Driven Development; Similar to Story DD since you develop feature by feature.
- Fun Driven Development; Link.
- GDD
- Guru Driven Development; You have a really bright and/or experienced person on your team and he basically tells everybody exactly what to do.
- Guru Driven Design; You have a really bright and/or experienced person on your team and he does all the design work but not much implementing.
- HDD
- Help Driven Development; Similar to Comment DD and User guide DD but here you start with the help files.
- IDD
- Interrupt Driven Development;Occurs when the team is continuously interrupted and given new "highest priority" tasks. Similar to Management DD.
- Interface Driven Design; Extensive use of interfaces in design.
- JDD
- Junior Driven Development; Often used together with Guru Driven Design i.e. the main body of the team are juniors.
- KDD
- Kaizen Driven Development; Really having the Kaizen Mind when developing continuously trying to improve the application under development.
- LDD
- Lazy Driven Development; Always doing as little as possible to complete tasks. or getting others to do it...
- MDD
- Management Driven Development; Having management deeply involved in the development work.
- Model Driven Design; Using models such as UML models for design and then having tools generate the code from the models.
- NDD
- Nightly build Driven Development; Similar to Interrupt DD but interrupts occur only as result of nightly builds.
- ODD
- Output Driven Development; Another name for Value DD.
- Object Driven Design; Being strict with object oriented design when designing application.
- PDD
- Performance Driven Development; Having great performance is the most important factor when implementing new features.
- Process Driven Development; Link.
- QDD
- Quality Driven Development; Making over all quality the most important factor when implementing new features.
- RDD
- Reality Driven Development; Link.
- Responsibility Driven Development; Applying the single responsibility principle all the time.
- Result Driven Development; Link.
- Return Driven Development; Another term for Result DD.
- SDD
- Story Driven Development; Implementing a single user story at the time in the team.
- Story Driven Design; making the design evolve as you take more and more user stories into account.
- TDD
- Test Driven Development; Link.
- UDD
- User guide Driven Development (aka UGDD) ; Similar to Help DD and Comment DD but starting with the user guide.
- VDD
- Value Driven Design; Basically the same thing as Story Driven Design since you design for greatest value first. Either value for the end users or ROI.
- WDD
- Waterfall Driven Design; Doing everything the old water fall way.
- XDD
- eXtreme Driven Development; Being strict about applying all XP principles and guidelines.
- YDD
- Yes Driven Development; Just doing whatever you're told without objection even if the demands are ridiculous. Junior DD and Management DD often involved Yes DD.
- ZDD
- Zombie Driven Development; Another name for Yes DD.
If you feel something is missing, don't hesitate to contact me!
Comments
Anonymous
January 13, 2009
In Swedish there is a saying that translates to something like " a loved child is known by many namesAnonymous
March 04, 2009
Today I got a sweet reminder on developing with contracts when I read this (in Swedish). I always get