Game Development Methodology

Story Board

Building the storyboard is an integral part of putting together an animated feature. The process provides not only a visual interpretation of the script, it also allows designers in each area to get a feel for what is being presented on screen.

At GameZ3, we follow a specific process for story boarding which is shown below

User Interface Designing

At GameZ3, we first of all understand the user requirement and then developed the objects and before developing the complete User Interface, we work with the prototype of the interface to that we can reduce the wastage of resources in repetitive work. We try and work in iterative model on the prototype so that we can come up with User specific design in short possible time and resources.

Below is the process of how we develop the User Interface for games at GameZ3:

Game Programming

Once the requirements are gathered and we have a well defined user interface, the programming for the game takes place. Here also, we try and follow the practice of iterative development so that redundancies are discovered very early in the life cycle of the project and hence, no loss of time and money occurs in the repetitive work.

Code reviews are conducted on an ongoing basis. Typically, upon completion of each module, its code is reviewed to ensure that coding is done according to laid out guidelines and that code is correct, readable, clean and maintainable.

Backend Development

This is the phase that runs parallel to the programming phase as, the backend development. According to the programming schedule and the requirement the backend of the game is developed.

The backend development of the game will include developing a database to store the scores of the users who submit the score after playing the game.

The database will have data stored in terms of the highest scorer first. People scoring the same score will be sorted based on the other parameters such as time, date of scoring etc.

The game will access the database to display the results of the highest scorers after the user finishes the game and submits the game. The interface of the game will show top 50 scorers of the game till date and the user score of the current users if his/her score does not appear in top 50 list (that means the interface will show 51 records at a time).

Game Testing

Test Planning is done at the onset of project in project planning phase. Test plan outlines the types of test to be performed, resources, tools and responsibilities for test related activities.

For unit testing, the developers, themselves are made responsible for the quality of the module they are developing.

Integrated Testing: During the integrated testing the entire game is deployed on the internal test server for QA Testing. Issues would be assigned to the development team and they would be resolved by the team. QA Engineer does a final verification of resolved issues before finally closing them.