The Dynamic Systems Development Model

Dynamic Systems Development Model

Posted on Posted in IT Strategy

In mid-1990’s U.K. developed The Dynamic Systems Development Model as rapid application development (RAD) practices evolvedThe Dynamic Systems Development Model stresses on continuous user involvement in an iterative development and incremental approach,

Compared to SSADM, The Dynamic Systems Development Model is a culture change.

User stories instead of requirements are used to work out tough technical problems.

Despite the requirements changes, time for the life of project and resources are fixed. Therefore,the development of software system satisfies the business requirements on time and on the budget. D.J & I.J. Tudor (2002) assert that DSDM carries out the concept of 80/20 rules and follow the fundamental assumption of “Nothing is built perfectly the first time”.

The Dynamic Systems Development Model

consists of five phases:

  1. feasibility study
  2. business study
  3. functional model iteration
  4. system design and build iteration
  5. implementation

DSDM projects are limited by time and resources . To meet business needs,Dynamic Systems Development Model consists of nine principles:

  1. Active user involvement is imperative.
  2.  Empowered DSDM teams to make decisions.
  3. The focus is on frequent delivery of products.
  4. Fitness for business purpose is the essential criterion for acceptance of deliverables.
  5. Iterative incremental development is necessary to converge on a right business solution.
  6. All changes during development are reversible.
  7. Requirements are baselined at a high level.
  8.  Integrated Testing throughout the lifecycle.
  9. A collaborative and cooperative approach between all stakeholders are essential.

Ignoring one of The nine principles break with the frameworks philosophy and significantly increase project risks D.J & I.J. Tudor, (2002).  Many of the 9 principles are encompassed in the following characteristics :

  • Deliver quickly and often (timeboxing)
  • Joint Application Development workshops
  • Prototyping/tools
  • Timeboxing
  • Pareto Principle
  • MoSCow rule
  • Extreme Programming

Leave a Reply

Your email address will not be published. Required fields are marked *