Capstone Computing Project

Final Demo Times

The final demo will be on Wednesday April 29, 8:30am in Amoco Hall. Everyone has a maximum of 10 minutes. Please be ready before your turn. Feel free to invite your client and anyone else you want to attend. The event is open to the public.

The presentation times are (as always, we might be running a bit earlier/later depending on the Demo Gods whims. Tip: offers of Bitcoin appease them):

Time Group
8:30 CockyReaders
8:40 IArch
8:50 MSN
9:00 CampaignApp
9:10 USCConnect
9:20 ADAUSC
9:30 driftNode
9:40 DD-USC
9:50 EST
10:00 QRECT
10:10 CourseManager
10:20 AdvisementCEC
10:30 Apollo16
10:40 ClassTrack
10:50 PetDetector
11:00 leader-assess
11:10 Krit
11:20 ErlangRouters
11:30 AAVRAD
11:40 FIGS
11:50 VWRoom

Testing Milestone Group Assignments

The testing assignments are below. Group n will test the app of group n + 1, the last one tests the first one. See the quality assurance milestone for details on what you need to do. I have just given you read permission to their repo, which should let you add Issues to their repo. Please, do not start testing until April 1.

  1. IArch
  2. MSN
  3. CampaignApp
  4. USCConnect
  5. ADAUSC
  6. DD-USC
  7. EST
  8. QRECT
  9. CourseManager
  10. AdvisementCEC
  11. Apollo16
  12. ClassTrack
  13. leader-assess
  14. Krit
  15. ErlangRouters
  16. AAVRAD
  17. FIGS
  18. CockyReaders
  19. VWRoom

The two hardware projects, driftNode and PetDetector, will be tested by their respective faculty advisors.

What You Are Working On Now

I expect all teams to be working already on their Milestones for this semester. By the time we first meet you will have had between 1 and 3 weeks of work, depending on when we first meet. Thus, I will expect certain things to be done already:

  1. New team members should be able to pull, build, and push to the repo using their own laptops. Bring them to the meeting so you can demo this.
  2. You will have already chosen and installed a Unit testing framework, as per the testing milestone.
  3. You have posted lots of new issues, one for each new feature. Some are closed because you have implemented them. You have been coding.
  4. Everyone's personal logs are up to date.
  5. Demo, every meeting.

I expect the final product for this class to be a polished (looks professional), solid (never crashes, no workarounds), and complete (all the features, and them some) piece of software.

Meeting Times Poll

By now you should have received an email with the email address of all the members in your team, including any new members. Meet with your team and decide what times you can meet with me.

Each group, please submit the form below to let me know ALL the times your team can meet, by Wednesday, Jan 14.

Group Meetings Only, No Lectures

Just like CSCE 490, in 492 each group will meet with me in my office for our bi-weekly meeting. There are no lectures. I will be posting the survey for preferred meeting times right here, so, come back.

If you are New to Capstone: If you were not in 490 then I will be assigning you to a group. You will have a lot of catching the first month (this is why we recommend you take 490 first). Expect an email from me after the start of classes. In the meantime, learn git and github.

Please, email me your github username by Monday Jan 12 @midnight.

Remember, your grade depends on your git commit log.

Team Members Assessment

Read the team members' assessment rubric.

Fill out and submit the form below once for every team member, including yourself. That is, you will have to come back to this page and re-submit the form with your review of each team member. I will be the only one who reads these, no student will read them. Remember to also submit one review of yourself. Deadline is Wednesday, December 10 at noon.

The form is now closed.

Prototype Demo and Presentation Time

I have updated the Presentation milestone. It will be Saturday, December 6, 8am to noon in Amoco Hall. See the milestone for details.

Unrelated to that, checkout interviewcake.com. I signed up for their weekly questions. They are good. And, no, I don't know the answers right away. It takes me hours to figure out some of them, which is why Google won't hire me.

Pages

Subscribe to Capstone News