Best Way to Record Days Of Week in Tags

[CraigCullen]

Hi,
I am modelling some Archimate application interfaces (scheduled scripts) and would like to capture the days of the week that each script runs.  Presently I capture these in a CheckList, but this is insufficient for my needs because if I only select Monday to Friday then it simply shows as "Incomplete" in documentation, due to the fact that it thinks I'm trying to complete a full task checklist but Saturday & Sunday haven't been "checked off" yet.
Actually, there is a way that I have found to make the contents of the CheckList display in a report, but this is not what I'm after as it requires the report to be in a format that I can't easily copy to Excel and re-order by script run day / time.
Does anybody have any good ideas for how to do this without having to resort to having 7 tags against each script with a Yes/No for each day?
Thanks.

[Glassboy]

Well I'd think that the trigger is an application event which triggers an application function or process which is assigned to an application component which includes an application interface (compose / aggregate).

If you modeled the structure and behavior separately and didn't use tagged values (which are an afterthought in Archimate anyway) you could just include the application event in your report rather than mucking about trying to make up for the lack of enumerations in the notation.

[Uffe]

Hi Craig,

Here's an alternative.

1) Create a class stereotype «dow» or similar for representing days of the week.
    You want to keep this stereotype name short if possible.

2) Create a RefGUIDList tag type named ScheduledDays:
Type=RefGUIDList;
Values=Class;
Stereotypes=dow;

3) Create seven «dow» classes named Th, Tu, etc. Keep these names short as well.

In the script elements, all you then need to do is add the ScheduledDays tag and select the relevant days.

The reason for keeping the names short is the limited space in the tagged value's text field in the GUI; the stereotype also gets repeated for each list entry.

I'm not entirely sure how this type of tagged values plays in every scenario. The value stored is actually the GUIDs of the selected elements, but I think you can include them in CSV import/exports, and get the right values (selected class names) out in documents as well (might need a fragment or two). They certainly render correctly in diagrams.

HTH,


/Uffe