This week's book giveaways are in the Scala and Android forums.
We're giving away four copies each of Machine Learning Systems: Designs that scale and Xamarin in Action: Creating native cross-platform mobile apps and have the authors on-line!
See this thread and this one for details.
Win a copy of Machine Learning Systems: Designs that scale this week in the Scala forum
or Xamarin in Action: Creating native cross-platform mobile apps in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Part 2 -About Class Diagram  RSS feed

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
For Part 2 Assignment should we need to include attributes and methods to the class diagram ? Becuase In SCEA -Cade book it is mentioned as "At this point, attributes and operations
have not been added to the classes because that information will be done during the
detailed design. This diagram just shows the basic classes that will be used in the system
to provide some structure and business rules. A detailed class diagram will be created by
the developers during the design of the system
".
 
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would include significant operations that represent the behavior of the class. I have seen many people struggle with this idea of how much detail to show in a class diagram. In my opinion, classes without operations are not terribly useful, because operations are how behavior is implemented. At the least, you should show the operations that are used in the sequence diagram.
 
Ranch Hand
Posts: 254
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How are you going to produce a sequence diagram without methods?

Attributes are different in the sense they are implementation details. Of course, some attributes will be implicit from the associations you model between your classes.
 
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree that the important operations should be in classes diagrams. However, many people said the class diagram should show the business domain model other than other classes. Here I regard the business domain model are those POJO entities. but many key operations should be in other classes such as session beans and business objects. do these session beans belong to domain model? if yes, the class diagram will relate to JavaEE technologies. some people said the class diagram should not relate to any technologies.

I am consued... any help would be appreciated
 
Any sufficiently advanced technology will be used as a cat toy. And this tiny ad contains a very small cat:
Rocket Oven Kickstarter - from the trailboss
https://coderanch.com/t/695773/Rocket-Oven-Kickstarter-trailboss
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!