The place where stuff Happens

(DSDM) Dynamic Systems Design Methodology


DSDM is software methodology found in the Rapid Application Development (RAD) category. The goal of DSDM is to deliver the software system on time and on budget while changing requirements if needed along the development but without compromising quality.

Nine Principles

DSDM has nine principles that must be followed for a successful DSDM that are:

1.       Active user involvement.

2.       Empowered teams that the authority to can make decisions.

3.       A focus on frequent delivery of products.

4.       Using fitness for business purpose as the essential criterion for acceptance of deliverables.

5.       Iterative and incremental development to ensure convergence on an accurate business solution.

6.       Reversible changes during development.

7.       Requirements that are base lined at a high level.

8.       Integrated testing throughout the life cycle.

9.       Collaboration and cooperation between all stakeholders.

Overview: three phases of DSDM:

1.       Pre-Project Phase

At this phase project funding are released and commitment are ensured. This early for the project so its safe to ensure this stage is good and well done.

2.       Project Life Cycle Phase

In this phase there are 5 steps that must be followed to ensure a good DSDM

  • Feasibility Study
  • Business Study
  • Functional Model iteration
  • Design and Build iteration
  • Implementation

3.       Post-Project Phase.

In this phase the project is checked for errors and reliability and efficiently. Any malfunction or enhancements are added in this phrase trough maintenance.

Project Life Cycle Phase

1.       Stage 1A: The Feasibility Study

In this stage a report is issued with the requirement the new system needs to have, and why the system is needed at the first place. The current Deficiencies of the old system are examined at this stage. Cost benefits and limitation are reported at this stage two. And the recommendation is giving to user to which systems can be used. A Risk Log that identifies the most important risks for the project is created at this stage.

2.       Stage 1B: The Business Study

This extends the feasibility study because the new system is feasible for DSDM. At this stage planning is done so project can be done and Time Boxing technique is used. The Risk log is updated at this stage.

3.       Stage 2: Functional Model Iteration

At this stage, the previous stages are converted to a functional model and split in two a prototype and models. To ensure quality, test is implemented throughout every iteration of DSDM and can by divide in four stages:

·         Identify Functional Prototype

·         Agree Schedule

·         Create Functional Prototype

·         Review Prototype

A functional model and a prototype are realized to user to test. The Risk log is updated drastically at this stage because the prototype and model are similar to the last project.

4.       Stage 3: Design and Build Iteration

The scope of DSDM is to integrate a functioning model from the previous phase to one system that satisfies the user needs. This Design and build iteration consist of four stages

·         Identify the requirements of the module

·         Plan and commit to the requirement

·         Develop the module

·         Validate the functionality of the module                        

When the system is finally tested it is passed to the implementation stage. And the User Manual is done at this stage.

5.       Stage 4: Implementation

This is the final stage; at this stage the system is installed and ready for use.  User documentation is handled and training of future users is done. Implementation in splited in four parts:

·         User Approval and Guidelines

·         Train Users

·         Implement

·         Review Business

Roles of DSDM

1.       Executive Sponsor he/she gives the necessary funds for the system to be done

2.       Visionary he/she knows how the project is meant to be done; the visionary has the job to track the project work.

3.       Ambassador User gives all the users feedback to the project designers and developers

4.       Advisor User Gives the daily knowledge of the project

5.       Project Manager he/she manages the project in general

6.       Technical Coordinator: Design the system architecture and controls the technical quality of system

7.       Team Leader  leads the team and ensure the team work effetely

8.       Developer creates the system form the requirements that was given to him/her

9.       Tester test the system for any kind of errors and give them back to the developers

10.   Scribe Responsible to gather and record the requirements, agreements, and decisions (anything) made in every workshop.

11.   Facilitator ensures communications between each phase and stages.


blog comments powered by Disqus