Thanks for diagram tips. I like to see candidates who do not have attributes or methods in their class diagrams. Did you show navigation and role names? For component, did you base it on Cade?
Did you write about your architecture and design in general to elaborate on it? It seems like a lot of people do even though it's not "officially" required.
Also - how many pages were you assumptions?
Do I need to add detailed level design of the framework with all the Actions and Command patterns ?
-Also same applies for my component diagram .. Its bloating and becoming really difficult to keep clean keeping to the guidelines of agilemodeling.
Did u run into any such issues and if so what was your work around that ?
Your assumption document gives me some hope. I had read from previous posts and have gradually made my doc into a architecture document sorts is that all right ?