• 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
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
  • paul wheaton
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Henry Wong
Saloon Keepers:
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Tim Moores
  • Mikalai Zaikin
Bartenders:
  • Frits Walraven

Class Diagram Detail

 
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ranchers ...
How detail the class diagram you draw for the assignment part II ? only in concept level or specification level ?
Do you put some "basics" operations and attribute in the class (without going to much in implementation detail) ? since I read at Cade's book, he doesn't put any operation and additional attributes at all ..
Thank you for the help
[ April 06, 2003: Message edited by: Alex John ]
 
Ranch Hand
Posts: 51
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I take the specification perspective. The given domain model is in my opinion the class diagram in the conceptual perspective.
 
Greenhorn
Posts: 25
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm adhering to the deliverables statement: "It is not necessary to provide each method name and attribute in the class." While I'm still working on my class diagram, I have not as yet found it important to communicate that level of detail. I'll leave it to my sequence diagrams to elaborate on operations. I can think of one situation where I might decide to depart from the BDM by treating one of its entities as a simple attribute. If I do, I'll document it in my assumptions or maybe as note in my class diagram.
 
There are 29 Knuts in one Sickle, and 17 Sickles make up a Galleon. 42 tiny ads in a knut:
Gift giving made easy with the permaculture playing cards
https://coderanch.com/t/777758/Gift-giving-easy-permaculture-playing
reply
    Bookmark Topic Watch Topic
  • New Topic