Final Project Timeline

Table of Contents

2/20Initial client report due
2/25Project specifications report due
3/1User feedback report due
3/4, 3/6Project elevator talks
3/11Front-end design presentation (to mentor TA)
3/18Project checkpoint 1
3/18, 3/20Poster fair
4/8Back-end report due
4/15Selective project presentations
4/19Project checkpoint 2
4/24Client feedback report due
5/1Project testing report due
5/6, 5/7Final project presentations
5/8Final project due

Timeline

Initial client report: due 2/20 @ 11:59pm

You should plan to meet with your client before 2/20 so that you can turn this report in on time. During the meeting, you should get to know your client and familiarize yourself with their proposed project and the expectations they have for the semester.

The initial client report should be a write-up of how the meeting with your client went. It should include what your and your client’s expectations are for the project going forward. Meeting notes will suffice for this report.

The report doesn’t need to be longer than a double-spaced page. Please include the name of your project as well as all the names and logins of your group members.

Handin here: Link

Project specifications report: due 2/25 @ 11:59pm

If you would like a refresher on what specifications are, check out the "Requirements and Specifications" lecture, especially slides 27-33.

The project specifications report should include details about what you plan to implement in your project (not how you plan to implement things). Remember that requirements look at things from a user’s perspective whereas specifications look at things from a programmer’s perspective. Therefore, your report should include things such as:

In your report, please include the name of your project as well as all the names and logins of your group members.

Handin here: Link

User feedback report: due 3/1 @ 11:59pm

You should speak to at least three (potential) users about your project to bounce your ideas off of others outside the course. If you would like a refresher on talking to potential users, check out the "Requirements and Specifications" lecture, especially slides 15-18. Some things you might want to ask a user are what sort of functionality they would expect from your project (without first telling them) to see if maybe you’re missing anything or what features they believe would be most important. You can also show them a mockup of your front-end design and ask them how easy it is for them to figure out how to navigate to a certain feature. You must ask each user at least three questions (but we encourage you to ask more!).

The user feedback report should be a write-up of what you asked these users and what you learned from them.

The report doesn’t need to be longer than a double-spaced page. Please include the name of your project as well as all the names and logins of your group members.

Handin here: Link

Project elevator talks: 3/4, 3/6

Your elevator pitch should be three minutes in length, including set up time. You should describe what your final project is about and what you expect to be working on throughout the semester. Use the elevator pitch to really sell your project to the class and get the audience excited to see your final project at the end of the semester.

Elevator pitches will take place in class. You can find the order of the pitches here. Roughly the first half will present on Mon 3/4, and the second half will present on Wed 3/6. However, we cannot guarantee which day your group will present on, especially those in the middle of the list, so plan on attending both days. We will not be honoring requests for ordering swaps unless there are exceptional circumstances. While we would prefer that all group members be present during the elevator pitch, note that one member being unable to attend will not be considered an exceptional circumstance.

Front-end design presentation: 3/11

You should schedule a meeting to present your initial front-end design to your mentor TA before 3/11.

In your presentation, you should include mockups and designs created for the front-end of your project. You can also include alternate designs for your project. What you present will vary by team/project and we do not require a minimum number of pages mocked up or that your mockups be hi-fi. We will just be checking that you have thought about your front-end and are ready to write it in code.

Project checkpoint 1: 3/18

You do not need to hand in anything or meet with your mentor TA for this checkpoint (though always feel free to reach out to your TA to ask them questions or have them look over your project).

We highly recommend that the first iteration of the front-end of your project be done at this point. This is because the poster-fair is the following week and will require more immediate attention. You should also start thinking about the back-end of your project for the back-end design report due on 4/8.

Poster fair: 3/18, 3/20

Students are expected to be present both days of the poster fair to give feedback to their peers. More details about which groups will present on which day and the location of the fair will be released soon.

What should be on the poster:
Each of the poster’s will vary by what stage each group is at, but in general, we just want to see what your web app will look like. You can choose to display alternate designs for your project, the designs for every page or only the most common ones, etc. The poster fair is mostly for you to get helpful feedback from your peers. Use the poster to show what your website might look like in order to get the appropriate feedback needed to get a better and more final design.

Instructions for printing posters will be released soon.

Back-end report: due 4/8 @ 11:59pm

The back-end design report should be an of the overview of your system design and architecture. In your write-up, include all technologies you will be using and focus on the backend.

The report doesn’t need to be longer than a double-spaced page. Please include the name of your project as well as all the names and logins of your group members.

Handin here: Link

Selective project presentations: 4/15

More details to be released soon.

Project checkpoint 2: 4/19

By now you should have a completed first iteration of your project. This includes connecting the frontend to the backend and making sure pages link to each other as they will in the final product. Feel free to have lorem ipsum text and placeholder images for now.

Client feedback report: due 4/24 @ 11:59pm

You should plan to meet with your client before 4/24 to present the current progress of your project and ask for their feedback. Be prepared to ask them questions about their thoughts towards any design decisions you may have made on your own.

The client feedback report should be a write-up on your client’s feedback on the project thus far. Include your client’s opinions towards the project as well as your own thoughts on working with the client.

The report should be about 1-2 pages double spaced. Please include the name of your project as well as all the names and logins of your group members.

Handin here: Link

Project testing report: due 5/1 @ 11:59pm

The project testing report should be a write-up about the testing that has been done for the project. Include edge cases you had to consider, how you covered all edge cases, how you tested for security, and how you ensured robustness. Mention different testing software you may have utilized as well as how you used unit testing and system testing. Also discuss any issues you may have encountered. As a side note, you are allowed to include content from the individual testing reports that you submitted for lab in your project testing report.

The report should be about 1-2 pages double spaced. Please include the name of your project as well as all the names and logins of your group members.

Handin here: Link

Final project presentations: 5/6, 5/7

Presentation locations and times will be released soon.

You will have 15 minutes to present your final project to Professor Reiss and your classmates. Your presentation should be a walkthrough of your web app, showing off the pages that you created and the functions that you implemented. Be prepared to answer questions regarding technical challenges you encountered, the architecture of your code, design choices, and other aspects of your development process. Make sure that someone in your group brings your final project on a laptop that can be connect to with an HDMI cable so that your project can be projected on the big screen. This presentation will constitute a portion of your grade for the final project.

If you had any concerns or issues about any of your group members that you would like to voice, you can fill out the form here. Your response will remain confidential and will only be seen by those on the course staff responsible for grading your project. Positive feedback about your group members is also welcome!

Final project presentations to TA: 5/6 - 5/12

Additionally, you will have a meeting with your mentor TA that will take place after the final project presentations. This meeting will involve a more in-depth look at the code that you wrote and a thorough exploration of the features of your project. This meeting will also be a component of the final project grade.

Final project handin: due 5/8 @ 11:59pm

Hurray, you made it to the end!

To hand in your final project code, first create an empty directory on a department machine by running cs132_install final_project. Transfer your files over, then run cs132_handin final_project. Before handing in, please test that your code works on a department machine!