output from CASSM stylesheet v1.1 created Dec 2003
Notes
Relationships | ||||||||
Name | Actor | Type | Acted_on | Notes | ||||
rel0 | maps_onto | Enacted Guideline | ||||||
rel1 | Enacted Guideline | goal_constraint | Enacted Guideline.Runtime outcome | The goal of the guideline user is to get support from .... | ||||
rel2 | Enacted Guideline.Runtime outcome | goal_constraint | Enacted Guideline.User support outcome | .... the guideline. | ||||
Entities and Attributes | ||||||||
Relns: actor in upright, acted-on in italics. | ||||||||
Name | Create/set | Delete/change | Relns. |
|
Notes | |||
Enacted Guideline | rel1 rel0 |
|
||||||
Plans | fixed | fixed |
|
Guideline users are not interested | ||||
Proforma | fixed | fixed |
|
code (even if easy to display). These are designer's tools. | ||||
Runtime outcome | indirect | easy | rel2 rel1 |
|
Guideline outcomes may look and behave just like the creator expected. | |||
Summary | easy | easy |
|
Summaries of usage tracks may be of use, though even this is doubtful | ||||
Tasks | fixed | fixed |
|
in or know about guideline | ||||
Triggers | fixed | fixed |
|
components, triggers or | ||||
User support outcome | hard | hard | rel2 |
|
But guideline outcomes have to support the guideline user's needs. | |||
Proforma Guideline | rel0 |
|
||||||
Name | fixed | fixed |
|
Names are set by the creator | ||||
Tallis Enactor | bySys | bySys |
|
Guideline users don't want to know about the Enactor .... | ||||
Running state | easy | easy |
|
... but they do want to start and stop it |