be-course-18-19
Oral Test - Team
You’ve worked iteratively (formative) on your product and finish with an oral test (summative) where you present your final project with your team. First you’ll present the whole project as a team, then you’ll show how you contributed to the project and explain if you reached your own goals you’ve set at the beginning of the project.
You will show you can create a quality project in which you apply the subject matter of this course and that you understand it. You will answer questions in such a way as to demonstrate sufficient knowledge of our goals.
This is a team assessment but you’ll be graded individually! Each prototype contains an individually recognizable contribution of you based on the learning goals of this course. So, you need to show you worked on something for back-end. For example; you can’t just work on the CSS of the project because that was your role. Working with CSS is not a learning goal of this course.
Preperation
Presenting your work is a skill all by itself, make sure you and your team prepare yourself properly. The best way is to treat it as public speaking and there are many books on public speaking available.
- Bring your own computer and a charger.
- Have the latest version of your code ready in your editor.
- Open up your docs inside of your GitHub repository.
- Have a live version up and running.
Make sure your repository stays online after the oral test is finished, we might want to check the code handed in on GitHub after the test. We also want to download and archive your project when it’s done.
Rubic
| 1-2 | 3-4 | 5-6 | 7-8 | 9-10 | |
|---|---|---|---|---|---|
| Application of subject matter | Git, npm, a database, or Node are used; the web server runs without errors | Data is read from (HTTP GET), removed from (HTTP DELETE), and created (HTTP POST) on the server; users can input (files) and retrieve data | Data is changed in the database through the web app; users have different states trough sessions, the web app is deployted | The web app and database contain well-chosen features or methods of interaction; special care was taken to create a performant or secure web app |
😱 The way the student applies Git, npm, databases, and Node is more advanced than what they were taught in class; let’s switch places |
| Understanding | There is substantial own code; the student can explain the code that exists | The student can explain some parts of their code, how some parts works together, and tech stack | The student can explain every part of their code, how everything works together, and why software is used instead of alternatives; the project is structured logically | The project is complex but still understandable; the student carefully chose every part of their stack; software is used that was not covered in class; the student can make live changes |
🤓 The student understands JavaScript and Node’s programming principles and a geeky / nerdy conversation can be held about these principles |
| Quality | The project is handed in documented, on time, working, and on GitHub; in other words: proper | Code style is consistent (semicolons or not? double or single quotes? spaces or tabs? how many spaces? nesting…); code, project, and process are partially documented | Code adheres to standards; docs cover what the project is and does and the students process and choices | Code quality is good and enforced; docs are useful and professional |
📚 Code and docs both read like great books |
Note:
you’ll need a > 5.5 for each row to pass: you can’t compensate between rows
each of this rubric’s rows is cumulative: for example, to get a 5-6 on concept, you also need to have a 1-2 and 3-4.
| Checklist |
|---|
| Source code is available on GitHub |
Project is documented and has a readme.md |
| Cites the sources used; either in code comments or APA style in readme |
| Live version of the application is deployed |
| Seperation of concerns (HTML, CSS & JS) |
| Code validates and semantic HTML is used |
Publishing
Grades will be published and communicated trough Email, Moodle and/or Slack based on student numbers.
- Final grades will be published one week after test date.
- Final grades will be put in SIS two weeks after test date.
After the oral test you can request viewing time for additional feedback, this can be useful for a resit. Feel free to contact your lecturer if you want to do so.
Plagiarism
💁 We don’t like plagiarism and report it to our assessment committee (examencommissie in Dutch). See ¶ 6.1.2 of Teaching and Examination Regulations (TER) 2017-2018 (in Dutch: Onderwijs- en examenregeling, OER) for a full definition, but here are a few cases that count as plagiarism:
a. using or copying someone else’s texts, data or ideas without a full and correct acknowledgement of sources; b. presenting the structure or central ideas developed by someone else as your own work or ideas, even when a reference to other authors has been included;
[…]
e. copying (parts of) media files or other sources, software source codes, models and other diagrams of other people without acknowledgement and allowing it to be held as your own work;
[…]
g. copying the work of fellow-students and allowing it to be held as your own work;
[…]
Copyright
You are not allowed to simply use portions of someone else’s work in your project. The copyright is owned by the creator of the work. You must cite the sources used. Quoting or using material without a source citation is plagiarism and is punishable.
More information on the Student Copyright Information Point
The manner in which you cite your sources depends. The most widely used style at the AUAS is APA of the American Psychological Association. Make sure you cite your sources in the repository or documentation of your project on GitHub.