# Test model for verifying the import of UML into MSWord via HTML

Description: | This is the documentation at the Project level; don't know if it turns up on the UC

Actor | Actor_1
Stereotype: | offstage actor
Description: | The actor having selected the case for UC3 can now invoke the process
Subtypes: | Actor_2
Associations:
visibility | participants | roles
public | Use_Case_1 | This association is the interface object (view) to the controler UC1
public | Use_Case_2 |

Actor | Actor_2
Description: | Actor 2 is a subclass of actor one, adding a special case of UC1
Supertypes: | Actor_1
Subtypes: | Actor_3
Associations:
visibility | participants | roles
public | Use_Case_4 | This is the association of the actor2 to the extension UC4

Actor | Actor_3
Description: | Actor three is only here to show a subclass of a subclass
Supertypes: | Actor_2
Associations:
visibility | participants | roles
public | Use_Case_3 | Special Special case A3 acces directly to UC3

Use-Case | Use_Case_1
Description: | This is a branch point where we can include the module of UC2 but optionally shift type to include UC3
Associations:
visibility | participants | roles
public | Actor_1 | This association is the interface object (view) to the controler UC1

Use-Case | Use_Case_2
Stereotype: | process
Description: | Use Case UC2 is 'included' meaning it is always part of UC1
Associations:
visibility | participants | roles
public | Actor_1 |

Use-Case | Use_Case_3
Stereotype: | thread
Description: | UC3 is a variation added to (or replacing parts of) UC1 when required.
Associations:
visibility | participants | roles
public | Actor_3 | Special Special case A3 acces directly to UC3
Suppliers: | package_1

Use-Case | Use_Case_4
Stereotype: | process
Associations:
visibility | participants | roles
public | Actor_2 | This is the association of the actor2 to the extension UC4

Collaboration | Collaboration_1
Description: | The collaboration is not all that clear, but it cannot be attached to an actor or the superclass of any UseCase, although it can be attached to the usecase.
Components: | Use_Case_1, Use_Case_2, Use_Case_3

Package | package_1
Stereotype: | framework
Description: | The package is often a constraint due to legacy or partnership systems
Dependencies: | Use_Case_3