Search form

You are here

Capstone Computing Project

We will be using the github wiki, issues, and milestones as a way of communicating, like software teams do. Specifically:

All your design, documentation, and all other documents will be placed on the wiki

I will create a wiki page called something like "Vidal Meeting Notes" under which I will add notes from our meetings, things that are going right or wrong with your project, my expectations, etc. Please read this soon (a day) after our meeting

I will also add Issues. Issues are things that you must do (not all the things that you must do are in Issues, just the ones that I feel you need reminding of). Once you have fixed the issue, you will close it.

I recommend you add your own issues, and assign them to your team members. This is an easy way to make sure everyone knows what to do, and knows what everyone is doing.

If you have a question for me, or want to discuss something about your project, you can create an issue, give it the label question, and assign it to me. We can then have a conversation under that issue and it will be saved and available for all team members to see. You could also email me, or IM, or drop by if you want, but those won't be saved in your github.

I have just sent you each and email (google calendar event invites) with your meetings with me. If you did not get your email, you can just look at my calendar for your team's meeting time.

There are two groups that have not yet filled out their preferences. They are University-101 Interactive Textbook and HumpDay-Decode. Please send in your preferences ASAP. Make sure you don't pick a spot that has already been claimed.

By now you should know what platform you will be using, so it is time to start learning about it: download the software, go over the tutorials, implement your 'Hello World!' in the new platform, and read about the more advanced features of the platform that you will need. So, now is a great time to work on your Milestone 3: Research.

Our in-class exercise was to re-design the way a student learns about and chooses classes for the next semester, improving on this mess.

Some of you were unable to stray away too far from the way it is currently being done. This is a common problem: once we see one way of doing it, it is hard to imagine other, sometimes much better, ways of doing the same thing.

Some of you realized that a way to improve this is for the program to use more information about the student: what classes he has taken, his major, etc. This, of course, would require the student to log in. But, even with all this information it is still not clear how to actually make the interface easy to use. Below are some of the more creative solutions provided by you:

Remember that, as part of M1 you have to select a github project name (aka: codename) for your project. Then, email me your github project name along with the github usernames of all the people in your team. I will create a private github repo for your team and give it to you.

Contact your client and setup a meeting with them for next week (Sept 9--13), at the latest.