Purpose: The purpose the Service Blueprint is to make a blueprint of the enterprise by collecting the most relevant elements.
Core concerns: The Blueprint enables you to collect objects of the different facets in the EDGY language in one diagram.
Templates and model types in the QualiWare platform.
Purpose: The purpose the Service Blueprint is to make a blueprint of the enterprise by collecting the most relevant elements.
Core concerns: The Blueprint enables you to collect objects of the different facets in the EDGY language in one diagram.
Purpose: The purpose the Story Board is illustrate identity and purpose, while verbalizing your mission statement as a story.
Core concerns: An enterprise story is a narrative with our co-creators as protagonists, the enterprise as the setting, the ecosystem as context, and the co-creators’ activities as actions.
The Story Board is a part of the EDGY language created by the Intersection Group.
Purpose: The purpose the Object Map (previously known as “Structure Board”) is to use a single and consistent vocabulary, while consistently using the same entities and relations when designing software solutions (data models, user interfaces)
Core concerns: An object is a tangible or intangible multi-part structure such as a machine, building, application or data. Objects can have behaviour, such as performing automated activities, or support people that are doing activities. Objects consist of parts: objects that combine to form an object of a higher complexity and function.
The Object Map (previously known as Structure Board) is a part of the EDGY language created by the Intersection Group.
More information about EDGY:
Purpose: The purpose the Task Board is when deciding which products to create and market, tasks clarify what these products are for. It can also gain insight and a sense of priority about what matters to customers or other important people.
Core concerns: People have numerous tasks they want to accomplish every day: getting up in the morning, working together with a colleague, visiting a friend or relaxing in the evening. Those tasks are about the outcomes people want to achieve, not the means to get there. Tasks can be seen as a stable expression of people’s needs, motivations and intent.
The Task Board is a part of the EDGY language created by the Intersection Group.
Purpose: The purpose of the Activity Board diagram is modelling what is being done or going on in our enterprise or its ecosystem.
Core concerns: Activities represent something happening that is relevant to our enterprise. This can be something people do, individually and/or collectively (work, entertainment, other ways to spend their time). It can also refer to something happening or going on, events unfolding within our enterprise or outside its boundaries within our ecosystem. They capture the behavior and dynamics of our enterprise over time and enable us to model and map what we do to go about our business and organize ourselves to do so.
The Activity Board is a part of the EDGY language created by the Intersection Group.
The HTMLVisualizerFilter template is used to create customized filter(s) to use in the 3D Visualizer on the web.
Click “Add Templates” to select the templates to be included in the filter.
Click “Add Relation” to insert the relation to be included in the filter.
Once a HTMLVisualizerFilter is created it becomes available in the Explore and Local Explore menu.
The HTMLContextMenu template is for designing context menus for the web.
(relevant from version 10.2, and enhanced in version 10.3)
The symbols available for HTMLContextMenu are:
HTMLContextMenuItem
The graphical part of HTMLContextMenu is only used to define context menus; it is not used for displaying to the user. The HTMLContextMenuItems on the HTMLContextMenu are defining when and where context menus are available to the user.
Example of HTMLContextMenu:
A default context menu can be defined in the HTMLPublisher. The default context menu will be applied to objects of all templates unless specific context menu is defined on the HTMLTemplateDefinition for the template. If the default context menu is left empty then only templates with a context menu defined will get a context menu.
A default context menu defined on the HTMLPublisher:
A template specific context menu is defined on the template definition for that template:
To activate the changes in context menu setup press publish in the HTMLPublisher.
Context menu and Governance Workflow Engine
Objects governed by a GovernanceWorkflow will get an extra context menu item. The item is called Governance and is added as the last item of the context menu. It contains the possible transitions available for the object.
Settings for the HTMLContextMenuItem
(relevant from version 10.2)
HTMLContextMenuItem sample:
Context menu item
List of items to who in the context menu
Menu Image:
Not supported
Role access
General role access for all items in the context menu.
Context menu items
The context menu supports GovernanceStateFeature and HTMLContextMenuItem. Adding a GovernanceStateFeature means adding an action to the context menu. Adding a HTMLContextMenuItem will create a sub menu in the context menu.
Context
Role
Condition
Sample list of context menu items containing one sub menu and several items with conditions set:
Settings tab on HTMLContextMenuItem
The settings defined on this tab will apply to the whole context menu. If a HTMLContextMenuItem is used as a sub menu, then only Visual name is used.
Visual name
Active on
Icon on web
Target
This object is used to describe Service Level Expectations, and contain the following standard propertity fields.
The object can be associated to Goals, and can linked to an IT-Service (Concerns).
This object is used to describe Service Level Agreements (SLAs), and contain the following standard propertity fields.
The SLA can be associated to Goals, and can linked to an IT-Service (Concerns).