You are going to individually create a program that demonstrates the skills you have learned this semester. Each of you will choose a different program to make. Claim your project early.
It is up to you to ensure that you demonstrate all the skills required. Your exam will be marked according to the specific skills you show in your project. You will get credit for that skill if it works naturally and purposefully as part of solving your program's task.
Exam evaluation (The exam is worth 20% of your final mark)
- 10% - //HTML
- 10% - //CSS
- 5% - //INIT
- 5% - //INPUT
- 15% - //PROCESS
- 5% - //OUTPUT
- 20% - //Programming structure
- 20% - //STYLE
- 10% - //CHECKLIST
Questions to ask before you start
- What will you program do?
- What will your user interface look like?
- What variables and data structures will you need to store information?
- What will you have to set up during initialization?
- What will you use for input?
- Please list the processing functions/methods that will be required:
- What will you do for output?
- How will you use an object oriented programming in your program?
Saving your work
Please save your work as "
Some examples of applicable programs
- A simple game: A version of X's and O's, hangman, minesweeper, connect four, 2048, checkers, chess
- A unit-to-unit battle simulator
- A program to demonstrate properties of physics, chemistry, biology, or another science (eg, the game of life)
- A fractal generator or math toy
- A twitter bot
- A statistics viewer or analyser
- A random encounter generator
- An interactive map
- A sound board
- A inventory checklist
- An online shopping cart
- A bank account balancer
- Team game roster creator
- An online portfolio: photo gallery, sound clips, video clips
- A dramatic experience creator
- A military organization tool
- A car price calculator
- An interactive graduation ceremony
- A news site
- A stock monitor
- and so much more...
- a dating sim
- Conway's game of life
- Sieve of Eratosthenes
- A map creator
- Get things working in bite-sized chunks.
- Use console logs to tell you where you are in your code.
- Use console logs to tell you what values your variables contain.
- Do CSS work when you are stuck or need a break.
- Plan your data structures carefully before you start.
- Have a clear definition of what you want input and what you want to output. This makes the process much easier.
- When looking online for advice, keep in mind that the quality of publicly available code is iffy. Get me to take a quick look at it...