Computer Science and software engineering (CSE)
Problem 1.1.7 Scratch Game or Story
Checkers
Group: Laine Rudolf, AJ Russell, Noah Fonseca
Final Product:
|
Abstract: The game we decided to make was checkers. THe objective of the game is to Jump over your opponents pieces one at a time to capture them all. You can move one space at a time diagonally. You can only move forward. If you reach the opposite side of the board without being captured, you turn into a king. A king can move any direction diagonally.
|
Artifacts: Rubric, Product Backlog, Decision Matrix
|
Artifacts: Sketches, Code
|
Reflection
Throughout the course of the project, I learned many things. I learned how to solve problems on my own and with my teammates help, the basics of coding, and how to think in the language of code. The hardest part of the project was making the checkers jump over an opponents piece and take that out. The easiest part was moving the pieces without jumping. We didn't get the chance to do most of the more advanced tasks for the game.
Problem 1.2.6 Designing an App
Notepad
Partners: Laine Rudolf, Jacob Miller, and Gunnar Ickes
Final Product: |
Abstract:Our group decided to make an app that would assist the user in making reminders for themselves. For example, a user can create a grocery list, then they can check a checkbox that will allow them to choose a time and date to set a notification. We started with the GUI Interface and then moved on to the coding of the notification and then on to switching screens. My task was to create the GUI Interface for the note taking screen.
|
Artifacts: Rubric, Product Backlogs, Decision Matrix
|
Artifacts: Sketches, Code
|
reflection:
There were many ups and downs in the process of making this project. It was easy to get the text boxes and the date and time picker for the notification. however, it wasn't as easy to get the notification to actually work. If we had more time we could have played around with the notifications and maybe we could have gotten it to work. By doing this problem, I learned about different techniques for making an app, how to better utilize the agile design method, and how to figure out what would appeal to the app's users. The next steps for this app could be a better background, sharing notifications, or even a voice to typing method. Overall, I had a great time making this app and I hope to be able to make more sophisticated apps in the future.
Problem 1.5.4 designing a python gui
Tic-Tac-Toe
Partners:
Laine Rudolf
Anthony Alagna
Ryan Martin
Laine Rudolf
Anthony Alagna
Ryan Martin
Final product |
abstract |
Artifacts: Rubric, Product Backlogs, Decision Matrix
|
Artifacts: Sketches, Code
|
Reflection
We decided to make tic-tac-toe because it was the number in the middle on the decision matrix. It seemed challenging, but at the same time doable. I learned many new things about coding and how to problem solve by collaborating with my peers. The original goal was to have an X button and an O button. Whichever one was clicked would "pick it up" and you would click the game board where you wanted it to go. We couldn't figure out how to get that to work, so we asked another group for help with doing a right-click, left-click idea. That ended up working really well. If we wanted to take the game farther we could make it so the computer knows who wins and make it say congratulations to the winner.