Friday, March 4, 2022

For gaming software

As part of the article, I tried to give an overview of the "top level" of the application software development process. Each stage of the process, of course, needs a separate discussion with the obligatory consideration of the features of the developed software.


I note that the process diagram considered here is the result of a generalization of my personal experience in the development of various software tools. Like any generalization, my schema is an abstraction. And, like any abstraction, it has its limits of applicability. You can not thoughtlessly apply this scheme to a specific project. It is important to understand that each project has its own nuances that affect the organization of the development process. And therefore, for each project, the scheme presented here must be adapted, and in some cases it will be necessary to develop a fundamentally different approach.

Architecture development for gaming software

 Requirements and architecture development for gaming software often reuses lessons learned from previous projects. In this regard, the project termination stage also receives additional weight, when all useful developments must be recorded in the developers' knowledge base.


The delivery of gaming software takes place within a single stage. Even if a certain core, the “engine” of the game system, is first created, its operation cannot be verified without the implementation of the entire functionality of the system.


There are no beta or decommissioning phases for gaming software. Games immediately go on sale, and after use, they are simply deleted by the user as they lose interest in them.

For gaming software

As part of the article, I tried to give an overview of the "top level" of the application software development process. Each stage...