FINAL PROJECT PROPOSAL: Magnus Opus and Exigence > High Level Documentation for Video Game
Z, is for a specific game or is your project a more generic approach to the complex task of writing such code.
Do you have analogs on how to do this? We spoke briefly about README files. Do you place such annotations in a task folder? Is this organized by time (SLACK looks very horizontal time-line organized) or by hierarchy, where layers matter.
Tell me a bit more about this guidance document for work flow/programming tasks.
Do you have analogs on how to do this? We spoke briefly about README files. Do you place such annotations in a task folder? Is this organized by time (SLACK looks very horizontal time-line organized) or by hierarchy, where layers matter.
Tell me a bit more about this guidance document for work flow/programming tasks.
April 21, 2019 |
MbS
MbS
Its for a specific game I dont have a title for yet. The document is organized by features/priority. This is a (bad) example of one http://www.shodor.org/~pfears/high%20level%20design.doc. I've worked on some in the past and mine will be a lot more fleshed out.
April 22, 2019 |
Zain Bhaila
Zain Bhaila
correct link: www.shodor.org/~pfears/high%20level%20design.doc
April 22, 2019 |
Zain Bhaila
Zain Bhaila
Context: High level documentation helps with the development process, and is essential to larger projects to keep them organized.
Purpose: To help myself organize my development and keep track of my project ideas and goals.
Design: Multiple subsections focusing on different areas of the project. Overview of the project and preliminary user guide.
Citation Style: informal links