Game Development Reference
One of the most critical aspects of the conversion process is the creation of a train-
ing plan to instruct users on how to operate the new product, and help manage the
changes caused by the new product.
Once the product has been deployed and tested, the project team establishes a sup-
port and maintenance plan for the new product. This plan usually includes a post-
implementation review, as well as a method to identify the changes needed for the
product. Optionally included are retirement plans for the product, generally
affected by changing technology and business rules.
The development methodology described in this topic is commonly known as the
Waterfall approach. This model is one of the oldest versions of the software devel-
opment life cycle. The Waterfall model is linear and sequential, and once a stage
has been completed, there is no turning back.
Imagine a waterfall rushing over a rocky cliff. Once the water has flowed over the
cliff, it cannot turn back. This is the same idea behind waterfall development. Once
a phase transitions into another, there is no turning back.
Waterfall development is advantageous in that it allows for managerial control. A
schedule is set with deadlines for each development stage, and the product can
proceed through the development process and be delivered on time, in theory.
Each phase of development transitions into the next phase in strict linear order,
without any overlapping or iterative steps.
The disadvantage to the waterfall development model is that it does not allow for
reflection or revision. Once an application is in the testing phase, it is very difficult
to modify something that was not explored in the concept state.
There are a number of popular software development methodologies, and each
model works best for different types of companies. Other development method-
ologies include SCRUM\Agile, iteration and increment, eXtreme programming
(XP), feature-driven development, Rational Unified Process (RUP), and Microsoft
Solutions Framework (MSF).
Development of a game itself generally utilizes the SCRUM\Agile approach,
whereas tools development typically follows either the waterfall approach or a cus-
tom model when there are only a handful of developers working on it.
The best development methodology to use depends on your company and project.