Skip to content

Project 4 Submission

Below are the steps to "submitting" a completed project, although the code review is only required for 2 out of the 4 projects.

Warning

The end of the semester is a hard due-date! I recommend submitting the project and doing your code review early enough to give yourself enough time to make project corrections!

Screenshots

Place all screenshots the screenshots/project-4 directory.

  1. successfulBuild.png show the program builds without errors.

  2. addValidation.png show how the employee add jsp validates user input.

  3. addSuccess.png show a successful add with the success message on the employee add jsp.

  4. addMessageRemoved.png show in your code where the successful add message is removed once you navigate away from the add employee jsp.

  5. searchSuccess.png show a successful search with the employee you just added. (make note of the ID created)

  6. searchId.png show a successful ID search with the employee you just added.

  7. searchLastName.png show a successful Last Name search with the employee you just added.

  8. searchNotFound.png show a search when the employee is not found.

  9. javaDoc.png show the JavaDoc script running without errors.

Push your code to GitHub

  1. Stage all your changes for the next commit.

    git add .

  2. Commit your code with a meaningful message

    git commit -m "some meaningful message here

  3. Push your code to your remote repository

    git push

GitHub Issue & Reflection

  1. Create a new issue in GitHub, title it: "Project 4 ready for review".
  2. Reflect on Project 4: Copy the below text and paste it into the "Add a description" textarea.

Note on Question #2

Question 2 can be submitted in any format! If you would rather tell your Project 3 story through audio, video, drawings/FigJam, or whatever you have in mind, let me know!

Suggestion: Work on this reflection in another document and copy it all to your issue once complete. 

@kkschumacher

## Project 4 Reflection

#### 1. Are you completing a code review for this project? If yes, place an "X" between the brackets [] to indicate which review you plan to complete.
- [ ] MS Teams
- [ ] Recorded video

#### 2. Tell your Project 4 "story". Describe how it unfolded, from its overall learnings to the obstacles and pitfalls you encountered along the way, whether they made you cringe, caused frustration, or left you exclaiming "oh no!" Your commit history should help you reflect on your project journey. Elaborate on the creative approaches and solutions that took you from "oh no!" to "I got this!". Emphasize the significant takeaways and knowledge you acquired throughout the project's journey.



#### 3. Look back at your commit history. How many git commits did you create during this unit? Do your commit message show the process and progress through the project, if yes, how so?



#### 4. Now that you have finished your code, look back at your planning document. What about your plan was correct? What was incorrect?



#### 5. Look back at the Project 3 reflection in your closed issues. Have you made progress in the areas you chose to improve on? Explain.



#### 6. How do you feel you have grown as a developer during this course?



#### 7. Look at the work you have completed and the "Grade Bundles." What grade do you feel you earned in this course? Why?

Schedule Code Review

See Project 4 Code Review for details on the parts to code review.

MS Teams

If choosing to do a MS Teams code review, schedule an appointment with me. If there is not a date/time that works for you, please Slack me so we can work to find a time that does work.

  • Schedule a MS Teams Code Review

  • If you need to cancel your code review, you can cancel the automated MS Teams meeting.

  • If you need to reschedule your code review, you can cancel the automated MS Teams meeting and go back to the booking link above.

Recorded Video

  1. If recording a video, please share your 20 minute video with me through Slack.

Making Corrections

If you receive a "Not Yet" mark on your project code, you are encouraged to make corrections to your code.

  1. Using the verbal feedback your instructor gives during the code review or written feedback in GitHub, make the necessary updates to your project code.

  2. Add, commit, and push all your changes before the due date.

  3. Reply to your GitHub Issue and include the list of the changes/corrections you made.

  4. I will review your changes and reply to your issue with any additional feedback.

Finalizing Your Project

One you receive a "Met" mark on your project, it's time to tag your project!

  1. Tag your project as v4.0-project1. See Tagging Your Project for instructions on how to create a git tag.