Predefined Tagged Values for Requirements

[Richard Peaker]

Hi,

I'm investigating EA for the management of our Companies requirements, and from what I've read it looks really great. I'm doing some testing and I just cannot figure out how to create Predefined Tagged Values and then get them to be applied to all future Requirements elements.

I've read the documentation, and I think I can create new Tagged Value Types using the Settings -> UML Types -> Tagged Value Types tab.

I can also see the process of setting a Requirements Element to be in a Model Template (I don't want to go into Profiles yet, walk before I try to run!).

However, how to do I get the Tagged Value Types I've created to be seen in the Requirements Element I want to act as the template element for all future requirements?

I'm obviously missing a crucial step, but I can't figure it out. I'd be grateful for any help as without this I can't customise the fields and tags to meet our requirements formats.

Many thanks,

Rich.

 

[qwerty]

You should consider MDG. It is possible to create a profile which will add custom requirements that are adorned with any tags you like.

q.

[philchudley]

For the momment, try the following

1. Create diagram and on this create a requirement element
2. Add your desired tagged values to this requirement
3. To create a new requirement including this tagged values, select the requirement on the diagram, hold Ctrl down on the keyboard and drag down the diagram.
4. In the dialog, enter the new name for the requirement
5. Now you can repeat this proocess by selecting both requirements and Ctrl drag and you will create two requirements.
6. Repeat to create 4, 8, 16, 32 etc

However, in the long run do consider creating a Profile and MDG as querty has suggested

Cheers

Phil

[Robert Sheridan]

Creating and using profiles is not as intimidating as it sounds.  I use profiles extensively for creating custom requirement elements with tags, it is especially useful if you are importing requirements which have additional data to that availble in the standard EA fields.

The other reason to use profiles is that it is more reliable than manually adding tags to requirement elements as and when needed, especially if people who are new to EA are creating the requirments

[dzyndzla]

Hello everyone, I've decided to reply to this topic instead of adding another one.

Despite the fact that Sparx released 13th version of EA, adding tagged values to the requirement model seems to be as complicated as it was in 2012. In other words, I have the same problem as the topic's author and I was wondering if something has changed in this case since 2012? I would like to use requirement model to manage my requirements and I've defined tagged values (UML Types -> Tagged Value Types). However, I can't force EA to include all these tagged values to each new requirement I create. Could anyone provide a tip how to do that? Thanks and regards ;-)

[qwerty]

I guess the answer is still the same: create a MDG.

q.

[Geert Bellekens]

It may seem complicated and difficult at first, but it's not all that bad.

And it has gotten a lot better compared to 2012. There is now the UML profile helper that helps you build the stereotypes.
So no more magic strings to remember.

Geert

[Nizam]

Its really worth  the efforts to get the MDG defined using a external consultant. This is the first step in any of our EA client roll-outs . Be it requirements or application architecture or data modeling.

However a simpler option will be using Template Packages too.

[Uffe]

Hello,


Well I'm with the others on this one. EA consultants, unite!

A lighter-weight approach is to create just a profile and import that back into the project (an MDG Technology contains profiles, as well as diagram types with customized toolboxes, document templates, etc). However, this isn't much help since it's the profile that's the hurdle really -- creating a simple MDG Technology with just one profile in it is very easy even the first time out, but building the profile takes a little more effort.

As Geert pointed out, that effort has been reduced since 2012, although it still isn't zero. In EA, profiles are modelled according to a specific set of rules, then exported as XML (NB: not regular XMI, there's a specific "save as profile" function). This takes a little getting used to, but for a simple profile with just a couple of tagged values to requirements, it's less than a day's job once you get up to speed.

HTH,


/Uffe

[Graham_Moir]

However a simpler option will be using Template Packages too.

In the short term this is likely to be the fastest option.  Configure your requirement element the way you want, then place it on a diagram in the template package to define it as a template element.  EA will then use that template element as the basis for creating other elements of that type. 

[Nabil]

Hello Richard,

I found this in Sparx Community to define complex toolbox https://www.sparxsystems.com.au/downloads/whitepapers/enterprise_architecture_framework_design.pdf very helpful when I started in 2012. This one is outdated now as it was documented in 2009. What you are looking for is a simple solution this one will help.

Also refer this page http://www.sparxsystems.com/enterprise_architect_user_guide/13.5/modeling_tools/predefinedtaggedvaluetypes.htmlfor different types of tagged values

Best Regards,
Nabil