CPSC 421 Object-Oriented Programming Spring 2026

News

---

• Week 2 Class 2 Tue Jan 20 Posted: Jan 20

  After Class

  • Exercise 5: Rainfall I

    • I posted a feedback report, Report1.md, in your repository under the branch feedback. I strongly suggest looking at it on GitHub:

    • I posted the scores and any additional comments in Brightspace

    Points were taken off for:

    • Differences between your code for a commit and my code in the example
    • Not following the exact format of the header comment
    • Typos in words
    • Less or more than 3 commits
    • Wrong form of the action in the commit message. It is "Add", not "Added", "Adding", or "add".

    Also, do not use term "assignment" or "exercise" in your code. We simulate working on real code.

    If you have spacing or wording to fix, you can fix them. However, these commits must start with the word "Fix". Not "Fixing", "Fixed", or "fix", but "Fix".

  Special Announcement

  Our class will meet online today in Teams. During the meeting, please be muted, but leave your camera on if possible.

  Our Team is CPSC 421-010 OOP 2:00 - 3:15 pm. You should see the meeting in your calendar. There is also a direct meeting link in Brightspace. If you have any problems, send a chat message in Teams or an email.

  Announcements

  • Office Hours Online today from 1 - 2 pm. I will monitor Teams. If you want to meet, start a chat with me in Teams.
  • TA We have a TA (Teaching Assistant) for the course, TA: Mr. Sumaila Iddrisu si63@uakron.edu

  • Grades Exercises 1 - 4 are in Brightspace. Read the feedback.

    Future exercise posting to Brightspace will not be announced. Delays will be.

  • OOP Survey Results Link in Brightspace
  • Development Environment Survey Results Link in Brightspace

  Agenda

  • Guide: GitHub Authentication
  • Setup for Exercise 6: Rainfall I

  • Exercise 5: Statement Design Quiz

    • Completed during class
    • All solutions in a question produce the same result
    • Must choose the "best" choice, and state why it is better
    • If you complete the Design Quiz, you will get full credit for this exercise
  • Notes: Rainfall Coding Practices

  • Exercise 6: Rainfall I

    You can follow along and see the commits that I make in class:

    OOPS26-Rainfall-010

    If you have any questions or issues, make sure to contact me.

  • Notes: Software Design Characteristics

  Unless otherwise noted, exercises are due by 3:30 pm on Wed Jan 21

• Exercise 6: Rainfall I Posted: Jan 20

  Take the starting rainfall.cpp code and make the changes that I make in class. This means the exact same code changes and exact commit message.

  Your code is in a repository from GitHub Classroom:

  1. Log in to your GitHub account.
  2. Click on the invitation link (GitHub Classroom Rainfall) on the main course page in Brightspace.
  3. Follow the directions to link your GitHub account to your UA ID.

  Environment

  1. Local

     This would be on your own machine with local files.

     First, you need to authenticate your local environment with GitHub: Guide: GitHub Authentication. This only has to be done once per environment, e.g. WSL on Windows.

     Then you clone the repository. Cloning creates a local repository that is a copy of your repository at GitHub.

     You can get the repo link from the button <> Code on GitHub, then under Local and HTTPS.

     Cloning a repository creates a directory with the name of your repository, e.g., _rainfall-_. To work on the files, you need to move into that directory:

  2. GitHub Codespaces

     GitHub Codespaces provides a development environment in the browser. When you create one from your GitHub Repository, you are already authenticated with GitHub and have a cloned repository, so you can start working right away.

     You can start a Codespace from the <> Code button on GitHub, then under Codespaces.

  Build Setup

  Git Workflow on Rainfall

  1. Edit files locally, e.g., add a header comment to the file rainfall.cpp
  2. Build, run, and check your work
  3. View your changes
  4. Commit current changes to the local repository:
  5. Push your local commits to the GitHub repository:
  6. View and verify your changes at GitHub in your browser Do not skip this verification
  7. View your commits locally

  Note Your code must build and compile. If you have a build warning or error, fix these before making any more changes to the code.

  Note You must commit each change that I make separately and use the exact commit message that I use in class

Archive