*
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Part 2: should class diagram reflect non-business domain areas 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: should class diagram reflect non-business domain areas" Watch "Part 2: should class diagram reflect non-business domain areas" New topic
Author

Part 2: should class diagram reflect non-business domain areas

sriram ramanathan
Greenhorn

Joined: Jun 26, 2002
Posts: 12
Hi
Should the class diagram for part 2 also reflect the classes that do not map
to the business domain. e.g Session Beans, Service Locator, MVC classes etc.
Further, does the class diagram for business domain need to indicate actual
implementation classes(like extends javax.ejb.EntityBean) .
[ April 01, 2004: Message edited by: sriram ]
Ajith Kallambella
Sheriff

Joined: Mar 17, 2000
Posts: 5782
Thanks for joining JavaRanch.
Unfortunately your name violates our naming policy. Please take a quick look at the rules and edit your profile accordingly.
Thank you!


Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
Ajith Kallambella
Sheriff

Joined: Mar 17, 2000
Posts: 5782

Should the class diagram for part 2 also reflect the classes that do not map
to the business domain. e.g Session Beans, Service Locator, MVC classes etc.

You may omit framework components such as Service Locator, MVC implementation etc in the class diagram and show them in sequence/component diagram. However, I do not think Session Beans can be treated the same way. Session Beans normally model business processes and therefore correlates with domain concepts. So don't omit Session Beans.

Further, does the class diagram for business domain need to indicate actual
implementation classes(like extends javax.ejb.EntityBean) .

Yes, class diagrams should not only reflect your analysis of the domain model, but also refer to certain implementation choices - session bean, entity bean, POJO, helpers etc. There are two ways you can represent the implementation specific details. You can include J2EE specific classes in your class diagram, or you can use UML stereotypes. The former option tends to clutter the diagram.
Hope that helps,
sriram ramanathan
Greenhorn

Joined: Jun 26, 2002
Posts: 12
Originally posted by Ajith Kallambella:

Yes, class diagrams should not only reflect your analysis of the domain model, but also refer to certain implementation choices - session bean, entity bean, POJO, helpers etc. There are two ways you can represent the implementation specific details. You can include J2EE specific classes in your class diagram, or you can use UML stereotypes. The former option tends to clutter the diagram.
Hope that helps,

Thanks!! That is useful information.
[ April 02, 2004: Message edited by: sriram ]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Part 2: should class diagram reflect non-business domain areas
 
Similar Threads
Class Diagram
Class Diagram and Component Diagram
Anybody working on Big Smokes Cigar Shop assignment
Passed PartII-III with 100%
Dreamcar assignment for Part II