DEV Community

Cover image for Dynamic Software Development Method (DSDM) in SDLC, DSDM Phases, DSDM Techniques.
AKTHER HAMID SAYMON
AKTHER HAMID SAYMON

Posted on

Dynamic Software Development Method (DSDM) in SDLC, DSDM Phases, DSDM Techniques.

What is the Dynamic Software Development Method(DSDM)?

DSDM is an approach to software development for Rapid Application Development (RAD) which offers an agile platform for project delivery. The key feature of DSDM is that users need to be actively involved, and the decision-making power is provided to the teams.

DSDM Phase-

Pre-Project Phase:
You make sure the projects are set up based on a specific target during the Pre-Project process. To begin the feasibility stage of the project, you must ensure that resources exist.

Feasibility Phase:
You want to make sure projects are technologically feasible and cost-effective during the feasibility process. You do only enough to decide whether the priorities of the company are appropriate for further preparation.

Foundations Phase:
The aim here is to get a picture of the project's scope of work and place the basis for identifying it and estimating the completion of items within the project, using range estimates if appropriate.

Random 3

Evolutionary Development Phase:
To control the iterations, Evolutionary Creation makes use of timeboxing, with each iteration releasing a completed piece of a much larger whole.

Deployment Phase:
In many cases, you can either deploy the entire solution, which might make sense, or with each loop, you can deploy small parts of the solution through an iteration of evolutionary growth.

Post-Project Phase:
Your project is complete and you reach the Post-Project Phase when all of your prototypes are complete and you have a solution or product completely created.

DSDM techniques-

Flexibility: The flexibility of the criteria to be achieved has a direct effect on the processes and controls of implementation and on system acceptance.
It assumes that 80% of the proposed system can be generated in 20% of the time it would take to create the entire system, which is useful and useful.

80:20 Model: A basic principle is that nothing is constructed completely for the first time, but that 80% of the proposed method can be generated in 20% of the time it would take to create the complete solution in a functional and useful way.

Time Boxing: In addition to the activities that lead to its execution, Timeboxing operates by focusing on when a business target will be reached.

MoSCoW Rules:
Must have – fundamental to project success.
Should have – important but the project does not rely on.
Could have – left out without impacting on project.
Want to have but Won't have this time for those valuable requirements that can wait till later development takes place.

Top comments (0)