A Breakdown of the author's 'ABC' Methodology.  Created for the School of Information Systems, Multimedia Systems at The University of NSW.



MULTIMEDIA DEVELOPMENT OFTEN IS REGARDED AS MORE OF AN ART THAN A SCIENCE. AND PERHAPS RIGHTLY SO. BUT WHERE DOES THAT LEAVE THE DEVELOPMENT SIDE OF THINGS? WHAT STRUCTURE DOES YOUR SYSTEM FOLLOW? WHAT METHOD IS THERE TO THE MADNESS?

AS PART OF MY WORK AS AN ASSISTANT TUTOR FOR SISTM,  I DEVELOPED THIS DISTINCTION-AWARDED METHODOLOGY AT THE SCHOOL.

Introduction.

Methodologies abound. Their approaches and durations differ as much as their nomenclature. This article outlines a Methodology unique to most others, but which offers more of an evolution, rather than revolution against existing methods.

More concrete fields of system development such as applications, the web, software and network computing have a plethora of methodologies at their disposal, and are almost spoiled for choice.

The one factor uniting most formal Multimedia Methodologies is a desire to bring structure to abstract forms and designs. Multimedia fields often get disgregarded in the research into development approaches and philosophies, because of the "creative" aspects of a lot of the work.

This means the industry is at a disadvantage.

Approach.

'Had I been present at the creation of the world I would have proposed some improvements'

- Anon.

The Alpha Beta Collective (ABC) Methodology relies on explicit planning early on the piece, to ensure that quotes such as that above are avoided later on.

Planning of course, is far from a paradigm shift when it comes to the basis of most methodologies. Nevertheless, explicit emphasis on planning, followed by a swift execution period, is the focus of the ABC Method.


 

The above schema shows from a high level the reiterative process that the ABC Method revolves around.

Starting off with an initial Alpha system design, we progress re-iteratively up to an infinite (hopefully not) number of beta designs. The final repeated beta is the successful system design, whose features are 'locked in' and we progress to our Gamma (Release).

The Collected Gamma is so called because it incorporates all positive elements of all progressive betas, while dismissing any undesirable elements of the system previously discovered.

Alpha Stage Summary.

Set in concrete the User Cases, and begin construction of Wireframes that demonstrate typical User Processes executing correctly.

The Alpha Stage focuses heavily on the Brief of the Project, and conjures possible ways to satisfy the User Requirements.

 
Beta Stages Summary.

Resubmit the Beta System Design to the Customer until the set-in-concrete Specifications are met.

The Beta Stage(s) do not add any extra functionality, but concentrate on ensuring Customer satisfaction levels increase exponentially for each Beta.


Gamma Release Summary.

The Gamma Release is the Customer Release. Reiterative development during previous stages (Betas) ensure that the Gamma Release is successful.

A full copy of the ABC Methodology can be requested, simply by emailing the Author with a quick outline of your requirements or system.