Examples Of Software Development Methodology

1220 Words5 Pages

A software development methodology or system development methodology in software engineering is a framework that is used to structure, plan, and control the process of developing an information system.
There are the following methodologies:
• Agile Software Development
• Crystal Methods
• Dynamic Systems Development Model (DSDM)
• Extreme Programming (XP)
• Feature Driven Development (FDD)
• Joint Application Development (JAD)
• Lean Development (LD)
• Rapid Application Development (RAD)
• Rational Unified Process (RUP)
• Scrum
• Spiral
Systems Development Life Cycle (SDLC)
• Waterfall (a.k.a. Traditional) Agile Software Development Methodology
Agile software development is a conceptual framework for undertaking software engineering …show more content…

And it means that the process should be minimized - barely significant. The use of the word “crystal” refers to the various facets of a gemstone - each a different face on an underlying core. The underlying core represents values and principles, while each facet represents a specific set of elements such as techniques, roles, tools, and standards. Cockburn also differentiates between methodology, techniques, and policies. A methodology is a set of elements (practices, tools); techniques are skill areas such as developing use cases; and policies dictate organizational “musts”. Dynamic Systems Development Model Methodology
The Dynamic Systems Development Model was developed in the U.K. in the mid-1990s. It is the evolution of rapid application development (RAD) practices. DSDM boasts the best-supported training and documentation of any of the agile software development techniques, at least in Europe. DSDM favors the philosophy that nothing is built perfectly the first time and looks to software development as an exploratory endeavor. The nine principles of DSDM are:
• Active user …show more content…

However, XP has been used successfully on teams of over a hundred developers. Feature Driven Development Methodology More specifically, Feature Driven Development asserts that:
• A system for building systems is necessary in order to scale to larger projects.
• A simple, but well-define process will work best.
• Process steps should be logical and their worth immediately obvious to each team member.
• “Process pride” can keep the real work from happening.
• Good processes move to the background so team members can focus on results.
• Short, iterative, feature-driven life cycles are best. FDD proceeds to address the items above with this simple process (numbers in brackets indicate the project time spent): 1. Develop an overall model (10 percent initial, 4 percent ongoing)
2. Build a features list (4 percent initial, 1 percent ongoing)
3. Plan by feature (2 percent initial, 2 percent ongoing)
4. Design by feature
5. Build by feature (77 percent for design and build

Open Document