Check your Discord daily to ensure you stay up-to-date with all communications.
Please check the online syllabus for the most up-to-date schedule and assignment metrics.
When using Zoom, be on time and have the camera on for participation, if possible.
Send emails professionally, always including a proper greeting and signature.
I will respond to emails within 24 hours on workdays. If you email me on Friday night, expect a response on the next business day after holidays and weekends.
Academic practice emphasizes transparency and reproducibility. Classmates should be able to review the creative and technical methods used in your work. If you have programmed something, include your source code and provide step-by-step instructions in your report. Additionally, if you used any UI software, capture screenshots of each process you followed and explain them with captions. Ensure that you include these step-by-step instructions using screen capture software [1, 2]. In this course, it is permissible to use code from the internet, provided that the source is properly cited in your report. The writing and report must be entirely your own original work. Lastly, ensure that the title of the report is included in the page header and your last name along with the page number in the page footer on every page. The preferred citation style for business reports is IEEE BibTeX.
Please do not push new contents to submitted repository (shared URL) after the deadline, doing so could considered as a late submissions. If you have to continue working for personal reason, make sure to continue working on cloned the repo.
Example of citing unity asset in IEEE BibTeX:
@misc{unityradar,
title = {Deluxe Compass Bar},
author = {While Fun Games},
year = {2019},
abstract = {Deluxe Compass Bar asset listed in Unity Asset Store. The package include a GUI and script package to include a compass and object tracking GUI designed for FPS game.},
howpublished = {https://assetstore.unity.com/packages/templates/systems/deluxe-compass-bar-53856%7D,
version = {1.3},
date = {2019-02-13},
note = {Accessed: September 2022}
}
In addition to weekly course activities, students will be responsible for completing two assignments and one final project for the Spring 2025 semester. Each assignment and final project must be documented in written form and submitted on the class Google Drive/ GitHub prior to the class on which they are due. Communicate with the instruction team ahead of time if you have trouble submitting or will need more time to complete the assignments.
It is your responsibility to check the weekly course schedule regularly, please check once a week.
Please check class Discord channel announcement once a day.
A weekly survey submission is part of attendance, so make sure to fill out the survey right away.
Make sure to include your source code and step-by-step direction in the report.
Please carefully review both the assignment and schedule sections found in this online syllabus for any updates, as details will be added as the course progresses. Note that adjustments to the course are made to better assess the student profile and learning progress, ensuring the course remains relevant to students' interests and project ideas.
When communicating with us, please be prepared. Organize your thoughts and develop creative pipeline ideas when applicable. Have mock-up images or doodles ready to show when explaining the project to the instruction team. Bringing sketches, drawings, or even simple 3D renderings will further assist you—the more detail you provide, the better we can help.
First, please change your nickname for the server to your full name, First and Last (this will not affect your Discord profile in other channels you are already associated with). Do not post anything on the "announcements" as it is reserved for the instruction team. Please use emojis to respond to the announcements—so we know how many students have seen it. Please check the class Discord channel at least once an every other day. Please feel free to use "assignments-questions" to help each other and collaborate between students. "student-only" channel is reserved for students to communicate about anything. Use this link to join the class Discord channel [1, 2]. Please respect the communication protocol, and do not send a direct message to the instructor on Discord. For important message such as class missing, family imergency, request to meet, are all should be done through eamail.
Your weekly logs and research journals should reflect your experiences throughout this course, including your thoughts, ideas, sketches, notes, responses, activities, and independent learning. By the end of the course, this documentation will serve as an extensive record of your research process and course assignments, making it a vital component for your learning and research development. Use this space to describe your weekly progress on assignment projects, outline individual tasks, and highlight your contributions. Additionally, it can serve as a platform to formulate a technical instructional manual.
Your Weekly Logs should be located in: Google Drive -> Your Name -> Google Docs (week 01). Your Weekly Logs are just as much for you than they are for us. Keeping an organized document throughout the course will primarily benefit you. The only requirements we have are as follows:
Keep your logs in a google doc inside the shared student folder on our drive.
No less than 250 words per week.
Make sure to attach as much as screenshots of what you are working on
Look through examples found in class Google Drive -> Keanu REEVES (example)
Feel free to be as creative with these as you would like!
Weekly Logs Due every Saturday 11:59 PM
© You-Jin Kim
College Station, Texas