Dynamic system development method

Introduction

This report will be discussing about the development method to the new claims payment system. Through the researched, Dynamic System Development method (DSDM) that one type of the Agile method is more suitable used to guide the development team in the development process. This report will covered about the problem of the previous project, the suitability using the dynamic system development method in the project, explanation of the dynamic system development method, the nice principle of dynamic system development method, the process structure about the dynamic system development method, the benefit will carry into the project, and the possible problem will happen during the development process.

Problem of the previous project

According the case study, the previous project contains a lot of the problem. The problem can separate into three sections, such as the technology's problem, user's problem and the system owner's problem. Uncertainly has been hidden in the older system and no obviously to find out by the programmer. The older database structured design might not suitable for the current new system. The older user interface design and the usage of the system already out to date that the new technology already changed. The complex of data in the database might not suitable for the new database design. According the experience, most of the end user might very blur about their requirement of the new system. Thiers might request the higher requirement that over the current technology. The issues of the users might make the user always changed the requirement. Users will provide different of the request or information during each time of the interview. The user might cant has an abstract the overall of the system. Last, the problem faced by the manager or the system owner. The company was overpaying claims at a rate of up to $5,000 per day. In the same time, the older project are longer been used and containing the problem.

Suitability using Dynamic System Development Method (DSDM)

For the older system already been used in long time ago, and the company was overpaying claims at a rate of up to $5,000 per day. The project team should develop the project in shorter times and fulfil the latest users' requirement. The reason DSDM will be selected such as an approach method that DSDM quickly and efficiently complete the project (Clifton, 2003). Combination a number of staff with experience in JAVA and GUI tools is the key of used the DSDM. Others, activeness users involve in the project that provided the useful information. The system clearly defined user group. To increase the confident between the business managers, the project should clearly demonstrable that the user interface. This project considers is a complex system and allow to split small task. Time will be one of the constraint that the system already overpaying. The project requirement might be frequent change. Some category of users might is a non - IT technical workers, their might blur for the previous request of the system. To achieve the higher fulfil for that system, the project team should fully specified and understanding the overall project flow before any code can be written.

Dynamic System Development Method (DSDM)

Dynamic System Development Method (DSDM) is a software development methodology that project time is fixed but the functionality is still variable (Clifton, 2003). The functionality is variable means the system requirement might be change before or during the development start. To use the DSDM, project might complete in quickly and efficiently (Clifton, 2003). DSDM more focused on the project requirement, rather than just a team activity (Clifton, 2003). DSDM addresses the common problem during develop the project, such as budget constraint, out of deadlines, lack of user involvement and top management commitment. The key assumption of the DSDM are nothing is perfect for the first time, but 80% of the expected functionality in 20% of the time it would take to produce the total solution(Shirmohammadi , No Date). The overall of the DSDM is combination of the user's knowledge with the technical skill of IT (Shirmohammadi, No Date).

Nine Principle of Dynamic System Development Method (DSDM)

The first principle of the DSDM is the active user involvement. The users whose was using the system should active involve in its development that provided the useful and accurate requirement of the system. The users and the developer should share a same workplace, so that the decisions can be agreed and made accurately (Clifton, 2003; HighSmith).The second principle of the DSDM is the team must be empowered to make the decision making. Without waiting the higher level approval, the team able to make the complex and informed decisions (Clifton, 2003; Norfolk). The senior management commitment is the make issues to make this success. Third of the principle is the frequent releases. This principle is to frequent focus of the press conference. Frequently published in the product allows the user to enter a critical stage of development. The project ensures that the products can be release at any time (Clifton, 2003; HighSmith). The purpose of delivery product in the early stage is let users can be tested and reviewed. The tested record will be used in the next phase. Forth of the principle is fitness for business purpose. This principle is to acceptance the basic standard of the requirement. Fifth of the principle is the development for the system mush done in iterations, which allows the user frequent feedback that extra functional will be added in later iteration (Clifton, 2003). The sixth of the DSDM principle is all the changes of the system must be reversible. The all process of the project should able to roll back or restore to the stage which is no work very well (Clifton, 2003; Zrich, 2004). Seventh of the DSDM principle is to adjust the high level requirements or task should be based lined before the project start (Clifton, 2003). Eighth of the principle is that the testing is through the life cycle integration (Clifton, 2003; Zrich, 2004). The last DSDM principle is that communication and cooperation for all stakeholders are required.

Structured Process of Dynamic System Development Method (DSDM)

