Software Development Process Described Through a Case Study

The customer owns the Zuma game engine, which accepts level configurations in a specific data format.

Writing level configurations manually is relatively complex, so the goal is to develop an application that would allow for easier configuration of levels.

Levels and their configurations can be accessed in Zuma Level Examples.

By analyzing the customer's description, the following characteristics have been identified: Product scope is final and the problem falls into the Precise Assignments category.

The chosen development approach is the Waterfall development approach, since it is the most reasonable choice when both the problem and solution are clearly known (without the need for continuous feedback).

Having a clear goal that is to be achieved with the software solution, and having chosen a development approach, the requirements and offer can be prepared.

Usually, in cooperation with the customer, both are combined into one document, which serves both as the specification and for legal obligations.

An example of this document can be accessed in the Zuma Level Designer Offer.

To start with the technical solution, the code architecture should be chosen. The goal is to apply general conventions and rules that best fit the requirement.

For individual components, the MVVM pattern is chosen.

In the integration part, a one-way hierarchy is achieved, with the App component utilizing the LevelBuilder component, and the LevelBuilder component utilizing the CanvasLevelBuilder.

The responsibilities include JSON processing, processing basic input level data, and managing canvas-drawn level data, respectively.

Besides the general requirements found in all web projects, sometimes there are project-specific functionalities needed. General code patterns do not necessarily fit these.

In this project, that is the 'canvas drawing' section, particularly tunnel calculation. Tunnels can be opened and closed only on paths, which separates them from all other elements.

An abstraction named 'tools' is incorporated, and only pure functions are utilized.

Apart from various automated tests for units such as tunnel calculations, a final manual test is performed.

One of the level designs that is tested is shown in the image.

In the applied test, the following can be observed:

The visible area is correctly matched.

All tunnels are oriented correctly.

Paths and platforms are correctly rendered.

Balls are correctly generated.