Dynamic System Development Method - Term Paper Example

Dynamic System Development Method 16-Jan Introduction DSDM (dynamic system development method) is a system development approach that acts as a framework for developing and maintaining software. This software development approach is mostly implemented in time constrained environments where it involves the use of incremental prototyping in controlled project management (Stampleton, 2000). DSDM approach is tool independent therefore it can either use structured analysis approach or the object oriented approach. This approach is dynamic since it is considered to be a rapid application development method using incremental prototyping. DSDM is most suitable for systems that are being developed over a limited span of time (Stampleton, 2000). It is also preferable where the requirements cannot be halted at the beginning of the application development process. Using this approach the phases of development may not be clearly defined since the analysis, design and development stages may overlap. For instance, the software developers could be working on some requirements while developing some applications for the system. This approach also emphasizes on the involvement of the users on the system in its development (Futrell, 2006). This approach seeks to develop and deliver systems on time. This approach is also suitable for dynamic system requirements that are prone to change within the development process. The DSDM approach is made up of a 5 phase life cycle that includes feasibility study, business study, functional model iteration, design and building iteration and implementation (Katonya, 2007). I preferred to use the DSDM approach for the development of my work flow customer management system mainly due to the time constraints that I am facing. Given the limited amount that I have available to developing and delivering the system, this approach would be the most suitable. I also chose to use this approach due to its flexibility in system development. This makes the development of the online workflow customer management system easier since I have the choice of either using the structured or the object oriented approach (Katonya, 2007). In addition to the continuous user involvement in the development process, it will be easier to identify and correct errors in the system. It will also be easier to follow the user requirements due to user involvement in the system development. I also found this approach preferable due to its dynamism thus it will be easier to adjust to the user requirements that are prone to change from time to time (Puntambekar, 2008). With no formal specification requirements from computer fix company; their requirements could change at any point of the development process. With active user involvement in the development process I will have the mandate to assign them roles such as analysts to ensure accuracy. There are various benefits related to developing systems using DMDM approach as the framework for developing the proposed system. One of the benefits is that users are most likely to accept the ownership of the final system since they are actively involved in the development process (Stampleton, 2000). The involvement of the users also reduces the risks that could result to the development of the wrong system. As a result of the dynamism of this approach, one is able to suit to the changing requirements of the users thus it will improve usability by the customers and other users. This approach is also beneficial since it can be used with limited time schedules as the development phases can be easily interchanged (Stampleton, 2003). An extra plus of using this approach is the training of the users which decreases the chances for errors. This is very valuable to the business as it cuts on the costs related to training users on the system use. In addition, the implementation of the system is likely to be smooth as a result of the stakeholders’ support in the growth process. The company also benefits due to cooperation they easily achieve their goals and objectives. Using the approach, the testing process is integrated within the system development process thus it is simpler to make out and correct inaccuracies in the system (Futrell, 2006). The DSDM approach however has its disadvantages. One of the chief cons is that it could be costly to implements this approach since both the developers and users have to be equally trained to use the system effectively (Stampleton, 2000). This may therefore involve training costs. This approach could therefore not be suitable for small organizations in their startup projects. Due to time constraints related to rapid development, it might not be feasible to gratify all the user requirements. It is not possible to predetermine the budget for projects developed using this approach due to the dynamism of requirements. This therefore brings about other costs and resource requirements that were not initially intended for. The flow of activities in this approach is not clearly defined since some of the phases such as development and design tend to overlap each other (Highsmith, 2002). With no formal user requirements from the customers, it may be intricate for the developer to clearly plan their project (Highsmith, 2002). The active involvement of users and other stakeholders could also be a challenge to the developer as they may not be able to independently plan the project. This is as a result of the frequently changing user requirements. Differences in the stakeholders’ opinions could also lead to late delivery of the system. Using the DSDM approach to develop the online workflow customer system will play a vital role in the achievement of my objective which is to deliver a system that covers the requirements of all users (Stampleton, 2003). Due to its dynamism this approach will help me achieve the objective despite the limited span of time available. Additionally, considering the fact there was no formal user requirement from computer Fix Company, the dynamism of this approach will help me achieve my objective. The DSDM approach allows for iteration of the previous steps of development. The first step of system development using this approach is carrying out a feasibility study. The feasibility study will be done to identify the propensity of the system meeting the requirements of the user (Highsmith, 2002). It will also determine whether the DSDM approach will be suitable for development of the system. The feasibility study is then followed by a business study that is carried out to examine business processes, user groups and the respective requirements of each user group (Roebuck, 2011). The outcomes of this study are valuable in coming up with a summary of the system requirements. The outcome of this study is an account of the system structure in the perspective of the company. The next step is the functional model iteration where the identified user requirements are converted to a functional model. The functional model is made up of both the functioning models and prototypes (Highsmith, 2002). The developed prototype is assessed by the different user groups involved in the process. Testing is also implemented at this stage to ensure quality and accuracy. This phase is divided into 4 sub stages which include identification of the functional prototype, creating a suitable schedule for development, creating the functional prototype by combining it with other prototypes from previous iterations and reevaluating the prototype through testing to ensure correctness (Stampleton, 2000). The results of this stage are the functional model and prototype. The next step is the design and building iteration where functions from the previous phases are combined into one system to satisfy the user needs. This phase is divided into 4 different sub stages including identifying the functional requirements that are to be tested, agreeing on the appropriate schedule, creating the actual system that can be delivered to the user and reviewing the deign to check the correctness of the system. The deliverable for this phase is the design prototype that the end users test and hand it over for the implementation stage (Roebuck, 2011). Another result for this phase is the user documentation that helps the end user familiarize with using the final system. The figure below illustrates the DSDM approach frame work; This concluding phase is the execution of the system where the both the system and its documentation are delivered to the users. Implementation is divided into 4 other sub stages including user approval, user training, implementing and reviewing. The DSDM approach uses the time boxing technique where tasks are allocated a certain period of time in which they must be achieved. The end result of this technique is the final product. The tasks in the time box are also subject to change since the tasks are not defined. The tasks may change during time box iteration to allow rapid response to the changing user needs. The DSDM approach is therefore the most suitable approach for development of the online workflow customer management system due to conditions where time is limited and the business needs are prone to change. List of references Futrell, 2006, Requirements engineering: processes and techniques, Pearson Education, New Jersey. Highsmith, A, 2002, Agile Software Development Ecosystems, Addison-Wesley, Boston. Katonya, G, 2007, Requirements engineering: processes and techniques, J. Wiley, New York. Puntambekar, A, 2008, Software Engineering, Technical Publications, Maharashtra. Roebuck, K, 2011, Systems Development Life Cycle (SDLC): High-impact Strategies - What You Need to Know, Emereo Pty Limited, Brisbane. Stampleton, J, 2000, DSDM, Dynamic Systems Development Method: The Method in Practice, Cambridge University Press, Cambridge; UK. Stampleton, J, 2003, DSDM: Business Focused Development, Addison-Wesley, New York. Read More