Description: Our requirement was to create a guessing game. The computer picks a number between 1 and 100 then gives indicates if the guessed number is higher or lower. There is also a time limit of 2:00.

Design Aspects: I used the audio and timer components of Javascript. I also limited the number of guesses to 7, so it's always possible but it's only always possible if the perfect algorithm is used.

Link: Guessing Game

Description: Our project was to take a group of photos of bacteria and try to "train" a system to determine which were the most likely to respond to 2 different antibiotics. Then run our algorithm on the entire set to see how well we did.

Design Aspects: We broke the photos down into sections, then ran K-Means clustering on the each corresponding section. This produced several clusters with different responsiveness to the antibiotics. From that we were able to do regression testing to determine whether new photos showed antibiotic resistance. This was all written in Python.

Link (opens PDF file): Bacteria

Description: Our project was to create our own version of "Who Wants to Be a Millionaire?" using Javascript, SQL, HTML and CSS and PHP.

Design Aspects: We used a MVC design philosophy. The model was build with SQL and some PHP, the Controller was JavaScript and some PHP, and the View was HTML, CSS and some Javascript.

Link: Millionaire

Description: The requirement for this was pretty vague: build an Android app that uses a variety of the topics covered in class, including a database, system services, animation, images, etc.

Design Aspects: We used a MVC design philosophy, SQLLite, GPS and Drawable Animations among a wide variety of other items available to Android developers in the Android SDK.

Link: Link: Poker Leauge

Description: The requirement was to make a game that keeps score. We chose to make Paper, Rock, Scissors, Lizard, Spock, a game based on Paper, Rock, Scissors that comes from the TV show "Big Bang Theory". This was our first project of the semester, so we kept it pretty basic. There were no graphics involved.

Design Aspects: One piece of this project, in particular, was eventually implemented in a way I didn't like. The winner decision was based on a series of if-then-else statements to determine which player scored a point. My preferred way of handling the decision was a 2-dimensional array based on the chosen item. Alas, I was not the one to implement that part.

Link: Link: Paper, Rock, Scissors, Lizard, Spock

Description: This was a seemingly simple assignment: build a calculator. But little direction was given as to how it should look. No direction was given as to whether or not orders of operatioin should be taken into account. In the end I decided to just do one operation at a time, but save the value of the operation for use in the next operation, if desired. A follow-up to this was to remake the view portion twice more with a different layout.

Design Aspects: Since I'm lazy and a generalist, I tried to keep the programming to a minimum. I made one function that handled all the number keys and a separate function to handle all the operation keys. I used a state machine to help design the possible interactions.

Link: Link: Calculator