Just About IT

Software Development Methodology

One part that is so critical in creating an information system is choosing the most appropriate methodology. It must be suitable to the project and so you'll be able to utilize them well. One common problem in selecting a methodology is that some end up selecting a model instead of a methodology.

Model Vs. Methodology

Generally, a model or a framework allows you to understand which project deliverable you should produce on a specific time.  It does not show off what you should do. On the other hand, a methodology as defined by the Treasury Enterprise Architecture Framework a methodology is a documented approach for performing activities in a coherent, consistent, accountable, and repeatable manner. It most likely serve as a  step by step guide for you, towards the end of your project development.

Software Development Methodology are like standards that we can employ to organize, plan, and manage the process of developing an Information System. There are different variety of methodologies available, each of these methodologies possesses its own strenghts and weaknesses. A methodology could be appropriate to a certain project and may not appropriate to another project. A specific methodology is best suited to specific kind of project.
Below are some of the commonly used methodologies that you may consider using on your project:

  • Agile Unified Process
  • Capability Maturity Model Integration
  • Crystal
  • Dynamic Systems Development Method
  • Enterprise Unified Process
  • Essential Unified Process
  • Evo
  • Extreme Programming
  • Feature Driven Development
  • Lean Software Development
  • Microsoft Solutions Framework
  • Open Unified Process
  • Prince2
  • Project Management Body of Knowledge
  • Rational Unified Process
  • Scrum
  • Unified Process
Filed under: Tutorials No Comments