- I'm on the waiting list. Will I get in?
- Our goal is to accommodate as many as possible. We are hoping to accommodate 240 in Fall'13. Preference will be given to CS seniors & juniors, then EECS upper division and lower division students, then non-EECS students.
- I'm on the waitlist but I see there are still open spots.
- The waitlist is managed by the registrar and by Michael-David Sasson. Our intention is to accommodate everyone. But we can't make specific arrangements for a particular person to be "plucked" from the list at this point, beyond the general preferences above.
- What will the project be like?
- Teams of 6 students will work with a real external customer (generally nonprofits and campus units) to design, plan, develop, test, and deploy a software-as-a-service application, using Ruby on Rails as the implementation medium and Agile/XP as the development methodology. You'll use the same techniques and tools used by today's leading software companies, including Behavior-driven Design, Test-FIrst development, Agile/Extreme Programming, Pair Programming. Most other questions about the project can be answered on the Project page.
- Can I use another language/platform/etc. for the project other than Rails?
- No. It must be based on Rails. Sorry.
- Can I write a mobile phone app instead?
- It's OK to devote a minor fraction of the overall project effort to a mobile client part, but the majority of the focus should be development on the server side. We do not plan to provide software, dev kits, or TA support of any kind for the mobile side, though we can make suggestions.
- How will project groups be assigned?
- You'll choose them yourself, but if you don't choose up a team by the stated deadline, we'll assign them for you.
- Can teams be <6 or >6 students?
- No, unless you have special dispensation, which we're unlikely to grant. Larger teams should split their projects into loosely-coupled chunks each of which is manageable by a smaller team. You'll learn all the service-oriented architecture techniques needed to do this.
- Can projects be proprietary?
- During the course, your instructors, TAs, and even fellow students will need to see the project and parts of its code, and they will not be able to sign NDAs to do so. You will also be expected to use various tools to analyze your code, and many of those tools expect to operate on code that is hosted on a publicly-accessible repository (unless you wish to personally pay to host it somewhere private). After the course, Berkeley rules say that your work is your own and you may do whatever you wish with it.
- A colleague of mine has an idea for a project, or I have an idea for a project.
- Can people not enrolled in CS169 be part of CS169 project teams?
- All project team members must be students registered for credit in the class. You can choose to have others work on the project, but everyone on the team gets the same grade for the project, so you want people who have skin in the game. (That is, "Our non-CS169-student project member screwed up" will not be a valid excuse for problems in the project.)
Have a question? Email the course staff and we can add the answer here.