0. Meet with your team from HW5.
1. Look for steps in your use cases where what exactly the user clicks is not spelled out yet. Add at least two statecharts, and at least two activity diagrams, describing dynamic behavior in your system. "At least two" is not meant to be "enough": add as many as you see are needed.
2. Add a public interface (a set of public methods) for each of the classes in your team class diagram. Methods come from use case steps, events in statecharts or activity diagrams, or your knowledge of the application domain.
3. Look for external components your team's use cases depend on. Identify what team is designing them. Go talk to that team and review their public interfaces, give them feedback. For each external component, write a short summary of what methods you plan to call. If you need a functionality and can't identify who will provide it, bring it up with the instructor in class, and write it into your report.