Your will write an original video game using Pygame and Python in a student-managed team project. The theme(s) will be given during the end of the Pygame tutorials. Keep the scope of your game small.

You should decide with your group how you plan on coding. IDLE, Pyzo, Eclipse, repl.it are all valid choices. Which ones are you most comfortable with? What is the trade-off between comfort and functionality? Which are private, which are public? Which are supported in the classroom?

Here's the code that was used in 2018 to choose the themes.

import random

themes = ['earth', 'air', 'fire', 'water']

for groupNumber in range(0,4):

    drawn = random.choice(themes)

    print('Group # ' + str(groupNumber+1) + ', your theme is: '+ drawn)

    themes.remove(drawn)

Your team will be responsible for managing the software development process effectively, through all of its stages – planning, development, production, and closing. Due Dates at the bottom of this page:

Tasks

1. creating a software project plan by producing a software scope document
   1. This is a simple Preliminary Project Scope Statement.
2. developing the software product according to the project plan
   1. ensure that the software meets end user needs
   2. functions as intended
   3. produced within quality standards
   4. produced within timelines
3. Your game must be developed from an OOP design perspective. Create a UML drawing.
4. producing the software according to specifications:
   • max window size 800 x 600
   • no audio (unless you can drop the bitrate)
   • keep image resolution low (150 dpi)
   • do not install fonts for the user: set your copy and make it a png
   1. interview, code, test, deploy
   2. create user documentation
5. use an appropriate project management tools
   1. Explain to me, using an example, of how you will manage version control. This was covered in Unit 0 of ICS3U
   2. Gantt chart - See ICS3U notes
   3. Google Calendar - all members will be able to edit the calendar. Link Calendar to your site
   4. Google Sites - one member will build and maintain a website for your game. The site will have a public site and a private side. The public side will have your dev blog, screen shots, media, press releases, news, FAQ, etc. The private side will be for devs only. Your calendar and drive should be on the private side. Page-level permissions article.
   5. A developer blog - all members must post daily. Blog about your progress. Do not use an external blog site.
      1. USE FIRST NAMES ONLY.
      2. The ENTIRE world can READ your posts.
      3. All posts will be written in standard formal English.
      4. THIS FORUM IS RESERVED FOR YOUR DEV JOURNAL. It is not for posting personal messages to your classmates, or for asking me questions.
      5. You can write blog, then send it to the web admin so that they can update that portion of the site.
      6. Have fun, be courteous, treat each other with respect and be honest.
      7. Focus on what you built.
      8. Focus on positivity.
      9. Posts that are vague, negative, or promise work, don't mean much.
      10. Write about what you made, fixed, invented or collaborated on.
      11. If you didn't blog, just leave that entry blank.
      12. Avoid starting your posts with salutations - just begin.
      13. Images in the posts are great.
      14. Very little of you post should be about the promise or the intention of work, write about your contribution to the project.
      15. Standard English needs to be consistent. Web Admins, you NEED to proofread what you post, especially if you didn't write it.
      16. Blogs are 150 - 200 words in length.
   6. Google Drive - document / source sharing. YOU NEED TO USE VERSION CONTROL. Link Drive to your site.
6. Submit the game (source, sprites, backgrounds, assets, media) to me.
7. What would you do to maintain or build on your code? Write a 500 word report using specific details. What would you fix in version 2.0? Compare plan to actual performance, outline successes, make recommendations for improvement. All members must contribute to the report.
8. Your game credits must include where your assets (sprites, backgrounds, media) came from. Give credit to the original artists. If team members or students at our school created original sounds, music or art, please give credit.
   • If you have a team member that is drawing or painting sprite sheets during this unit, remind them that:
     • A) it can be done at home.
     • B) you need them to contribute to the code, the Gantt, the site, the UML and 2 reports.
9. A promotional / trailer / teaser / reveal video.

Things to Remember:

• Choose a spot to sit where each member of the your group has access to a classroom computer, even if they choose to bring their own machine to class. Leave that spot free for the remainder of the project.
• Exchange contact information between all members. You each need multiple reliable ways to contact each other. Trade this information on the first day. Members should provide a SMS / cell #, a valid email address (GMAIL) and a collaborative application like Discord are strong choices. If members refuse, or suggest social media DM's (direct messaging) speak to me directly ASAP. Test the contact information immediately.
• 1 minute meetings will be demonstrated. Begin each day with one. Hold each other accountable.
• Hold each other accountable. Spend your class time with coding and problem solving. Asset creation and large idea mapping should not be happening during the tutorial portion of the assignment, or the project management portion.

File Naming Convention and Project Size Limit

Please note that the Google classroom has a 20 file limit. If your project has many files, consider a zip archive that you build AT HOME. The project must be no greater than 10 MB (compressed in a zip archive, or uncompressed). For this project, use this naming convention:

1. Name your files using the class naming convention:
   1. GameName_assignment.py
   2. GameName_readme.txt
   3. GameName_image1.jpeg
   4. GameName_image2.jpeg

Due Dates:

ONLY THE PROJECT MANAGER CAN HAND IN THE ASSIGNMENTS.

Day 1 - Game name + URL (No Site content required at this point)

Day 7 - Gantt

Day 8 - Site + Drive - I already have your URL. I need you to provide SCREEN SHOTS (paste them into a Google Doc) so that I can LOOK at how you laid out your GOOGLE DRIVE. I DO NOT WANT ACCESS TO YOUR DRIVE.

Day 10 - UML

Day 10 - Preliminary Project Scope Document

Day 19 - Final Report

Day 19 - Game