Download Comparison and Key Features of RAD and DSDM and more Exercises Network security in PDF only on Docsity!
Describe about given software development model
RAD (Rapid application development)
RAD model is Rapid Application Development model. It is a type of incremental model. In RAD model the components or functions are developed in parallel as if they were mini projects. The developments are time boxed, delivered and then assembled into a working prototype. This can quickly give the customer something to see and use and to provide feedback regarding the delivery and their requirements. Diagram of RAD Model The phases in the rapid application development (RAD) model are: Business modeling: The information flow is identified between various business functions. Data modeling: Information gathered from business modeling is used to define data objects that are needed for the business. Process modeling: Data objects defined in data modeling are converted to achieve the business information flow to achieve some specific business objective. Description are identified and created for CRUD of data objects. Application generation: Automated tools are used to convert process models into code and the actual system. Testing and turnover: Test new components and all the interfaces.
Advantages of the RAD model: Reduced development time. Increases reusability of components Quick initial reviews occur Encourages customer feedback Integration from very beginning solves a lot of integration issues. Disadvantages of RAD model: Depends on strong team and individual performances for identifying business requirements. Only system that can be modularized can be built using RAD Requires highly skilled developers/designers. High dependency on modeling skills Inapplicable to cheaper projects as cost of modeling and automated code generation is very high. When to use RAD model: RAD should be used when there is a need to create a system that can be modularized in 2-3 months of time. It should be used if there’s high availability of designers for modeling and the budget is high enough to afford their cost along with the cost of automated code generating tools. RAD SDLC model should be chosen only if resources with high business knowledge are available and there is a need to produce the system in a short span of time (2-3 months).
DSDM is vendor-independent, covers the entire lifecycle of a project and provides best practice guidance for on-time, in-budget delivery of projects, with proven scalability to address projects of all sizes and for any business sector. DSDM advocates the use of several proven practices, including: Timeboxing : DSDM adheres to strict deadline standards. To do so, one must break down the whole of the project into smaller items that each have a firm budget and timeframe. To navigate this, requirements are prioritized. If time or money is running out, lowest priority requirements are removed. A finished project then comes from only the most essential requirement items. MoSCoW : This is the prioritization groups used to rank items from highest level of importance to the lowest. The priorizations groups are Must Have, Should Have, Could Have, and Won’t Have. Configuration management helps to navigate all of these competing deliverables, often being developed at the same time. Modelling and Iterative Development : Modelling helps to visualize different aspects of the project along the way. This helps to present each item in development and allow for iterative development by providing regular feedback and implementing improvement. Prototyping : Like many agile methodologies, prototyping is essential to test run the project at an early, conceptual stage. It is a way to map out the basic functions, discover glaring weaknesses, and allow users to test run the software.
Workshops : Users and stakeholders are brought together to discuss requirements, issues, results, and testing. DSDM relies on high levels of user interaction, right from the get-go. Testing is hugely important for DSDM, as it ensures high quality results. Advantages of dynamic systems development method Projects are delivered on time, whilst still allowing flexibility Progress can be easily understood across the organization Business cases are at the core of the DSDM model, ensuring delivered projects have real business value Disadvantages of the dynamic systems development method Large management overhead and costly implementation makes this unsuitable for small organizations DSDM can be restrictive and inhibit developer creativity. Projects are likely to be completed exactly as specified, even if more elegant solutions are available.
