We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now


what is the differences between approach and methodology

Medium Priority
Last Modified: 2013-12-13
i want the answer to that question with Example, let say for I.T testing

what is the differences between approach and methodology?
Watch Question

Unlock this solution with a free trial preview.
(No credit card required)
Get Preview


thanks chilternPC,
i agree with u, this is almost the right thing to say about the two definition. so when we say waterfall, do we use methodology or we can say approach, so which one is correct:
1- waterfall model
2-waterfall approach
3-waterfall methodology
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Sorry  I missed the part with a testing example.

Okay, so a testing methodology may state that projects, in general, do functional, regression, performance, and acceptance testing during the system-level testing phase.  The methodology explains the work products needed for each of these types of testing, and what roles perform them, and what those specific responsibilities are.  For example, regression testing may need to have the test lead create a change matrix tied to test cases so that regression coverage may be reviewed by the team.

Now, a testing approach (or sometimes called a test strategy) for a particular project may specify that performance testing is not required - maybe it is too impractical to replicate the production environment.  These decisions about what in the methodology will be followed and what will not need to be specifically documented with an acceptable rationale.

Ok, I also give you some light on your second question. As far as I see, the first question already answered.

Some refer water fall as approach while other refer as a methodology.

To me, actually waterfall is a model.
Water fall approach or water fall methodology is the process involved in creation of software. This process will be approach or methodology depends on how you deal during the waterfall model.

Ie: the "processes" that you are navigating through Conception, Initiation, Analysis, Design (validation), Construction, Testing to maintenance will be simply an approach or methodology.

Water fall, by the name itself you see once you've completed a phase, its results are frozen and until the results of the current phase are complete you cant start on any work that belongs to the next or later phase. This is the basic idea behind the waterfall model (though it has many variations)

Having said that you may see, that in order to follow the water flow model that you need to treat it as a methodology than approach, which may rephrase as waterfall methodology.

Hope this helps.

its a shame that people can spend a lot of time (and resource)  worrying over terms such as methodlogy vs approach vs model vs process.  
one mans process is another mans methodology.  for the QA people out there they should be happy if the approach/model/process can be measured. (therefore can be improved).

I like the term 'Process' myself, I think 'model' and 'methodology' terms are really  abstract or theoretical set of concepts that have to be tailored to a particular problem and turned into real steps (i.e. like the earlier comment of 'class' and 'instance of a class' ) and has to be turned into a process  to be of any use.


I am in QA by profession, and I know that value in understanding terminology.  QA isn't just about measurement.  And you can't reliably measure what you haven't defined.

For example, I was refining a one-page diagram/clarification of root cause, mistake, fault, failure, error, and defect just last week.

Why does it matter?  Well even if you go back to measurement, if I need to calculate a defect metric, what is a defect?  The answer is not as obvious as it seems, and without it the numbers have no integrity...

Well ,  as a QA professional, I also agreed with cdbosh. But really we don't want to make any argument here for model/process/approach/methodology.

These words has unique meaning and value when it comes to the software development (especially in QA)
And i agree with what chilternPC has mentioned, people may see a single thing in different  views depends on their own angle, but it doesn't make any difference to the meaning / value of these terms.

The most important thing to me is having a clear idea about these terms while on working :)
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.