Big class diagram, documentation and more question

[hoerb]

hi,

i have downloaded the ea 4.5 for evaluation.  i have made a big class diagram from a source code with the reverse engineering feature. the result is about 24 pages.
i have inserted notes and so on. now i want to create a document. i works well, but the class diagram  will not be shown in the document. it doesn't matter if it is rtf or html.

how can i get the large class diagram into a document !!!


three more questions:

if i delete a member variable in a header file in the source code and make an "Synchronize Model" the variable in the 'box' is deleted, but not the link to the corresponding class

i have an template class. ea takes it, but there are no links form the classes which uses the template. is this a bug ??

is it possible to geht the langueage of the documentaion in german ??

[Martin Terreni]

if i delete a member variable in a header file in the source code and make an "Synchronize Model" the variable in the 'box' is deleted, but not the link to the corresponding class

AFAIK it is a known that EA doesnt delete this links.

i have an template class. ea takes it, but there are no links form the classes which uses the template. is this a bug ??

I'm not sure it is an EA problem, but more like a UML problem. I dont think there is a common way to model such a thing in UML, so not so easy to implement it either.

[Martin Terreni]

I tried to document a diagram with more then 500 clases (+enums and structs) by "diagram only" option and it worked fine.

[hoerb]

hi,

i have made only a use case view with a class diagramm. in this diagramm i "imported" the code. if i make a  "diagrams only" i can create a .rtf file. if i open this file with wordpad or openoffice or winword i got this result:


Diagram:  


Diagram: Use Case Model


Diagram: Business Process Model



i can't see any pic of my class diagram.  i have the ea 4.5 downloaded from the internet. are there any restriction on this version

bye
hoerb

[Martin Terreni]

you're right
it opens only with MSword

[hoerb]

i tried it with an small ( 2 classes) examples and it woks. i geht a picture under the "diagram" text.

but if i tried it with my big one (about 24 pages from the reverse engineering process) i got nothing under the "diagram" text

is this a limitation of the unregistered trial version

[Martin Terreni]

no it didnt work with large diagram for me either.

[hoerb]

hmm, now i'm a little bit confused.

youd wrote in an answer above:

"I tried to document a diagram with more then 500 clases (+enums and structs) by "diagram only" option and it worked fine."


and now you can not create a diagram from a lot of pages.

now you see, why i'm a confuesd

[Martin Terreni]

only in MSword

[hoerb]

hmmm ...... please don't think i wanna kidding you but now i don't understand anything.


what i must do is:

to create a document from the class diagram (takes 24 pages in ea) and send it to a customer

Is this possible with ea in the trail version and if yes, how it works !!

[Martin Terreni]

AFAIK - yes.
the same as you did, but open it with MSWORD
any way you can try HTML docs. it works fine.
another option is for your client to d/l EA Lite.
In this EA viewer he can see all your project.

[hoerb]

i tried it from the beginning and it now works ..............  but my old project seems to be corrupt and i think i don't can "repair" it.  

again and again you will find things you will not understand :-)


thanks for all

[Tjerk]

I think that Martin is talking about 24 diagrams A4 size, while you are talking about 1 diagram of 24 A4 (or letter ). Diagrams larger than the output pagesize are made smaller to fit your page. A diagram of 24 times a pagesize becomes unusable. You'll have to copy - paste parts of your diagram to new diagrams.

[wciesiel]

Hi there,

Why are you using such enormous class diagrams? They are useless because of their complexity: difficult to find anything, hard to navigate, even harder to understand...

Use some of the UML (and great EA feats utilising UML ideas) to divide up that diagram into somthing that HAS SENSE. Model each package in its own diagram, create some 'colaborative' class diagrams to show classes involved in some subsytem but coming from different packages. IMHO - creating class diagram with 500 classes is counter-productive - it may only LOOK professional but what's the advantage of such diagram?

Regards,
Wojtek

[Martin Terreni]

Use some of the UML (and great EA feats utilising UML ideas) to divide up that diagram into somthing that HAS SENSE. Model each package in its own diagram, create some 'colaborative' class diagrams to show classes involved in some subsytem but coming from different packages.

I'm a consultant , that's what I'm paid for.

Why are you using such enormous class diagrams?

to do my job I have to, some times , reverse engineer old code to check it's architecture - then you might get to see things like that (or if your programing widows )