Messages

1

General Board / Re: Showing things from other packages

« on: January 11, 2006, 01:19:16 am »

Hi wargfang !

in order to include different packages, the better way is to use "virtual document" concept of EA !

-  You can insert any packages you wish into the virtual document
-  you can reaarange the order in the document without affecting the order in the model

have a look in the pdf help, chapter 14 or dynamic help
best regards
joel

2

General Board / Re: Help with section Numbering

« on: January 31, 2006, 04:55:40 am »

hi !

in order to succeed with that problem of deeper and depper numbering, the only way i've found is making a new template from the delivered [Basic] template

It's a hard work but this works !

If I create a new template, all numbering are at fixed level and not relatives !!

The [basic] template uses "Heading" styles (with capital 'h') which are not compatible with MS Word in french, so I wrote a word macro to convert all "Heading" styles in "Titre" styles (french name of numbering styles)

Joel MELAN, casino IT

3

General Board / Re: RTF (template)Document Generation+realized ele

« on: January 26, 2006, 01:12:48 am »

hi adamg !

in order to have a UC with its notes, constraints and scenarios, followed by some diagrams in the good order, the best way I've found is to put all the complemnetary diagrams as "child diagrams".

then all the "child diagrams" can be sorted the order you want with the thumbs of the project browser (Ctrl-up arrow or Ctrl-Down arrow)

To force diagrams to become child diagrams of an element of the model (a UC for instance) just drag and drop it from the project browser ON the model element

You' ll got a "+" on left of the model element and tabbed to the right the child diagrams


2/ if your problem is how to create a screen diagram? i need some precisions in order to help you : do you want to have a hard-copy of the layout ogf the screen ?

joel

4

General Board / EA paradigm for create / save produces loss of dat

« on: January 23, 2006, 01:40:42 am »

we' re some here to find that EA paradigm for New : save (properties for instance) produces loss of data ans is quite different from standard Windows's one !

Let's tell about constraints creation for a use case :

1/ let's suppose I've typed 2 constraints and I begin to strike a new one, oops I see a mistake in constraint1 and so I click on it to modify it :
;Dso sorry I've loss my data about the third new constraint !!


Ea has not informed me I was typing new data nor invite me to save it before modifying an older one !  


2/ If I have selected an existing constraint and want something like cloning part of it in a new one, I change it's name, type some long textual description and ... too late !  
I was changing the source constraint, not typing the new one !

another time, no alert message when i press the '"save" button ! asking if i want to modifiy the older or create a new !

any suggestions about a good new paradigm to propose to EA ?

Joel

5

General Board / Re: How do I find the orphans?

« on: January 20, 2006, 12:27:20 am »

Iv' found it after I pressed the "Advanced" button of the Ctrl-F Find function

and then select in the "search list" field "find orphans" !

6

General Board / Re: Building project tree with custom folders

« on: January 23, 2006, 01:54:13 am »

Yes, it's possible to have a multi-project repository on DBMS !

We're using it !

You just have to create a standard tree structure for each elementary project, export it's package in XML  [right-clic a package and Export Model to XMI] ans then re-import it for each new project
BUT with the absolute necessity to TICK the "strip GUID's" option of the Import Model from XMI function !

otherwise you crash all the existing projects !  

some limitations : all customisations are "collective" !
- security can be actived but visibilty is global : each project member can see other projects (even if he can't modify it !)

- alternate images are collective : the images of projectA are in the list of images for projectB

- the same for stereotypes, template for documentation, ...

Joel

7

General Board / Re: ease of typing textual descriptions

« on: January 12, 2006, 06:08:40 am »

I've discovered with EA support that another way of typing a formatted textual desciption is ... the EA concept of "linked documents" !

This way enable us to :
- type a formatted desciption "internal" to EA
- or to link to an "external" RTF documentation

It's accessible by Right-clic > Linked Document or Ctrl-Alt-D on some elements of the model

joel

8

General Board / Re: ease of typing textual descriptions

« on: December 30, 2005, 01:19:15 am »

thanks ben !

the Element browser is quite cool !
in the same time, it's not complete enough !
but it will be a very good base for a future way to implement an editable global view of the textual description of an element :

it just lacks :

• 
  

a supplementary frame with the textual part of the selected tab (like scenario, file, ...)

• 
  

a way to select several or all tabs

• 
  

a way to synchronize edited text with the property part

2/ another good view in order to edit textual description is "scenario" : it is editable and already synchronized !

3/ the "rules" view is also interesting but hasn't got such edition and synchronization functions : what a pity !


in brief, some elements are there : just the need to assemble them !

and the folllowing step is to import from Word and help organize and dispatch each elements of textual description ...

joel

9

General Board / Re: ease of typing textual descriptions

« on: December 21, 2005, 04:48:04 am »

yes, OK for first point : note window could be a space to type on a continuous input !

but for second point, no way to generate the global content of an element by assembling all notes, constraints, scenarios, ...

in order to give a global view of the description of that element !

it's true that RTF generator is like that, but there's a lot of manipulation to go from property windows to seeing and editing global view !!

10

General Board / ease of typing textual descriptions

« on: December 21, 2005, 01:58:43 am »

the logic of striking textual description of use cases for instance) in EA seems to be :
-first structure it in blocks (the post-conditions, invariants, ...)
-then fill in each block

but structuration is sometimes the last activity !
and some people prefer to strike all the textual description in a continuous input, then to spread it among blocks

• 
  

when modifications need to be inserted, it's often done from the RTF documentation and it’s quite uneasy to identify WHERE is the text to modify in the model as textual description is spread among a lot of types (post-condition, invariant) and blocks of text !


in order to help this way of modelling and modifying specifications, would it be possible for instance to generate very simply (without indicating a format and a file like in RTF generator) a global textual description (with no layout, ) of the current element, this global “view” being visible in a supplementary tab of the property windows.

So it would be possible to copy/paste from this global description to a specific constraint or scenario ...

ideally, EA would do it automatically !!  

11

General Board / Re: Class diagram layout

« on: December 29, 2005, 01:58:23 am »

marc !

you've no need to change the style of the DIAGRAM !
just change the type of each LINK you want to be in tree style

Method :
select the Link and right-Clic > Tree Style

Joel

12

Automation Interface, Add-Ins and Tools / Re: Linked Files in RTF Documentation

« on: January 26, 2006, 01:27:30 am »

hi hans-christian

first some concepts of EA are a little bit confusing : the name is not the feature !

- for instance, "linked files" are not "files which can be put in the RTF documentation" !

they just can be mentionned (their name put) in the RTF documentation

- the same for hyperlinks : they can't be inserted in the RTF documentation

If you need to insert some peace of RTF text, explore the "linked document" concept (pretty good till release 6.0 or better 6.1)

it can be an "internal" RTF document, ie a document typed into EA or an external one (for instance a RTF document stored somewhere in your directories)

for external document, you have to "import" them in the internal RTF editor ! not very simple but it works now

you can obtain "linked document" for element of the model only (it doesnt work for packages or diagrams, what a pity !) with right-clic > Linked Document or Ctrl-Alt-D

joel

13

Automation Interface, Add-Ins and Tools / Re: Automation and Document Artifact

« on: January 26, 2006, 01:35:47 am »

hi patrice !

if you don't need programmation, you can use "linked documents" to include some RTF document in a EA generated RTF documentation

just look at my answer on the subject "Linked Files in RTF Documentation "

joel