diff options
| author | Jaro <jarorutjes07@gmail.com> | 2024-09-18 19:30:48 +0200 |
|---|---|---|
| committer | Jaro <jarorutjes07@gmail.com> | 2024-09-18 19:30:48 +0200 |
| commit | 28d0733146aa3a8ba720bda20ff66ffa4cf4e64d (patch) | |
| tree | 3de2ee3439aca0c2474e9ebc0e2c5125a9f60c10 | |
| parent | 40f485af1bdcc04477a2cfcb71c899d397d7c6e6 (diff) | |
added feedback to project plan
| -rw-r--r-- | plan.tex | 5 | ||||
| -rw-r--r-- | sources.bib | 7 |
2 files changed, 11 insertions, 1 deletions
@@ -53,7 +53,10 @@ Finally, because the client does not want to dive deeply into the engine himself \subsection{Goal} -The goal is to develop a custom game engine that meets the client's requirements for maintainability, extensibility, user-friendliness, and adherence to a Unity-like structure. In addition, a validation application is created to show and test the engine's features. +The goal is to develop a custom game engine that meets the client's requirements for maintainability, extensibility, user-friendliness, and adherence to a Unity-like structure. The engine may integrate third-party software (as agreed with the client) to support specific features, such as audio, physics, and rendering. In addition, a validation application is created to show and test the engine's features. + +\subsection{Scope} +The requirements document \autocite{crepe:requirements} has several requirements with a MoSCoW `must', `should', `could' or `won't' priority to indicate the project's scope. \subsection{Result} diff --git a/sources.bib b/sources.bib index 50f5ead..8d96ce1 100644 --- a/sources.bib +++ b/sources.bib @@ -47,4 +47,11 @@ date = {2024-09-10}, } +@misc{crepe:requirements, + author = {Loek Le Blansch and Wouter Boerenkamps and Jaro Rutjes and Max Smits and Niels Stunnebrink}, + title = {Requirements}, + url = {https://github.com/lonkaars/crepe/blob/master/requirements.pdf}, + date = {2024-09-10}, +} + |