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.
Can anyone who passed SCEA II & III share how to get started?
- From Class Diagram -> Component Diagram -> Sequence Diagram ?
- From Use Case -> Sequence Diagram -> Class Diagram -> Component Diagram?
- From Component Diagram -> Class Diagram -> Sequence Diagram?
= Sequence Diagram =
For Sequence Diagram, should I avoid using Control, Boundary, Entity notation? There are two levels of Sequence Diagram: Analysis Model & Design Model. To my understanding, the Exam wants to us to draw the Design Model of Sequence Diagram. Is it correct?
I think right now everybody is gloating over their SCEA results. Pretty big milestone for most of the people who frequent this board and I think many of them gave this test. I myself have got no experience on Part II so will not be able to respond. Hopefully somebody else will be able to respond to this.
Use iterative methodology and refine with each pass - I prefer class diagram first but you can take use cases and start with sequence diagram. There are many paths to same result - find what you feel comfortable
One suggestion - read the assignment - read again and then sleep over it. Read in morning again and then start working. For sure you don't want to miss any requirement - Satisfying all requirements 100% is the most important thing. Also Sun does not expect a very detailed design - but again that's a comfort level thing.
My question is that I have some Factory classes + Contoller classes, should I show this level of detail in the Class diagram? I have more than 20 classes other than the BDM provided. Am I going to the wrong way? too detailed?
I've read people just have 20-25 classes including BDM. I am little bit confused.
I use my recipe for OOAD with UML. I usually create a coarse sequence diagram form the use cases, then the class diagram, and retrofit the changes to the sequence. Once I think is enough, I assign classes to components (and then to deployment if you want). Hope it helps