Class diagram had 29 classes (of which 4 were abstract and 4 were concrete subclasses of these) and 4 interfaces. This also included command objects and factories. Design patterns were specified as <<stereotypes>> and explained using notes.
In addition, I included a class diagram of the domain objects, somewhat changed from the original one and including multiplicities and use of structural design patterns.
I might have lost some points using design patterns as <<stereotypes>> as that might not be strictly by-the-book-UML - but I don't think so.
Component diagram had 28 components, two for the Agent swing application (view and controller), one for each JSF-page and one for the FacesServlet. The rest is secret Again, using <<stereotypes>> on each component to explain (e.g. <<stateless session bean>> <<JPA>> <<JSF>> )
I used collaboration diagrams instead of sequence diagrams throughout.
Technology - I used Swing for the Agent application, JSF for the web client, EJB 3.0 for the business logic, JPA for data access.
[ December 17, 2007: Message edited by: �dne Brunborg ]