Assigned Again: Feb 15, 2005
Due: Feb 24, 2005
Note: Please be sure to write all team member names on your assignment.
In this assignment your team needs to do a lot more design, including exploratory bottom-up design.
Design details get added after last assignment's preliminary design. You need to work out how everything is going to work. This often includes the addition of StateCharts and/or Collaboration Diagrams. It often includes substantially fixing or revising work done in the last homework, adding new classes, adding or defining associations, and adding concrete semantic detail to their descriptions. You should certainly think about how to present your design document in an easily readable and printable format, and that means both physically integrating the diagrams with the text prose, and making the connections between the two easy to follow.
Part of this homework should include a (bottom up) consideration of "components" -- are there pieces you can use that were developed elsewhere? Are there pieces of your design that can be developed to be repluggable, to improve portability or allow extension or customization? Your team needs to submit an HTML or OpenOffice document that identifies the likely mechanisms that you will need to use, and the explanatory rationale behind why you identified each piece or mechanism. Finally, you must also include a section that identifies major risks to your project. Describe the risk, give the reason(s) your team feels it is a major risk, and offer potential things your team can do to alleviate or minimize the risk.
If you are relying on off-the-shelf systems, you should document how you might be using their services for your project.