Published in: 10 May 2018
9:00 GMT
Game engines are one of the highest forms of information technology known to modern developers, its hard to imagine game development space without these vital tools whether its the number of supported platforms or the huge number of developers or high number of games produced by them it definitely made a generational impact on the gaming industry.
One of main reasons for game engines success is that it allows a single person to make a full game, allowing the developer to write code, level design, game design and all aspects of a game, but this comes with a great cost of time. using development models wisely can reduce this time to optimize developer time.
System development is a system of predefined steps that guide the development of a software and clarifies the input output for the whole development process, therefore allowing its developers to produce a software with predefined specifications, it also has the repetition and cycle form where each cycle has repetition of certain tasks depending on the process where the end result is the product.
Even for one person working alone a well defined development process can be a great map to orient the developer to the best set of tasks to be in order to reach the desired product.
Defining project requirements and end product expectation.
Keeps goals features and versions well defined and under control.
Fastest way to get production ready versions continuously.
Visualization of the process can be best introduction to the process, the development process is as follows:
"Washing Machine" software development model, diagram 1.
"Washing Machine" software development model is named based on resemblance between the model and cleaning laundry.
Step 1: separate features into versions demo, version 1, version 2 and version x, each version should have enough features that are interrelated to each other with the demo version having the bulk of the vital features and version 1 having enough features to be fully playable.
Step 2: All the features of each version are listed, making the most important first and least important last. see figure 2
Features are highlighted in yellow, Figure 2.
Step 3: take each feature at a time starting from game play and ending with menu threw the process of graphics. coding then finally testing. see figure 2.
A feature going threw the cycle of graphics, coding and testing, figure 3
Step 4: At the end of each cycle after testing a question is raised if the feature is ready or not, if the feature is not ready its taken back to graphics or coding phase based on the results of the testing, if the feature is finished then its highlighted or omitted from the list of features. see figure 4.
Version demo and its corresponding set of features being marked, figure 4.
Step 5: Step 4 is repeated for all the list of features.
Step 6: If set of features are finished for certain version move that version into production and publish it. to take a look at the development model generally, see figure 1.
Step 7: Select next version and repeat the process to transform it into production ready version.
Note: The integration of features is applied threw out the development process.
Focus on 1 person up to 2 people development team.
Fastest way to reach production ready version.
Highly adaptive to change.
Grouping similar features is possible.
Next step is clear simple and straight forward.
Can sustain small to medium projects.
Can be performance orientated or visual quality.
Developer his strengths and weaknesses.
Limited to small teams ideal for 1 or 2 developers.
Integration is difficult with progress.
Indie game developers can reach their own optimal software development model threw their own workflow with time, however to those who need structure, general workflow guideline and understand software development model, "Washing Machine" development model can be a good tool.
For Further Questions And Details Contact Me:
Email : Murad.dasi AT gmail.com