Dynamic System Development Method

14,278 views
13,689 views

Published on

Dynamic System Development Method

Published in: Education, Technology, Business
1 Comment
3 Likes
Statistics
Notes
No Downloads
Views
Total views
14,278
On SlideShare
0
From Embeds
0
Number of Embeds
82
Actions
Shares
0
Downloads
497
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide

Dynamic System Development Method

  1. 2. <ul><li>-Is a software development methodology originally based upon the Rapid Application Development (RAD) methodology. </li></ul><ul><li>-Is an iterative and incremental approach that emphasis continuous user involvement. </li></ul><ul><li>- It seems ideally suited for software development that place a high importance on the user interface or usability aspects of products. </li></ul>
  2. 3. <ul><li>- Its goal is to deliver software systems on time and budget while adjusting for changing requirements along the development process. DSDM is one of the Agile Methods for developing software, and its forms a part of the Agile Alliance. </li></ul>
  3. 4. <ul><li>DSDM was developed in the United Kingdom in the 1990’s and was first released in 1995. </li></ul><ul><li>DSDM was developed by a consortium of vendors and expert in the field of Information System (IS) development the DSDM consortium, combining their best practice experiences. </li></ul>
  4. 5. <ul><li>The 9 PRINCIPLES </li></ul><ul><li>1. Active user involvement is imperative </li></ul><ul><li>2. Team must be empowered to make decisions </li></ul><ul><li>3. Focus is on frequent delivery </li></ul><ul><li>4. Fitness for business is criterion for acceptance of deliverables </li></ul>
  5. 6. <ul><li>PRINCIPLES </li></ul><ul><li>5. Iterative and incremental development </li></ul><ul><li>is mandatory </li></ul><ul><li>6. All changes during development must be reversible </li></ul><ul><li>7. Requirements are baselined at high-level </li></ul><ul><li>8. Testing is integrated throughout </li></ul><ul><li>the cycle </li></ul><ul><li>9. Collaborative and Co-operative approach </li></ul>
  6. 7. Fig. 1 The phases of DSDM Pre-Project Post-Project
  7. 8. <ul><li>Phases of DSDM </li></ul><ul><li>Pre-post-project </li></ul><ul><li>Includes project suggestion and selection of a proposed project candidate. </li></ul><ul><li>Feasibility study </li></ul><ul><li>Definition of the problem to be addressed, assessments of the likely cost and technical feasibility of delivering of a computer system to solve the business problem. </li></ul>
  8. 9. <ul><li>Phases of DSDM </li></ul><ul><li>• Business Study </li></ul><ul><li>This stage examines the influenced business processes, user groups involved and their respective needs and wishes. </li></ul><ul><li>• Functional Model Iteration (FMI) </li></ul><ul><li>The focus is on refining and studying the business-based aspects of the computer system. </li></ul>
  9. 10. <ul><li>Phases of DSDM </li></ul><ul><li>• Design and Build Iteration </li></ul><ul><li>The product is designed and developed in iterations. In each iteration a design model is made of the area being developed, and then that area is coded and reviewed. </li></ul>
  10. 11. <ul><li>Phases of DSDM </li></ul><ul><li>• Implementation </li></ul><ul><li>Product is wrapped up, documentation is written, and reviewed is drawn up, comparing the requirements with their fulfillments in the product. The users are trained in how to use the system, and the users give approval to the system. </li></ul>
  11. 12. <ul><li>Phases of DSDM </li></ul><ul><li>• Post-project </li></ul><ul><li>Post-project tasks include measurements on how the deployed system is performing and if any further enhancement are required. </li></ul>
  12. 13. <ul><li>Tools andTechniques </li></ul><ul><li>• Time-boxing </li></ul><ul><li>• MoScoW Rules </li></ul><ul><li>• Prototyping </li></ul><ul><li>• Testing </li></ul><ul><li>• Workshop </li></ul><ul><li>• Modeling </li></ul><ul><li>• Configaration Management </li></ul>
  13. 14. <ul><li>Conclusion: </li></ul><ul><li>DSDM is a useful approach that helps to develop a robust system. The methodology helps keep a project from failing and also helps in developing requirements-satisfied systems. DSDM implementation aims at on-time delivery and within budget. If proper analysis is performed, the DSDM approach can yield superior results (Gorakavi, P.K.). </li></ul>
  14. 15. <ul><li>Conclusion: </li></ul><ul><li>The DSDM framework is a straight forward framework based on best practices to start implementing a project structure, its strengths being simplicity, extendibility, proven in the past but not claiming to be the solution to all kind of projects. (Voigt, B.J.J.). </li></ul>
  15. 16. <ul><li>Conclusion: </li></ul><ul><li>The weakness of DSDM is, like with many other structured approaches, the relatively high barrier to entry (apart from the licensing costs). Switching to DSDM is neither cheap nor fast, and requires a significant cultural shift in any organization, because suddenly deliverables are replaced with tasks (Voigt, B.J.J.). </li></ul>

×