Patrick Radomski

[Patrick Radomski]

Wait, no, I lied.

Even in a different template it appears to be impossible to get the software to give me a simple table of packages.

The analysts will manually write the tables.

[Patrick Radomski]

I understand. Can’t go breaking the system for an edge case. I would recommend some sort of feedback when the user tries to get the system to do something like this (maybe an entry in the generation log – or a ‘completed but with errors’ message). It was very frustrating trying to figure out if it was against the principles of the system or if I just didn’t have the relationship and stereotype entered correctly.

Unfortunately my client doesn’t care if the software can’t do it (especially when standard EA templates can) – the table needs to be there. So, for those playing along at home, I have created another EADocX template and profile to just create the table and will then get the analysts to copy and paste this into the other generated document.

[Patrick Radomski]

In the attached image, you’ll see the structure of the EA model.

Each document is generated at the ‘Big package’ Level.

Each document structure should be:

Big package heading / description etc
Big package Actors diagram
Table of actors in the diagram (they are from another package)
Big package survey diagram (which is just a diagram with all the child packages in it).

Table of all the packages in the survey diagram (or all the child packages under the ‘big package’. This table is just ‘Name’ and ‘Description’.

Then the rest of the document is a heading of each ‘child package’, the diagram under each one, and a table of all the use cases under each package.

I can get EA docX to do everything EXCEPT for a the table of all the packages in the survey diagram (child packages). It refuses to do this regardless of what I do.

• This reply was modified 12 years, 9 months ago by Patrick Radomski.

[Patrick Radomski]

Hi,

I’m happy to Beta test.

I am running 2010 on windows 7.

Cheers.

[Patrick Radomski]

Across all tables would be perfect.

It might be useful for other users to be able to change it between all the different alignment values (centre, bottom, top etc.).

[Patrick Radomski]

Thanks for that. Changing the order then changing it back worked a treat.

Helpful little feature EA has there.

[Patrick Radomski]

For tip 1 – there are 30 or so ‘big packages’ in the model, but each document is per each big package, so using this method I would need a different stereotype for each big package. Then for each analyst that is generating for their ‘big package’ they would need to re-configure the element report so that it picks up their packages not someone else’s. I would prefer not to go down this route.

Tip 2 – I don’t understand how a table of contents will help me create a table of names and notes.

Is there any reason why it won’t list child packages like this? It has no problem listing other child elements (use cases, objects, requirements) in exactly the same way (a simple table with the name and the description).

[Author]

Posts