How to structure UML for more than 100 entities?

Question

0.00/5 (No votes)

See more:

I am designing a UML for my JAVA program class. It has 50+ attributes and 50+ properties. I have to include the UML in my report in word document. Is there any problem if the diagram gets split into multiple pages?

20+ properties have getters and setters, so it is necessary to include them?

And there are few other classes with which I have to show the relationship, the relationship diagram will be on another page, so on relationship UML do I have to list all the attributes again ? or I can just include the class name in the rectangle?

What I have tried:

I tried creating the UML will all the entities, but it went upto 3 pages. Reducing font size is also not helping.I tried creating the UML will all the entities, but it went upto 3 pages. Reducing font size is also not helping.

Posted 12-Apr-18 18:31pm

Pushpa Raj Bhatta

Updated 12-Apr-18 22:53pm

Add a Solution

Comments

Ziee-M 13-Apr-18 11:06am

First of all, when you talk about UML, you need to precise witch diagram you are using. i guess you are talking about Class diagram here.
Getters and setters are technicaly methods, you dont want to put them but instead you put only your attributes.
Don't forget that the main objective of UML is readabilty, we need to understand your application classes with minimum effort just by reading your diagrams.
In general, you need to create many diagrams to explain your application functionality.
You would probably need to at least design your class diagram, Use Case Diagram and sequence and/or activity diagrams.
UML is not to be taken lightly, it reflect your design/conecption skills. In general, your application should have a few dozens of entity (in an end of study project). so KarstenK answer is very probably correct since you have a 100+ entity.
You should reconsider your hole conception for the project.
For the relationship part, you use the associations, so there is no class that can be created twice in the diagram.
You have to read a lot more about UML before you start.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

KarstenK · Answer 1 · 2018-04-12T22:54:00

This sounds not well. You should break down this amount of a more realistic size. Think about your task again and imagine the data as real objects, so you can better separate the attribute. Ask a teacher or a mate because it is obvious that your solution is poor, bad and maybe wrong!!!

If your solution stays as great I would make a small overview page and a full plan with some papers attached with glue or tape. Some work - but needed ;-)