File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Part 2 -About Class Diagram Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Part 2 -About Class Diagram" Watch "Part 2 -About Class Diagram" New topic

Part 2 -About Class Diagram

Gazo linia

Joined: Nov 17, 2009
Posts: 4
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
Ajith Kallambella

Joined: Mar 17, 2000
Posts: 5782
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.

Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
J J Wright
Ranch Hand

Joined: Jul 02, 2008
Posts: 254
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.

mimi mang
Ranch Hand

Joined: Dec 02, 2009
Posts: 36
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
I agree. Here's the link:
subject: Part 2 -About Class Diagram
It's not a secret anymore!