Author Topic: Prolaborate Lifecycle Configuration with ArchiMate stereotypes  (Read 23863 times)

ea0522

  • EA User
  • **
  • Posts: 134
  • Karma: +5/-0
    • View Profile
Prolaborate Lifecycle Configuration with ArchiMate stereotypes
« on: February 15, 2024, 09:25:29 pm »
Prolaborate has a promising Lifecycle feature (see https://prolaborate.sparxsystems.com/resources/v5/documentation/lifecycle-roadmap).
In that documentation is mentioned as a prerequisite that pre-defined date type tagged values must be included for the required stereotype when defining the modeling language.

Now I have a number of ArchiMate 3.1 WorkPackages containing the information on the projects we are working on.
And I would like to use those default stereotypes for showing a Lifecycle Roadmap.
For that I have defined some date type defined tagged values assigned to the elements but they are not recognised when defining the Lifecycle within Prolaborate.

Is it really necessary to define a custom stereotype for using the Lifecycle feature?

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1351
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
Re: Prolaborate Lifecycle Configuration with ArchiMate stereotypes
« Reply #1 on: March 08, 2024, 12:12:07 am »
I tried the Lifecycle roadmap which I'm confident will be useful for a number of Prolaborate owners.
I reported the same concern to Prolaborate support and I understand it has been identified as a future enhancement.
Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


ea0522

  • EA User
  • **
  • Posts: 134
  • Karma: +5/-0
    • View Profile
Re: Prolaborate Lifecycle Configuration with ArchiMate stereotypes
« Reply #2 on: March 11, 2024, 05:54:17 pm »
Thanks Guillaume for your comments and action taken.
In a later test, it looked like the enum defined Tagged Values are only available when the enumeration values are numerical digits.
Does this sound familiar?

sjf

  • EA User
  • **
  • Posts: 25
  • Karma: +1/-0
    • View Profile
Re: Prolaborate Lifecycle Configuration with ArchiMate stereotypes
« Reply #3 on: July 11, 2024, 11:23:02 pm »
I found the same issue, the recommended approach from an EA perspective is to use a dataType with the notes as Type=Date; This works find in EA, however it does not work in Prolaborate, the recommended approach is to use the EA legacy mechanism of creating a tagged value type with the same name as your tagged value and add Type=Date;
 to the detail of the tagged value. This off course means that you have to create lots of tagged value types - one for each unique tagged value name in your MDG.

zee9x9

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Prolaborate Lifecycle Configuration with ArchiMate stereotypes
« Reply #4 on: July 25, 2024, 07:50:15 pm »
Could you please elaborate more on this topic, as I have used the same approach but it I was not able to produce any results.

Nabil

  • EA User
  • **
  • Posts: 147
  • Karma: +5/-2
    • View Profile
    • View My LinkedIn Profile Here
Re: Prolaborate Lifecycle Configuration with ArchiMate stereotypes
« Reply #5 on: August 05, 2024, 07:38:25 pm »
I found the same issue, the recommended approach from an EA perspective is to use a dataType with the notes as Type=Date; This works find in EA, however it does not work in Prolaborate, the recommended approach is to use the EA legacy mechanism of creating a tagged value type with the same name as your tagged value and add Type=Date;
 to the detail of the tagged value. This off course means that you have to create lots of tagged value types - one for each unique tagged value name in your MDG.

Thank you for your request. The enhancement you requested will be delivered in Prolaborate 5.4. For more details on this topic, please send an email to [email protected].
Nabil