Skip to content

MVC Presentation

Objective

Create an interesting MVC application of your choice and share it with the class. Be creative! Build your application around something more interesting than a generic "contact". A few ideas to get you thinking about something fun and useful to build: a matching game, flash card quiz, golf score keeper, etc.

Requirements

  1. Either decide to work independently, or work with 1-2 other classmates to research and present a MVC application. It is highly recommended to work in a group to divide and conquer task and to practice collaboration (a skill all employers want to see)! If you need help forming a group, please let your instructor know and they can help.

  2. Build an MVC application with the minimum components:

    • 1 JavaBean
    • 1 Servlet
    • 2 JSPs

  3. The MVC application should also meet these requirements:

    JavaBean

    • The JavaBean should include at least 3 instance variables of two different types.

    Servlet

    • The Servlet should create a collection of JavaBean objects.

    JSPs

    • One JSP should include a diagram of your application.
    • One JSP should include a template/css for styling.
    • One JSP should display all JavaBean objects in a table (display all instance variables for each object).

Tips for working in a group

  1. Consider splitting up your team to allow individuals to focus on the various aspects of MVC. One person might work on the presentation layer, while another works on the bean code and the controller.

  2. To make working as a team easier, I highly recommend using a shared repository. This is also excellent practice with git and GitHub! A group assignment has been created here for you. One team member should accept the assignment, specifying the team name. This will establish the assignment for your team. After that, each additional team member can accept the assignment using that same team name. Finally, refer to the readme.md in the repository for more information about the repository use and contents.

Presentation

Each team will present their MVC application to the class.

Online-Live or In-Person Sections

You will do a live demo during class-time. If you prefer to record your presentation ahead of time and play it during your presentation time, that is a-ok. See Screen Recording Software for suggestions on how to record your presentation.

Online Section

Record your presentation and post the video in slack #challenges channel. See Screen Recording Software for suggestions on how to record your presentation.

Submission

  1. Post your work in the #challenges Slack chanel, include in your post:

  2. The name of your MVC application

  3. Your team name and group members (if applicable)
  4. Your recorded video (if you made a recording)
  5. A zip file containing your MVC application code

Rubric

All of the following must be satisfied to achieve a "Met" status

  • Creativity and Relevance: The MVC application is highly creative, unique, and engaging. It goes beyond the generic "contact" application and is both fun and useful. The chosen concept is well-suited for an MVC implementation.

  • Components: The MVC application includes all required components: 1 JavaBean, 1 Servlet, and 2 JSPs.

  • JavaBean: The JavaBean includes at least 3 instance variables of two different types. The instance variables are appropriately named, typed, and well-documented.

  • Servlet: The Servlet successfully creates a collection of JavaBean objects and manages the interaction between the model and the view. It is well-organized, handles exceptions gracefully, and follows best practices.

  • JSPs: Both JSPs are well-implemented. One JSP includes a clear diagram of the application's structure, and the other includes a template/css for styling. The JSP displaying JavaBean objects in a table is well-designed and functional.

  • (If working in a team) Team Collaboration: The team effectively collaborates on various aspects of the MVC application. Roles are clearly defined, and team members contribute cohesively.