Creating a Requirement Profile in EA 12

[Geert Bellekens]

Hi Pawel,

I had the same thing. You can solve it by making a toolbox profile and adding your stereotype to it.

Geert

[Pawel Zubkiewicz]

I had the same thing. You can solve it by making a toolbox profile and adding your stereotype to it.

I guess, by the same thing you mean this "stupid" context menu with duplicated element type.

Have you ever tried to put you custom types into existing Toolbox groups?

[Geert Bellekens]

Have you ever tried to put you custom types into existing Toolbox groups?

No, but I've done it the other way around.
I've added standard elements to my custom toolboxes.

You can also override standard toolboxes so that it shows your toolbox iso the standard toolbox.

For example, we have a profile with stereotyped use case, and a stereotyped activity, all using in use case modelling.
So I made a toolbox with my two stereotypes, and furthermore use case, actor, include, boundary,... but I left out the things our modelers are not allowed to use.
Then you can tell your toolbox to replace the standard use case toolbox, which means that if a standard use case diagram is opened my toolbox shows up iso the standard use case toolbox.

See http://sparxsystems.com/enterprise_architect_user_guide/12.1/building_models/overriding_default_toolboxes.html for more info (and note that your MDG has to be Set Active
for the override to work.

Geert

[vodzurk]

Hi Sarah,

Just been reading your post and have been thinking about using the Volere standard with EA over the following 3 weeks for a dissertation project (I'm a full time BA, new to EA, and doing an MSc in my spare time).

So I guess my question is... how much of a nightmare was it to learn to extend EA to be workable with Volere?  Approximately how many hours did you spend getting it working?  (Assuming you weren't forced to give up due to time constraints).

I understand that it's a "totally easy thing to do" for those who know... but being new to EA like yourself, even the simplest of EA tasks are a brick-wall with no peers.