Identify conceptual classes, associations and attributes within your project domain. The diagram must use proper UML notation for a domain model diagram.

Domain model is good. You don't need to add in attribute types.

"Bob, how fresh is your limb? I think mine expired last Monday and its starting to stink!" :-)

A complete set of the numbered FURPS+ requirements for your project. The functional requirement list must include requirements drawn out of the use cases. All requirements should be prioritized using a ranking system such as MoSCoW.

Your requirements are good. Are there any more?

SSDs for the most important (or most complex) use cases in the project. Proper identification and naming of system events, as well as correct UML notation is required.

Don't show multiple systems within a single SSD. The point of the SSD is to focus on the interaction of the actor and the system that the user is interacting with. Any internal logic used by that system should be hidden under the 'black box theory'. If the user can't see it in the use case than it shouldn't appear in the SSD.

80% of all known use cases must be written out in detail using the fully dressed format, as discussed in class.

Use cases are good.

UC05: FireHeadMissile - this is a good use case. Very detailed in how the user interface will react to the user input.