Development Methodolgies

When using open source systems, you can use thousands of features simply by turning them on. You don't have to create the code for the functions you need, just activate them; saving time and money. It's pretty cool stuff. But, the benefit in using open source systems can also be a big challenge when it comes to coordination different aspects of a project. Not everything exists in harmony- even when it is easy to turn on or off- and project planning/development methodologies can mean the difference between reaching your goal and just not.

Why we don't change feature's module file in code?

A good reason you don't change any features module by hand, so you don't loose your work.  Ex if you changed the file and pushed it to dev and someone else is working on this site with the UI a new featrue module will be created without your work.  A feature module not like a custom or a contrib module because if someone working on a contrib or custom module and change a file and someone has already change this file on dev and you are trying to push it, you will get a conflict with this file and you will know that.  With the feature modules if you change any file and some one is working o

Spiral Methodology

spiral methodology provides an iterative and progressive approach to defining the requirements and design of your site using prototyping. Once an operational prototype is reached, the development phase of production starts and you proceed using a waterfall approach. The spiral model suggests that a series of four steps be performed before coding begins. The following briefly describes the activities in each pass of the spiral, starting in the center of the spiral.

1. Determine your objectives, your alternatives for meeting your objectives, and any constraints that must be met.