This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have already completed Part-I and in a hurry to complete the remaining parts(before August-1).
when going through the forum topics I could see that the assignment would contain some documentation section to explain the NFR, assumptions, Risks and mitigation and other topics.
Can anybody brief about in what format this has to be submitted I suppose it should be in word format. If it is the case then is there any specific sections that this document should contain or is there any standard structure that can be used for documentation of the proposed architecture.
I used SeaMonkey as HTML tool in which you can link to images. It's a nice tool. Make sure that your UML tool can export the PNG/JPEG as you might want to reduce the size of it other wise final deliverable can bloat.