The VCAA PSM is just another example of a problem solving methodology (PSM) that has been created, and it has a fairly easy to understand layout, with four stages each taking one step closer to a final product.
1. Analysis
This stage, being the first stage, is all about taking scope of the situation and figuring out what the end goal is. It has three key parts; identifying solution requirements, establishing solution constraints and defining the scope of the solution. At the end of this stage, the user should know what the goal is and what can and can't be done to get there
2. Design
The design stage has two parts; the solution design and the evaluation criteria. The first is about creating a blueprint for what the final result should look like. It should show what the solution should look like, and and how the data and information elements should be created or structured. The second stage is to create a set of guidelines for the last stage so that everyone involved in the creation of the work or solution knows what level of work needs to be achieved.
3. Development
This stage is the 'creation' stage. Here the developers take the design and creates and tests (validates) the work. The four parts of development are, manipulation, validation, testing and documentation. The first stages create the work and test it whilst the final stage involves recording what happened so any errors found in the last stage could be found more easily.
4. Evaluation
The final stage has only two important steps; creating an evaluation 'strategy' and reporting on the success of the result. The aim of the final stage is to check whether the result is a success or if it failed to achieve the result.
If that was to badly explained to follow, there is a helpful PDF here, (I didn't make it)
Personally, I believe that, compared to other methodologies (such as the 8D and GROW methods, found here on wikipedia) this study method is not as accurate as the others are. Even the GROW method, which is a much more simple form of this method, provides better planning and would result in a smoother production or work 'phase'. This method may be better suited to working out a maths problem or solving an error in a bunch of code, but I think that, as it has more applications, simple methods like this are superior to the detailed methods such as the VCAA's, even if it is just because it is easier to follow.
For anyone who doesn't want to scroll down through a PDF, here is an image of the VCAA's PSM:
Find it here
For people wanting to learn more about the GROW and 8D models there are some good websites here;
I hope this post helped you decide on which PSM to use, and while I never actually answered the question in the post title, I do not believe it is specifically good or bad, just that there is a place for every methodology and in many situations the VCAA's PSM may be too complicated for many situations...
