Win a copy of liveProject: Protecting User Data with Spring Security and OAuth2 this week in the Spring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • paul wheaton
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Piet Souris
Bartenders:
  • salvin francis
  • Mikalai Zaikin
  • Himai Minh

Part II - Class diagram - dependecies

 
Ranch Hand
Posts: 142
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I am pretty much done with the first draft of my class diagram. Am giving it a hard second look to see where I can refine it. A couple of questions popped in my head as I was doing this exercise.
1. Do the examiners expect detailed method signatures(for the ones that I show in my classes) or just the names of the methods?
2. Do I need to show dependencies? I feel that the associations are pretty obvious and don't want to mess up the class diagram with more lines and details.

Any insights please, especially from the ones that have cleared the exam???
thanks
Sridhar
 
Sridhar Raman
Ranch Hand
Posts: 142
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Can anyone throw some light on this please?
Most appreciated!
Sridhar-
 
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


1. Do the examiners expect detailed method signatures(for the ones that I show in my classes) or just the names of the methods?


Show everything that is significant - arguments that matter to the method logic. Include elipses (...) to indicate additional but insignificant arguments. But you must show arguments that are important. Consider for example a withdraw method. Clearly Account.withdraw(amount) is more descriptive than Account.withrdraw(...) or Account.withdraw(). The latter versions are open to interpretation which might hurt cause confusion if someone is looking at the sequence diagram.


2. Do I need to show dependencies? I feel that the associations are pretty obvious and don't want to mess up the class diagram with more lines and details.


You can omit derived, inherited and implied relationships. Again put yourself in the evaluator's seat and ask the question - do you understand everything you see, is there ambiguity or opportunities for open interpretation? Do you see anything confusing? If so, you may need to add clarity by showing the compelling associations/dependencies.
Hope that helps,
 
Sridhar Raman
Ranch Hand
Posts: 142
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks, Ajith. It sure helps.
Sridhar-
 
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic