Software Development Methodology [closed]

开发者_运维知识库Closed. This question is off-topic. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Stack Overflow.

Closed 10 years ago.

Improve this question

I'd like to know the difference between Software Development Process and Software Development Methodology if there is any.

---

A process is only a component of a methodology. A methodology has:

• A process aspect: what tasks are to be carried out?
• A product aspect: what things are to be used and/or created?
• A people aspect: what people and teams are going to do all this?
• A time aspect: how does all this get organised in time?
• A modelling aspect: what modelling units (language) are used to capture all this?

This is a simplified interpretation of the more formal definitions that you can find in ISO/IEC 24744 Software Engineering - Metamodel for Development Methodologies.

Still, the terms "method", "methodology" and "process" are used by different people with different meanings. After 20 years working in this field, I think that trying to agree on a standard use is futile. :-)

---

It's the same as the difference between process and methodology in any other discipline. I think of the processes as the implementation of the methodology.

---

The methodology is more a general mindset which sets basic parameters. A process is a concrete manifestation within the given borders of the methodology. You can think of agile as methodology and Scrum as concrete implementation.

Sometimes it's hard to distinguish between the two. As rule of thumb: If you can immediately start to work with it, it's probably a process. A methodology requires more adaptation .

---

A more wide term would be Software Development Philosophies. http://en.wikipedia.org/wiki/List_of_software_development_philosophies