• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Dividing class diagram into 2 parts

 
viv anand
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I am currently doing SCEA Part-2 assignment. My class diagram contains 35 classes and so I am planning to split it into 2 parts.
Part-1 will contain all the JSPs, Controllers and Managers (14 in total)
Part-2 will contain all the DAOs and Entitys (21 in total).
Am I doing the right thing or should I keep one large class diagram? If divided into 2 parts, will it be difficult for the reviewer to get the entire view of the class diagram? I am giving some notes about the the class diagram.Where will I put those points(in part-1 or part-2)? Please suggest and share your views or experience.

 
Rahul Mishra
Ranch Hand
Posts: 211
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Splitting your class diagram often makes it confusing especially if you split it by layer and not by feature..


if i did end up splitting the class diagram (although at first attempt i would try to avoid it) , i would perhaps switch it by feature...so a bunch of jsps, controllers, services,...etc..which serve a common feature..end up in related diagrams..

splitting it by layer..would require the examiner to go through multiple diagrams to understand each feature of your solution...

But before you do something..hear from others as well..
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35269
383
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Rahul,
I disagree. Splitting into back end and front end seems perfectly logical to me. This is the approach I took in my exam.
 
Claudiu Dumitrescu
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I also will go for splitting by layer (behind Jeanne confirmation that would be OK).

Trying to split by feature will end, in my case, to an equivalent mess as I'll end up using a large amount of the business layer classes for each of the features. Another unwanted consequence will be duplication of classes on each diagram.

 
Rajan Choudhary
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Claudiu Dumitrescu wrote:I also will go for splitting by layer (behind Jeanne confirmation that would be OK).

Trying to split by feature will end, in my case, to an equivalent mess as I'll end up using a large amount of the business layer classes for each of the features. Another unwanted consequence will be duplication of classes on each diagram.



fully Agree ...
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic