I\'m interested in learning how to design/plan for web application development, in a multiple developer team scenario.
Assuming the role of \"Project Manager/Lead\": >
All the Use Cases must be well detailed, continued cooperation from the customer will always be a plus, still it could sprout unforeseen cases.
If developing interaction among different servers that will poll/push messages at different times you will be needing Sequence Diagrams for sure.
Avoid overdesigning it, in Class Diagrams unneeded classes tend to mushroom, cut them down, use more methods, keep track of what environment each class will really end up running (some will run server side, some client side - javascript - some will be scheduled jobs and run on the real server, some wil be cgi (or module) encapsuled by he webserver and run on demand, some will interface with the database.
Define the boundaries, make them clear. Server side/client side/database work are different beasts and may take different times and people.