DSDM: t Rapid Application Development methodology .Rapid Application

DSDM:
Dynamic System
Development Method

DSDM was originally developed in late 1994 to
improve the t
Rapid Application Development methodology .Rapid Application
Development methodology is process based and traditional approach to complete
any task .DSDM is based on some agile methodology in which agile roles and
principle are used to complete any task. It is not exactly same as agile but it
is not as much preferred as agile methodology. The name suggests dynamic means
it welcomes changing requirements rather than like waterfall model where requirements
are not changed after initializing task.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

·       
DSDM approach is based on pre –development and post development
process rather the focus on only one process.

·       
Due to this it become little complex but also better than water
fall and iterative model.

·       
It is straight forward based on principle to start implementing
a project structure.

·       
It is extendable approach.

·       
Remove bureaucracy and also eliminates the communication barrier
between middle parties.

·       
Ability of users to affect the project directions.

 

 

Principles of DSDM

There are
eight principles underpinning DSDM. These principles direct the team in the
attitude they must take and the mindset they must adopt in order to deliver
consistently.

1.   Primary
concern  on the business need

2.   Deliver
product on given time

3.   Collaborate
cooperative

4.   First
priority is given to quantity

5.   Build
incrementally from firm foundations

6.   Develop
iteratively

7.   Communicate
continuously and clearly

8.   Demonstrate
control

 

Life cycle of DSDM:

 

The Pre-Project: In which business problem are identify and plan
requirements and focus on analysis .So that the task is based on proper requirements

The Project life-cycle: it describes the five different
stages of project development. Initial two stages are feasibility study and
business study are the sequential .after completion of these stages the system
is generated iteratively and incrementally in next functional model iteration,
then design and implantation is done.

v
Feasibility Study

v
Business Study

v
Functional Model Iteration

v
Design and Build Iteration

v  Implementation

 Post project: In post project
phase, it is validated by the technical teams and the business-operations teams
that the system operates as per the business expectations. Post project phase
also comprises of maintenance and fixes phase. In these phases the project is
improvised incrementally and thus continuous product development is achieved.

Core Techniques of DSDM:

v Time boxing: Time boxing is interval to complete any task. In which
different tasks can be accomplished and deliver on time.

 

v Moscow:

   Moscow rules are:

·       
Must:
requirements must be satisfied for the success of product.

·       
 Should: it is based on high priority time and
solution should be added of any problem.

·       
Could: requirements
are considered not desirable.

·       
Want: in
which needs or requirements are   changed in coming days                                

 

v Prototyping: Prototypes are to implement critical
functionality fist to discover difficulties early in the development process, they
also allow having very early deliverables to get user feedback

v
Testing:
testing is just like testing of system in which all the modules are tested and
then passed to Workshop.

v
Workshop:
In which again discuss the project requirements and discussion of anything
changed and required.

v
Modeling: helps visualize a business domain and improve understanding.
Produces a diagrammatic representation of specific aspects of the system or
business area that is being developed.

v Configuration management: it
is configuration of system. system is developed on time and frequent delivery  of system

 

 

Scrum: scrum is part
of agile. It is lightweight approach but hard to master. IN which complex
problems can be defined it is framework where complex problems and design are
generated and adapt the requirements .It
is an iterative and incremental agile software method.

Scrum  is a straight  framework for effective team collaboration on
complex products.  Scrum co-creators Ken Schwaber and Jeff Sutherland have
written The
Scrum Guide to explain Scrum clearly .
 This Guide contains the definition of Scrum. This definition consists of
Scrum’s roles, events, artifacts, and the rules that bind them together. 

Scrum is based on events:

·       
Sprint

·       
Sprint planning

·       
Daily scrum

·       
Sprint review

·       
Sprint retrospective

·        
Product
Owner: A person that
define requirements to engineer and try to clear what he want .actually The Product
Owner have right to change requirements if he is not satisfied with the
product. product owner is also major part of scrum..

·        
Scrum
Master: scrum master is
like servant leader. Scrum master   give focus to eliminate problems and motivate
the development team to accomplish task more effectively and achieved goal as
soon as possible.

·        
Team:  development team is  responsible to complete the task within time
and fully covered requirements that satisfied product owners need it is team of
about 3 to 9 members that are master in their work and work on the same environment.

                          DSDM

                   SCRUM

·       
In DSDM,
development work is termed the ‘engineering activity’ and the output of each
iteration is called the ’emerging solution.
·       
The DSDM guidance does advise that any ‘definition
of done’ work upfront during the Foundations phase should be reviewed
regularly throughout the project lifecycle.
·       
DSDM
originally sought to provide some application to the rapid application
development method.
·       
Simple
and extendable
·       
Project
based
·       
Robust
scalable ,governable agile
 

·       
In Scrum
the output is termed a ‘potentially releasable increment.
 
 
·       
In Scrum an increment is described as “Done” when
it meets a “Definition of Done” for the Scrum Team. 
 
·       
It is an iterative software development model used to manage complex
software and product development.
 
·       
Difficult
to master
·       
Team
focused
·       
Light
empirical agile