PROCESS MODEL

Process Model Critical Discussion and Proposal

Process Model Critical Discussion and Proposal

Part A: Process Model Critical Discussion

Dynamic Systems Development Methodology (DSDM)

Dynamic systems development method (Dynamic Systems Development Method, DSDM) - it's mostly software development methodology based on the concept of rapid application development (Rapid Application Development, RAD). In 2007, DSDM has become the main approach to project management and application development. DSDM - an iterative and incremental approach that emphasizes the period of participation in the process of the user / consumer. The DSDM arises as a consequence of failures of software development and information systems, aims to promote rapid application development. In addition to the DSDM has been formed to combat the growing dissatisfaction over the traditional methods of application development. In a business environment where opportunities are reduced, rapid application development appears as an essential factor of competitiveness. Therefore, DSDM says it has been created to reduce the time spent in development, reduce costs and improve quality. The previous version of DSDM (released in May 2003), which is still valid and widely used - is DSDM 4.2, which is slightly expanded version of DSDM 4. The extended version contains guidance on how to use DSDM with Extreme Programming (Extreme Programming).

Comparison of DSDM to Spiral Model

The spiral model is a process model in software development , which in the year 1986 by Barry W. Boehm is described. It is a generic process model and therefore open to existing process models. The management can intervene again and again, as you progress in a spiral develops.

Strengths

Early customer involvement

Critical and high-risk features are implemented at the beginning

It is already evident in the first few cycles, if a project is feasible

Sets value to the development and less on a perfect design

Improved management control over quality, costs, resources and schedule

Performance improvements or risk reduction can also be the target of a cycle

Works on complex or uncertain requirements

Weaknesses

Not suitable for small projects or projects with manageable risk

Risk management skills are required

Due to ever more demands we never comes to an end

Due to the high cost addition, such projects can quickly become expensive

Developers are only required for certain stages in between and must be otherwise occupied

Is often perceived as too complex

The purpose of the method of \DSDM is to take the project on time and ready to meet your budget, but at the same time adjusting to the project requirements change during their development. DSDM is a family of Agile software development, as well as the development is not within the sphere of information technologies. As part of the adoption and implementation of a DSDM methodology, missteps should be avoided. These pitfalls don't represent a death sentence for an agile data warehouse project; instead, if a data warehouse team accepts them as necessary evils, it accepts that the risks of failure are increased. Given that one of the key benefits of adopting an agile methodology is to reduce risk, each item gradually offsets the long-term benefits of agile and could undermine its effectiveness to the overall delivery ...