expectation on design review?

This question is directoed to Experienced (Java/J2EE)Archictects and your insights and advice is highly appreciated. Here's the scenario:
I had applied for a job at startup and they have invited me for an interview and also to do a "design review of their current architecture." Although I have done J2EE design and ejb programming, I have not done any design review for companies. I have several questions:
1. What will the company give me for design review?
{I assume, the company will show me their UML diagrams, class diagrams and even sequence diagrams and I will have to analyze the diagram. Is this basically true? I gather for complex architecture, it could be very complex. How long does an average design review take? }
2. Given the fact that I don't have the domain expertise and only Java/J2EE expertise, how do I go about with the analysis? Are there certain standard procedures that experienced J2EE architects would follow? Do I follow the J2EE best practices, J2EE design patterns and Petstore blueprint as a guide?
3. As a part of design review, what am I suppose to deliver? Will making comments and suggestions be enough or do I have to give them UML diagrams etc. ?
4. Given the fact that both the hiring engineering manager and architects of the current design will be at the design review and ultimately make the hiring decision: how do I tactfully make recommendations so that the manager feels that I am bring in valuable insights & expertise without offending the current architects?
5. Are there any good books or articles that I can read to better prepare for the design review?
6. Any words of wisdom or horror stories that I can learn from will also be appreciated.
thanks a bunch!
--kai