Book a Demo

Author Topic: Element in Template Folder not used  (Read 4059 times)

Meik

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Element in Template Folder not used
« on: December 03, 2010, 01:58:19 am »
Hi,

I have placed the elements "Requirement", "Issue" and "Change" in a package. This package I have defined as my "Template Package". I have enriched all elements in this template with specific tagged values.

After it has been working for all elements I haveno the challenge that the "Issue" - element does not pull the information from its template, but the "Requirements"-Element does.

Does anyone has an idea?

Meik

P.S.: The Project is set up at an Oacle 11g database.

Meik

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Re: Element in Template Folder not used
« Reply #1 on: December 03, 2010, 02:46:58 am »
Is solved.  ;D But the system behaviour seams not very consistent here. I guess it interprets the "type" of an issue as a stereotype. And if this one is set at the template issue element it will not be considered for newly created issue objects.

Meik

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Element in Template Folder not used
« Reply #2 on: December 03, 2010, 07:33:28 pm »
Meik,

So do you mean that an Issue in the template folder without stereotype works fine as basis of new Issues?

Geert

Meik

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Re: Element in Template Folder not used
« Reply #3 on: December 03, 2010, 08:40:15 pm »
Geert,

I mean that the issue in the template folder without a "Type" like "functional" works fine as a basis for a new issue.
In the documentation it is stated that if the element in the template folder has a stereotype assigned, this template element will not be used as a basis.

What is irritating me now is the system behaviour concering the attribute "Type" of an issue. This attribute is obviously not a stereotype but treated as one in this context.

Meik

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Element in Template Folder not used
« Reply #4 on: December 03, 2010, 08:52:29 pm »
Actually, EA works consistent (in this instance)
The "Type" you see in the the custom properties dialog is translated into a UML stereotype underneath.
If EA were to behave differently I would be annoyed.

Geert

Fred Bevan

  • EA User
  • **
  • Posts: 46
  • Karma: +0/-0
    • View Profile
Re: Element in Template Folder not used
« Reply #5 on: December 04, 2010, 08:02:34 am »
I tend to agree with Meik on this one and find the implementation of stereotypes for requirements a bit inconsistent from that of other element types.

In the requirement element’s Properties dialog, the field is called Type instead of stereotype and there is no button beside it to select from stereotypes filtered by profile. In addition, the requirement “types” can be specified in the General Types dialog (off the Settings menu).

These inconsistencies do make for some confusion.

Fred