This is entirely up to you. Keep in mind that the project is intended to be read by someone knowledgable in
J2EE and UML. Therefore, you don't need to explain UML or J2EE to the reader. The assumptions/design notes page is only there to explain things that are not immediately obvious to the reader or justify certain design decisions that may not be cut and dry.
In my case, I included less than a page of design notes and I did just fine. Overall, your design diagrams should be self-explanatory and stand on their own. A large part of this is accomplished by picking good class names. When in doubt have a friend look it over...
i would be submitting in a day or two..still doing some fine tuning...as for any example, i can tell u like "Since web svr and app svr r on diff nodes, it is safe to assume that the front business interface of ejbs should have a remote interface " and this is the foundation for my facade; my facade deals with local interfaces also..