The project life-cycle can separate into four phases. First phase of the project life-cycle can separate into two sections which is feasibility study and the business study. In the feasibility section, the team should address the suitability to use the DSDM in the project understanding the project requirement and the risk (Clifton, 2003). Business study is to determine which of the stakeholders will be involved and the priority of the project task. The section of business study always updated the risk log with the facts that have been happen or identified during the phase of DSDM (Clifton, 2003). Except the first phase, the three remainder phases are work such as a circle. Each of the circles will contain four tasks. The three circles might overlap each other during the development process. The second phase of the project life circle is functional model iteration. The purpose of this phase is to determine the functional prototype of the system between the program and different users group. The first task of the functional model iteration is to identify the functional (Clifton, 2003). This task is to determine the functionalities in the project. The second task of the functional model iteration is to agree the plan. It was agree on when and how to develop the functionalities. Third task is created the functional prototype. This task is to develop the prototype and might have a combination with previous iteration. And the last task of the functional model iteration is to review the prototype. This testing might completely by the end users. It was check the correctness of the developed prototype. Through the demonstrate prototype to the users, the team taking the feedback and incorporating the changes (Clifton, 2003). The third phase of the DSDM project life circle is design and builds iteration. This phase of product will be designed and developed. The non- functional requirement will be addressed (Clifton, 2003).The first task is to identify the design prototype. It was address the functional and the non-functional requirement will be needed to test in the system. The following task is the agree schedule that agree on how and when to realize the requirement that have been identified. The third task is to create the design prototype. The last task of the design and builds iteration is let the users check and review the correctness of the design system. Again, this phases will taking the feedback from the users. The last phase is to implementation. First task of the implementation is to getting the end users approve to the tested system and guideline that create the system. The system will be created. The following task is to train the users to use the system. The system will implement at the location of the end users. The last task of the implementation is to review the business rules (Clifton, 2003).

Benefit applying Dynamic System Development Method (DSDM)

Many business problems might be implementation in the early stage. It is because each task of the development process, the team getting feedback from the end users. The end users be the tester and check the correctness of the system. The users user involve into the project that become the partner of the team member. The final version of the system would not let the user feel stranger, it is because the system are combination from the small process that agreed by the end users. The user will be more easily accept the system. In the same time, the risk that the project will out of the scope or objective is reduced. The system is likely meet the user's real business requirement (Brannstrom, 2006). The users will be easy being train, since the system is request and review by the end-users between the development processes. The implementation of the system might works smoothly, it is because the co-operation of all member and the users are involved and provided the useful information (Brannstrom, 2006). Team member will have an empowerment to making the decision that to development the project.

Possible Problem

The possible problem might occur during the project are lack of the active user involve. Some of the users might get the time planning problem. It is difficult to meet and work together with the users. This has meant that the issues of prioritisation are very important. The users needed to re-adjust their priority of the work that depend what the project need (Brannstrom, 2006). The team might making the wrong decision but in the most case is better that no decision at all (Brannstrom, 2006). The business requirement might easily be out of the scope, it is because the end users do not reviewed of each process. If the project control by the time and resource, it might be the one of the problem that applies DSDM. It is because the traditional method to control project is a reversed requirement DSDM. For the traditional development methodology, functionalities are fixed, but the time and the resource is a variable. In DSDM, the project of the functionalities is a variable, time and resource is fixed (Clifton, 2003). The speed to development the overall project might be delay once spend too much time on the decision making for every single process. The project might out of the deadline of the project. The developer might develop some of the task that irreversible during the design or the ideas are not work very well. If might been increase the team job to find other way to solve the problem. The worst case the project has been restarted. In the same time, the time usage will be increase. The project might be slow down if the team are focus on activity rather than delivery of products. Some of the development process might be skipped the testing phase that no integrated throughout the project circle. During the development process, some of the users might allocated to the project are not interesting or "not wanted". The users might becoming the deactivate member and might do not touch with their job. The complex prototyping of the system might occur that the development process hard moving to the next phase.

Conclusion

The key success for the project is needed the cooperation between the user and the team member. The users have to review that check the correctness each process are working correctly. So that the project would not out of scope or no fulfil the project requirement. The users are more likely to accept the overall system design and the functionalities provided. Compare with the Extreme programming (XP), DSDM can completely the project in the shorter time that included all the functionality are fulfilment. The most important to avoid the problem, the nine principles is the main key to success the project. Without the nine principles, the DSDM are would not work well or project will become failed.

Please be aware that the free essay that you were just reading was not written by us. This essay, and all of the others available to view on the website, were provided to us by students in exchange for services that we offer. This relationship helps our students to get an even better deal while also contributing to the biggest free essay resource in the UK!