subject: A Study On Various Software Development Methodologies [print this page] Software development methodology: An intro
Software development methodology can be described as a framework for the planning, construction and management of the development of an information system. Here, we will discuss various methodologies that can be used for this task.
Agile software development methodology:
This particular methodology was introduced as a concept-based framework to handle all kinds of software development projects. This methodology is further spread out into several methodologies, such as Crystal Method, Dynamic Systems Development Model (DSDM) and Scrum.
A noteworthy characteristic of almost all Agile software development services are restricting projects to short timeframes (iterations) in order to cut down possible risks to the lowest level, each of which in turn was a mini project on its own containing all the components of an actual project.
Crystal Method:
The Crystal Methodology was created by Alistair Cockburn, who had his sights on factors like the staff, communication, community, skills and talent. He believed that these factors were the driving force for optimal performance, while process takes up a later spot in the importance graph. According to him, every member involved in this methodology has his own unique skills, which can be used for a task thats suitable for his skills.
Dynamic Systems Development Model (DSDM):
Developed in the UK in the mid 90s, the Dynamic Systems Development Model (DSDM) is basically an advanced version of the rapid application development (RAD) practices. Among all the Agile Software Development methodologies, DSDM apparently has the best training and documentation abilities, especially in Europe. DSDM follows nine principles in its approach. These principles are:
Livelier user activity
Monitoring product delivery activities
Granting more authority to teams for easy decision making
Step by step and part by part development to meet at a single point of business solution
Incorporation of a testing feature for as long as the project goes on
Considering preparedness for business goal as the basis for taking up the responsibility of deliverables
Facilitation of reversibility of changes made during the project
Maintaining requirements at the highest importance level
Participation and support among all the stakeholders involved
Scrum Methodology:
The Scrum methodology in software development was created by Ken Schwaber for the purpose of enhancement in the productivity of the teams, who had earlier suffered under the implementation of complex and process-oriented methodologies. This methodology facilitates the establishment of self-organizing teams through the initiation of personal interaction between each throughout all the departments involved. So, the approach of this methodology is typically empirical in nature and concentrates on boosting the abilities of the teams in meeting challenges and performing better.
