Maxstate
02-14-2010, 06:24 PM
1) Lay down functional documentation:
Explain all the necessary functionalities of all basic systems.
2) Create and import the first player model:
We should do this as soon as possible as it is the only thing keeping us from number 3;
3) Create animations for the first player model:
Base all animations on this original model and then just endlessly adapt the model.
4) Design the systems:
4a) Design the first maps and textures;
4b) Design the first HUD;
4c) Design the first option and menu screens;
4d) Design the first profile screens;
4e) Compose in-game music;
4f) Record basic sound effects;
4g) Discuss storyline and make sure it is clear;
4h) Resolve any in-team issues before continuing.
5) Lay down the technical documentation:
Explain all the necessary technicalities and details of all systems.
5b) Request a website and forum for easier communication.
5c) Present all written functional documentation and let it pass peer-review.
6) Start work on the first drafts of the HUD system.
7) Start work on the first weapon and item models.
8) Realize the best designed maps.
9) TEST 1: Populate the map with players, weapons, items and test for stability.
10a) If test is succesful, continue creating models and textures according to functional documentation; document changes;
10b) If test fails, revert all latest changes and find the error; fix error before continuing.
11) Realize the best HUD, option, menu and profile screen designs.
12) Implement HUD, option, menu and profile screens;
12b) Make screens available to player;
12c) Test out all facets of screens; see whether user can navigate around the menus without problems.
12d) If test is succesful, document changes;
12e) If test fails, revert all latest changes and find the error; fix error before continuing.
13) Populate the HUD with all counters defined in the HUD documentation;
13b) If test is succesful, document changes;
13c) If test fails, revert all latest changes and find the error; fix error before continuing.
14) Populate the menu with all choices defined in the menu documentation;
14b) If test is succesful, document changes;
14c) If test fails, revert all latest changes and find the error; fix error before continuing.
15) Populate the options screen with all options defined in the option documentation;
15b) If test is succesful, document changes;
15c) If test fails, revert all latest changes and find the error; fix error before continuing.
16) Populate the profile screen with all skills, categories and player attributes defined in the profile screen and skill documentation
16b) If test is succesful, document changes;
16c) If test fails, revert all latest changes and find the error; fix error before continuing.
17) TEST 1: Test all populations for stability;
17b) If test is succesful, document changes;
17c) If test fails, revert all latest changes and find the error; fix error before continuing.
18) Release internal Alpha version 0.1 for testing;
18b) If test is succesful, document changes;
18c) If test fails, revert all latest changes and find the error; fix error before continuing.
19) Continue to slowly populate game with new material and follow test & fix protocols as defined in 1xb, 1xc, etc.
Explain all the necessary functionalities of all basic systems.
2) Create and import the first player model:
We should do this as soon as possible as it is the only thing keeping us from number 3;
3) Create animations for the first player model:
Base all animations on this original model and then just endlessly adapt the model.
4) Design the systems:
4a) Design the first maps and textures;
4b) Design the first HUD;
4c) Design the first option and menu screens;
4d) Design the first profile screens;
4e) Compose in-game music;
4f) Record basic sound effects;
4g) Discuss storyline and make sure it is clear;
4h) Resolve any in-team issues before continuing.
5) Lay down the technical documentation:
Explain all the necessary technicalities and details of all systems.
5b) Request a website and forum for easier communication.
5c) Present all written functional documentation and let it pass peer-review.
6) Start work on the first drafts of the HUD system.
7) Start work on the first weapon and item models.
8) Realize the best designed maps.
9) TEST 1: Populate the map with players, weapons, items and test for stability.
10a) If test is succesful, continue creating models and textures according to functional documentation; document changes;
10b) If test fails, revert all latest changes and find the error; fix error before continuing.
11) Realize the best HUD, option, menu and profile screen designs.
12) Implement HUD, option, menu and profile screens;
12b) Make screens available to player;
12c) Test out all facets of screens; see whether user can navigate around the menus without problems.
12d) If test is succesful, document changes;
12e) If test fails, revert all latest changes and find the error; fix error before continuing.
13) Populate the HUD with all counters defined in the HUD documentation;
13b) If test is succesful, document changes;
13c) If test fails, revert all latest changes and find the error; fix error before continuing.
14) Populate the menu with all choices defined in the menu documentation;
14b) If test is succesful, document changes;
14c) If test fails, revert all latest changes and find the error; fix error before continuing.
15) Populate the options screen with all options defined in the option documentation;
15b) If test is succesful, document changes;
15c) If test fails, revert all latest changes and find the error; fix error before continuing.
16) Populate the profile screen with all skills, categories and player attributes defined in the profile screen and skill documentation
16b) If test is succesful, document changes;
16c) If test fails, revert all latest changes and find the error; fix error before continuing.
17) TEST 1: Test all populations for stability;
17b) If test is succesful, document changes;
17c) If test fails, revert all latest changes and find the error; fix error before continuing.
18) Release internal Alpha version 0.1 for testing;
18b) If test is succesful, document changes;
18c) If test fails, revert all latest changes and find the error; fix error before continuing.
19) Continue to slowly populate game with new material and follow test & fix protocols as defined in 1xb, 1xc, etc.