| Property | Type | Description |
|---|---|---|
Sitemap Id |
String |
Unique id for each sitemap within a single project. |
Start map |
Line width |
Each project must have exactly one start sitemap (indicated by a bold line width) that must contain the start page. |
{ actors } |
List of Strings |
Optional property to indicate that all links within this sitemap diagram will inherit the actors given. NOTE: This property can not be set on the start sitemap and links from other sitemaps that refers to pages within this sitemap must have set a matching actor property. |
The Sitemap represents a single application window and the boundaries of the site we want to model. The sitemap container can hold any kind of sitemap elements (SME), except popup elements which have their application window and therefore a different sitemap. Their symbol are therefore draw outside of the sitemap symbol, but connected via an associated link with the a link within the sitemap.
In case that the sitemap gets to crowded, a new empty sitemap can be drawn which must have the same Sitemap Id to express that the two sitemaps represents the same application window and therefore representing a single sitemap. By using Reference Connector (see: Reference Contentarea Connector resp. Reference Page Connector) navigation between these two sitemap drawings can be modelled.
To distinguish between different functionality of the site (for instance defined by UML use cases and/or SCRUM user stories) is another good reason to split up sitemaps in serveral sitemap diagrams.