2022/3, Trimester 2, Face-to-Face, Edinburgh Napier University
VIEW FULL DETAILS
Occurrence: | 001 |
Primary mode of delivery: | Face-to-Face |
Location of delivery: | MERCHISTON |
Partner: | Edinburgh Napier University |
Member of staff responsible for delivering module: | Thomas Methven |
Module Organiser: | |
Learning, Teaching and Assessment (LTA) Approach: |
The module uses a mix of lectures and practical labs for direct teaching, and groupwork approaches to assessment.The lectures are themed towards separate parts of game design and engineering. The focus is on developing understanding of these principles within the context of the overall development of a game engine. The lectures cover learning outcomes 1-4.The practical labs are threaded together to allow an engine to be developed to run a game, with several sample games developed that use features as they are introduced. The labs cover learning outcomes 1, 2, and 4.Students are expected within their small groups to research further technologies and ideas and apply them to the overall engine being developed to provide an individualised project. There will be a significant amount of resources pointed to throughout the module, and this will allow the students to further explore the area. The additional material covers learning outcomes 1-4.
|
The module blends formative and summative assessment throughout. During the lab based sessions, students will be asked to discuss their current progress through the game engine development, and feedback and advice given as appropriate. This will include general approaches to software engineering, workflow and project management, and the overall clarity of code.The blend of formative and summative assessment is described in the summative assessment section.
|
The module aims to develop the students core software engineering competencies while allowing the student to develop a portfolio piece of work. As such, the formative assessment, although having four elements, feeds into a single narrative of work. The assessment is undertaken by pairs of students as far as possible.In week 3, the pair must present a short pitch presentation of their idea. A structure for the pitch will be provided. The aim of this presentation is to provide some experience in presentation in this manner, with suitable feedback given. Also, the pitch is designed to ensure that the pair have come up with a suitable idea, the idea fits with the module and the time available, and that the pair have undertaken an initial outline of the work involved. This assessment covers learning outcomes 3 and 4.In week 7 the students must submit a design document for their game. A format for this report will be provided. The document is in effect a contract for the deliverable for the final assessment. The document will have allowed the student to formulate an overall plan and set of requirements for the deliverable. Feedback will be given on the quality of the document as well as the proposed game. This assessment covers learning outcomes 3 and 4.In week 15 the final game deliverable, built using the game engine developed in the module, is delivered. This is the culmination of the different elements assessment up to this point. The game will be assessed based on quality requirements and technical complexity. This assessment covers learning outcomes 1 to 4.Also in week 15 the students will need to demonstrate their work. This provides the module team the opportunity to give instant feedback as well as discuss any areas which might not be so clear in the final product. Furthermore, the class will undertake a peer-review of the games delivered, including overall quality of the software products. This assessment covers learning outcomes 1 to 4.
|
Student Activity (Notional Equivalent Study Hours (NESH)) |
Mode of activity | Learning & Teaching Activity | NESH (Study Hours) |
Face To Face | Lecture | 24 |
Face To Face | Tutorial | 24 |
Independent Learning | Groupwork (Independent Study) | 152 |
| Total Study Hours | 200 |
| Expected Total Study Hours for Module | 200 |
Assessment |
Type of Assessment | Weighting % | LOs covered | Week due | Length in Hours/Words |
Oral Presentation | 5 | 3,4 | 3 | HOURS= 1, WORDS= 0 |
Report | 10 | 3,4 | 7 | HOURS= 0, WORDS= 1500 |
Portfolio | 75 | 1-4 | 15 | HOURS= 40, WORDS= 0 |
Oral Presentation | 10 | 1-4 | 15 | HOURS= 2, WORDS= 0 |
Component 1 subtotal: | 100 | |
Component 2 subtotal: | 0 | | | |
Module subtotal: | 100 | | | |