Programming III. requirements
PROJECT WORK REQUIREMENTS
The students have to prepare a simple game that is
- A game with simple logical/action game with simple user interactions (controlled
by the mouse / keyboard).
- Fulfils the basic principle of the separation of layers (separation of the business
logic, and the MVVM-based separation of the WPF code).
- Display using Shapes / DrawingImages / FrameworkElements.
- Game development framework (e.g. XNA, Unity) is not allowed!
- Display framework (e.g. SDL, DirectX, OpenGL, Vulcan) is allowed, but the time
spared on the display layer by using such a framework has to be spent on
developing the game logic!
Deadlines:
- The exact deadlines will be announced at the start of every semester by the lab
teachers
- 2-pages-long specification: third week (rules, user interactions, a screenshot plan /
mock user interface, address of bitbucket project)
- Final deadline (program, and all required documentations): the beginning of the
week before the second test
- Supplementary deadline: the end of the week before the second test
- Defence: according to the decision of the practice teacher; during the second test
or during the re-test or in a separated time slot.
- Competition: for the best-quality student projects, after the semester
The best works can be presented in a visual application development competition,
where the winners can be awarded with one or two extra grades, or even with the
acquittance from the software parts of the entry-test in the professional
comprehensive exams.
Expectations when submitting the project work:
- GIT project hosted at bitbucket.org, with full and compile-able source code
o For using the GIT, see the prog_tools documentations’s ​GIT QUICKSTART
chapter.
o The repository name must contain the Neptun code of the student:
OENIK_prog3_<semester>_NEPTUNCODE
▪ where value of the <semester> part contains a year + one of the
strings
‘autumn’
or
‘spring’
concatenated;
e.g.
OENIK_prog3_2016autumn_X0XY0Y
o Admin permissions for the repository must be given to the practice teacher.
o The project must show signs of continuous development; the version
control should not be simply 1-2 commits before the deadline!
2017-02-16
1. oldal
Programming III. requirements
o The repository must contain every file that is required for the project to be
rebuilt and run, including all images and text files. ​Before deadline please
check specifically (either by downloading the repository to another folder
or to another machine) whether every necessary file is present. Projects
that cannot be rebuilt count as if they were not handed in.
-
Valid source code, according to the StyleCop ruleset oenik.ruleset (about using
Stylecop, the prog_tools documentations’s ​STYLECOP QUICKSTART​ chapter.
Developer documentation using HTML format, generated with doxygen
User documentation (in PDF format): title page + minimum 2 full pages: game
rules, controls, screenshots (minimum 1, and maximum N-2 images, where
N=number of pages. More screenshots are possible if they are aligned next to each
other.) Format as in the documentation of the example project. With most projects
that are of adequate difficulty this page count will be easily reached; but if the
documentation is less than the minimum number of pages, then additional
features need to be developed until the minimum number of pages is reached (so
we do not recommend leaving the documentation part until the last possible
moment).
Additional materials:
- oenik.ruleset
- example project work with documentation: exampleproject.zip or the newest
version on git: https://bitbucket.org/eszter_cseri/prog3_example_projects.git
- prog_tools.pdf
2017-02-16
2. oldal