Class hours: 9:40 – 2:05
Mr. Bohmann
wbohmann@ewsd.org
Today’s Notes
- Welcome to Week 36 Wow! Our last full week together!
- No School on Monday, May 30th – Memorial Day
- June 9th is your last school day and Recognition Night but…..
- ALL missing work turned in by Friday June 3rd at 2:05. If you have missing work after this date you will start working with Mr. Curtis & Ms. Charron to make a plan to come back to school after summer starts (Friday June 10th and on). That would be a bummer
- Today is an EHS A Day
- Carter – NOON – VSAC meeting in the conference room – do not miss!
- May 31st 11am – Dan M. & Isaac Portfolio Presentations in m116
- Wednesday – Game Walkthroughs – screen casts – more on this tomorrow
- This week – CAWD Game Dev continues….
- Next Week – Prepare Games for deployment / testing – we’ll also officially wind down and prepare for the Certified Web Apprentice Certification
9:40 Attendance
9:45 Monday Mail – let’s see what everyone is saying….
9:45 Unity Mini Lessons
We’ll start at 9:50 in row 5 (Vincent) for presentations.
Week 35 Unity MiniLesson Dropbox
Talking Points
- What is your topic
- Give us the broad strokes – overview of what your topic is all about
- How can we use this in our own games / why should we know about it
10:35 Mask Break
10:45 English with Ms. Yopp
11:35 Game Studio Work time
| Date | Week | Deliverable | Software Development Cycle |
|---|---|---|---|
| May 23rd – May 27th | Three | GUI, Movement, Core Mechanics | Design / Implementation |
| May 31st – Jun 3rd | Four | Prototype with game play | Testing/Maintenance / Publishing |
| June 6th | June 6th Game Jam |
This week you are going to take your Game Design Document and your Trello planner and begin the Design and Implementation stage. You should be into coding your game mechanic if not done already, adding design elements and some game play!
The design phase is where requirements are transformed into concrete, detailed plans to help you write code. Given certain requirements, there could be many possible approaches to meeting those requirements. A design document will describe exactly how the program will be written, including details such as:
- How your player needs to move
- What kinds of input and output need to be displayed on the screen
- How many levels / design need to be created to challenge the player
- How to show your win / lose conditions
The Implementation phase begins once the program requirements and design are clearly understood and documented. It’s at this point where you can begin to write the code to meet those requirements. The design document provides guidance on exactly how to create the game, so you should reference what you wrote.
Most of the projects we programmed in class started at the implementation phase because the requirements and design were already determined by me ahead of time. I took time in my lessons to go through the planning and design phases.
5 Minute Scrum Meetings / Update Trello Boards
Remember a good meeting is quick and on target. What am I working on today, What help do I need. Those are the questions you should be responding to in your group or individually.
12:15 Lunch
12:45 Focus on Literacy
1:05 Mask Break
1:15 Production Time & Guided Support
CAWD Fun Games Studio work time (my fancy way of saying work with your game / game team
Wednesday – Game Walkthroughs – screen casts.