• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Clarification on Sequence Diagrams in SCEA II

 
sri scea
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am new to this community. I have cleared part I recently and currently working on part II. Had a few doubts regarding class diagrams & sequence diagrams.

Do we have to come up every method details with exceptions in class diagram?
For sequence diagrams, do we have to show method names in the message call or is it enough if we can show some meaningful message?
for ex: if a method call is something like getOrders(String[] s) then can we show it as "retrieve orders" in the message call.

Kindly clarify.

Thanks
 
Ricardo Ferreira
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Talking about the class diagrams, you are able to create one, without every single detail of attributes or methods. The domain model introduced, should be able to expose your idea from the scenario. If you think that you can came up with a exposable solution, without showing the attributes, so that's ok, you're able to.

The same tip are valid for the sequence diagrams. You can ben generic with messages like 'getCustomer' or being specific as the message: 'findByPrimaryKey(new CustomerPK())'.

Your architecture should be 'understandable'. That's enough !
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic