start

Home

Getting Started

Task assignments are ready, and information about the tasks is here.

You should all create a Sourceforge ID and send it to gayle@cs.cmu.edu to get permission to edit this wiki.

If you are not on the task list but you are in the class, you should worry.

Most tasks have multiple people assigned. You can work together or independently (I encourage the server-side connection manager group to do one implementation in Java Servelets and one in Python.) I suggest you at least try to divide the task into sub-tasks and divide the work among the team.

For most, the first job will be to have a design session. It is very important to add to the wiki what you are doing:

1. What are the tasks?
2. Who is responsible for each task?
3. What is the API for your component?
4. Write user documentation before implementing. Include examples that show how to initialize, call methods, and what parameters to pass. Others will need this for their implementation.
5. JavaDoc is recommended to help keep documentation consistent with code. It is very important to document the high-level architecture and how things fit together -- do not just document low-level methods and expect the big picture to be evident.

If your task depends on other task designs and you don't see documentation, tell the responsible group what you need to do and what you need to know. Make sure they write it in the wiki. Do not simply ask and write your code without a supporting written API and documentation.

We'll be picking up the pace rapidly and discussing issues in class, so it's (as always) important to attend. When we ask "how does the conductor tell a performer to play louder" and there are no performance interface guys to answer, it will not be good.

The stress test group needs to produce results very rapidly so other orchestras can test their network connections. You should immediately plan a meeting and get started -- I can either attend or talk to someone before the meeting to go over expectations.

Home