"Phishing Maturity Model" for Software Testing"

 

In the STP magazine of April 2010, Matt heusser and chris mcmahon proposed the "phishing Maturity Model" for software testing following the CMM model. They used the phishing metaphor for software testing:

 

1 chaotic (chaotic phase ).

Fishing is a seat-of-the-pants, ad hoc, made-up-as-we-go, improvised process.

Random Process. Sometimes you can catch big fish, sometimes you can't catch them.

 

2 planned (planned ).

The location and timing of your daily fishing partition ditions is scheduled. with knowledge of how you did for the past two weeks, knowing you will go to the same places, you can predict the size of your catch.

The positions and timing are all planned. Repeat previous practices to find a certain number of bugs.

 

3 managed (managed ).

By taking your fishing process and standardizing processes for how fast to drive the boat, how deep and how quickly to let out the nets and so on, you can improve your estimates over time.

Test process standardization. Go fishing according to certain programs!

 

4. measured (measured ).

You track your results over time, to determine exactly how many pounds of fish are delivered at what time with what processes.

Trace and measure the test process. The quantity, quality, and efficiency of phishing scams must be tracked and measured.

 

5 optimizing (optimization level ).

Now, you experiment with different techniques to see which technique yields more fish and which does not. This is continuous improvement.

Introduce different testing technologies and processes to continuously improve the testing process.