For me, class diagram is absolutely the first step, and deployment is the last step. The order of sequence diagram and component diagram is up to you.
Oh, maybe the assumption and risk list should be done before drawing diagrams. But I'd assume that the updating of assumption and risk list would be go through the whole process.
BTW, I am also working on part II....
You can also think of going for component diagram first , where you get a overall idea of components needed.
then follows the sequence diagram between components and more detailed class diagrams later.
Assumptions and risk list can go side by side as and when there is something to add to them.
But whatever sequence you choose, iterate through all the diagrams multiple times, thats when you will notice more details to add to make diagrams complete.
Joined: Aug 01, 2005
I will go with Prashant idea, it seems to be much suitable for this assignment.
It's up to you actually. The bottom line is all diagrams must be consistency, one of the reasons that why we use many types of diagram is we want to eliminate contradiction, if there is a contradiction that means something is wrong in somewhere.
SCJA 1.0, SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJP 5.0, SCEA 5, SCBCD 5; OCUP - Fundamental, Intermediate and Advanced; IBM Certified Solution Designer - OOAD, vUML 2; SpringSource Certified Spring Professional