Templates | QualiWare Center of Excellence

PropertySheet

QualiWare 10.10 introduces a new propertysheet template, that enables to get a spreadsheet view of:

default properties for an object
a set of properties for an object for multiple:
- Configurations
- Languages
- Revisions

This enables the user to easily explore and modify properties of different variants of the same objects.

The behavior of the propertysheet can be selected from the list under code behaviour.

On the Settings tab it is possible to right click in the window and “Add standard parameters”.

As a part of these settings, it is possible to specify the behavior of the spreadsheet.

In the setting you can specify how many colums should be included in the spreadsheet. If more revisions are available the sheet will show the following coloum:

Property
First revision
Latest X revisions (e.g in the case of 5, the 3 latest will be shown, along the first revision 0).

Business Gauge

Gauges are a form of charts that can be used to in the web solution.

When used in relation to a contextbox with a checklist they aggregate based upon the checked selection.

Business Gauges can be used in the center top content of the HTMLTemplateDefinition.

Concerns: Here you link to an object of the type which data you would like to display (in the example above an InformationSystem)

Value:

For the gauge chart to display anything, it needs some values. Values are provided by either using URL parameters or by setting up a checklist in a HTMLContentBox left or right panel. When using a checklist, the attributes, defined in Value, will be taken from the selected objects and used in the gauge chart.

Prompt: The prompt that explains to the user, what this value means.
Attribute: The attribute to take a value from.
Color: The color of the value. It will be used in the legend next to the prompt, and also in the chart. Colors should be defined in hexadecimal.
Shape: The shape of how the value is shown in the chart. Shape does not have any meaning for a radial gauge chart as all values will be shown as arrows.
For horizontal and vertical gauge charts, the following options apply:
- bar – shows the value as a bar in the chart.
- arrow – shows the value as a small arrow along the axis in the chart.
Margin: Margin does not have any meaning for a radial gauge chart and for arrow shapes in horizontal and vertical gauge charts.
For bar shapes in horizontal and vertical gauge charts, margins can be used to place the bars next to each other.
If no margin is used, then the bars will be placed on top of each other which will make it difficult for users to easily read the values.
Tip: Use a margin divisible by 7 to space the bars evenly.

Settings:

Title: The title will be shown in the top of the gauge chart on web.

Type:

Vertical:

Horizontal:

Radial:

Miscellaneous display settings:
These are a mix of settings that each has an impact on how the final chart is displayed.

Height: Height in pixels of the gauge chart without the legend.
Width: Width in pixels of the gauge chart without the legend.
Start angle: Only applicable to radial gauge chart.
The starting angle of the chart.
End angle: Only applicable to radial gauge chart.
The ending angle of the chart.
Minor unit: The minor unit of the chart shown with a small line.
Major unit: The major unit of the chart shown with a bigger line than minor unit.
min: The minimum value of the chart.
max: The maximum value of the chart.

Ranges:

Ranges can be used to define if a range should be shown in a specific color. This can be used to enable a user to quickly see if any values are outside of normal values or in other ways concerning.

From: The value at which the color should start.
It is accepted that the From value is the same as another range’s To value.
To: The value at which the color should end. It is accepted that the To value is the same as another range’s From value.
Color: The color of the range in hexadecimal.

IntroductoryViewpoint-ArchiMate

The Introductory Viewpoint is a legacy viewpoint from ArchiMate 2.0.

The Introductory Viewpoint in ArchiMate is designed to provide a simplified overview of an architecture, typically used at the beginning of a design process. This viewpoint uses a subset of the full ArchiMate language with a simplified notation, making it easier to understand and communicate the initial ideas without overwhelming stakeholders with too much detail.

LandscapeMapViewpoint-ArchiMate

The Landscape Map Viewpoint is a legacy viewpoint introduced in ArchiMate 2.0.

This viewpoint helps in visualizing the relationships and dependencies between different architectural elements across various layers, providing a comprehensive overview of the architecture landscape.

Value Stream

A ValueStream is a step in a ValueStreamModel, representing a step in a stream.

A ValueStream has inherited a set of the properties from the BusinessProcess, enabling to describe it:

from a RASCI (Responsible, Accountable, Support, Consulted, Informed) point of view
Capability view
IGOE (Input, Guide, Output, Enbler) point of view
Economic point of view

Value Stream Model

Purpose: The purpose of a Value Stream Model is to model a value stream end-to-end from the perspective of one stakeholder and one value proposition.

Core concerns: The Value Stream Model template enables you to model the value stream stages, triggering stakeholder, and the value proposition. The value stream represents a formal description of how stakeholder value is delivered.

Value Stream : Archimate

A sequence of activities that create an overall result for a customer, stakeholder, or end user.

A value stream describes how an enterprise organizes its activities to create value. A key principle of value streams is that value is always defined from the perspective of the stakeholder – the customer, end user, or recipient of the product, service, or deliverable produced by the work.

Value streams are typically realized by business processes and possibly other core behavior elements. The stages in a value stream provide a framework for organizing and defining business processes, but different parts of the organization may have their own implementations of business processes that realize the same value stream stage. Conversely, one business process may realize multiple stages in a value stream.

It is recommended that the name of a value stream be expressed using a verb-noun construct in the active tense; e.g., “Acquire Insurance Product”.

Stakeholder : Archimate

The role of an individual, team, or organization (or classes thereof) that represents their interests in the effects of the architecture. In order to direct efforts to their interests and concerns, stakeholders change, set, and emphasize goals. Stakeholders may also influence each other. Examples of stakeholders are executives and key managers in an organization, the board of directors, shareholders, customers, business and application architects, and external partners and regulators. The name of a stakeholder should preferably be a noun.

Constraint : Archimate

A limitation on aspects of the architecture, its implementation, or its
realization. In contrast to a requirement, a constraint does not prescribe some intended functionality of the system to be realized, but imposes a restriction on the way it operates or may be realized. This may be a restriction on the implementation of the system (e.g., specific technology that is to be used), a restriction on the implementation process (e.g., time or budget constraints), or a restriction on the functioning of the system (e.g., legal constraints). The name of a constraint should be easily understood and is often a short sentence.

Application Event : Archimate

An application state change. Application functions and other application behavior may be triggered or interrupted by an application event. Also, application behavior may raise
events that trigger other application behavior. Unlike processes, functions, and interactions, an event is instantaneous; it does not have duration. Events may originate from the environment of the organization (e.g., from an external application), but also internal events may occur generated by, for example, other applications within the organization. The name of an application event should preferably be a verb in the perfect tense; e.g., “claim received”