Dynamic Systems Development Method

Words: 1562
Pages: 7

approach. Here each one of the iteration follows 80% rule in order to initiate the next iteration. The incremental prototyping allows parties to have a clear picture of the project throughout the software development life cycle. The best aspect of Dynamic Systems Development Method is that it provides an environment where all interested parties involved in a project can cooperate and collaborate for successful completion of the project [12]. The Dynamic Systems Development Method is a modified version of Pareto Principle. In Pareto Principle, 80% functionality of a project is delivered in 20% of the time in order to deliver a complete 100% of project. The remaining 20% of the functionality is deliberately left for later iterations. This strategy
RESULTS AND DISCUSSIONS The DXPRUM case study was carried out in a software house in Multan, a city in southern Punjab province of Pakistan. The name of software house was DreamSpark. The software house has a team of experienced members having ample knowledge of application development along with higher degrees in computer science. The employees were already using Agile in software development. Furthermore a one week in-house training program was conducted in order for team members to be aware of DXPRUM model thoroughly. An online shopping cart system was implemented using DXPRUM model. There were 4 team member and 2 other members were performing the role of DXPRUM Expert and Project Manager. The case study consists of 4 releases with an overall 1.5 months of duration. The team was balanced in all aspects of software development. The development team ensured that the development is going on in the right direction under the supervision of DXPRUM Expert and Project Manager and by using the guidelines of proposed DXPRUM model. The results obtained were quite good and are shown in Table 1. The DSDM case study was carried out in a British Telecom project and is written by “Ben Whittle” who was the project manager of the said project. It was further published in a book named “DSDM: Business Focused Development” written by “Jennifer Stapleton” [14]. British Telecom had already used DSDM in a number of their projects. Long working schedule is one of the major drawback of DSDM.
CONCLUSION DSDM is an already existing popular Agile methodology, while DXPRUM is a new methodology and is the combination of three Agile methodologies (DSDM, XP and Scrum). The DXPRUM needs some time to get mature. We have implemented DXPRUM model on a real time project and compared the obtained results with an already existing case study of a British Telecom project that used DSDM for development. The comparison are shown in the form of tables and figures. The results clearly showed that DXPRUM performed better and seems to be a more powerful model. By implementing DXPRUM we are able to deliver more high quality and cost effective software with minimum possible amount of time and low cost involved. The defect rate of those software are also low as compared to DSDM. This makes DXPRUM a more compact, concise and user friendly model and the one that need lots of attention in near