• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

How many class diagrams

 
SSK Singh
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Everone,

Greetings,

I have a old FBN assignment since 2003. Now, I'm sort of thinking to work on it..

I have a question about class diagam. How many class diagram would you create in this assignment -- any J2EE project for that matter? Let me clear it a little bit more. Would you have one class digram for domain model, one for business model(business logic), and one for presentation tier(presuming web cleint only)? Or would you rather have just one class diagram showing only important components from all tiers?


Regards,
 
Hong Anderson
Ranch Hand
Posts: 1936
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I didn't work on FBN. But for me, I created only one class diagram, scope of the assignment was quite small.
 
SSK Singh
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Kengkaj,

Let me understand you: did you include all--your domain model classes(persistence tier), business classes(business tier), and presentation tier classes -- in one class digram? How many classes did your diagram have? Did you show JSPs also in your class diagram?

Regards,
 
Hong Anderson
Ranch Hand
Posts: 1936
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
OK, I think we are from different schools.

N-tier is concept/architecture that is higher level than interfaces/classes. For interfaces/classes in a system, I separate them using Layered Architecture.
A layered architecture might have 4 layers: presentation layer (UI), application layer, domain layer, and infrastructure layer.

But we don't need to argue about Tier and Layer in this topic.

For your questions, I included what I thought it needs to be in a class diagram. I didn't include JSPs in class diagram because JSPs are not classes.
 
Juee Doo
Ranch Hand
Posts: 232
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I give classes without attributes and methods, except some import attributes and methods.
for example, a pojo, i just give it a class name, not give the detail of attributes.
It is fine for a archtectrue level doc?
 
Dhruva Mistry
Ranch Hand
Posts: 67
Eclipse IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
SSK Singh wrote:Hello Everone,

Greetings,

I have a old FBN assignment since 2003. Now, I'm sort of thinking to work on it..

I have a question about class diagam. How many class diagram would you create in this assignment -- any J2EE project for that matter? Let me clear it a little bit more. Would you have one class digram for domain model, one for business model(business logic), and one for presentation tier(presuming web cleint only)? Or would you rather have just one class diagram showing only important components from all tiers?


Regards,


um, i have never been to FBN but i used to make all necessary (or you can say necessary ie in terms of the MUST part of some application) class diagrams.
along with these you need to make DFD also!
 
Dhruva Mistry
Ranch Hand
Posts: 67
Eclipse IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
SSK Singh wrote:Thanks Kengkaj,

Let me understand you: did you include all--your domain model classes(persistence tier), business classes(business tier), and presentation tier classes -- in one class digram? How many classes did your diagram have? Did you show JSPs also in your class diagram?

Regards,


if your JSP page has some included classes, you need to make class diagram for all those classes but if it is simple jsp, you should make it as when you will compile it, it will generate a servlet file too....and servlet are just like simple java file that's why!
 
Ashish Garg
Ranch Hand
Posts: 68
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just wanted to add that FBN old assignment is now expired. If you are doing it for your understanding which is great.
 
Scott Soo
Ranch Hand
Posts: 83
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Juee Doo wrote:I give classes without attributes and methods, except some import attributes and methods.
for example, a pojo, i just give it a class name, not give the detail of attributes.
It is fine for a archtectrue level doc?


Hi,

For the SCEA5, it is mentioned to show important and referenced attributes or methods shown in other diagram (eg. Sequence Diagram) in the Class Diagram. Hence, I agreed with Juee. However, from a practical perspective, I would also think it is important to provide the key functionalities (ie. methods) for a class shown in a Class Diagram. This is important to translate and justify why the class is there in the class diagram. The developers can implement in multiple ways. However, if key functionalities are not there, developers may not know the intent of the class being there in the class diagram.

Above are my personal thoughts.

Cheers!!
 
Hong Anderson
Ranch Hand
Posts: 1936
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Don't quite understand your post, why however?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic