Templates | QualiWare Center of Excellence

Peripheral

A peripheral can be any type of item which exists in the infra structure which you want to add to a InfraStructureDiagram. Typically it is a hardware device which is physically defined by a HardwareComponent.

Peripheral properties

The Peripheral tab

Property	Metamodel name	Description
Short Description	ShortDescription	A short description of the item
Type	PeripheralType	The type of the peripheral.
Show	ShowType	Display the type next to the symbol on diagrams. Initial value is off.
Hardware	Hardware	The hardware or computer that implements the peripheral. Links to: Computer, HardwareComponent.
IP Address	IPAddress	The IP address of the device if the address is fixed
Logical name/address	LogicalAddress	The logical name or address of the item.
Show	ShowNetworkName	Display the network name next to the symbol on diagrams. Initial value is off.
Vendor	Vendor	The vendor of the item. The vendor might for instance be an internal organisation unit or an external supplier. Links to: BusinessConnection, ExternalEntity, OrganizationUnit.
Support	Support	The support provider. Links to: BusinessConnection, Person, ExternalEntity, OrganizationUnit.

The Economy tab

Property	Metamodel name	Description
Date of purchase	DateOfPurchase	When the item was purchased
Warranty expires	WarrantyExpires	When the warranty of the item expires
Contracts	HasContract	All the different contracts connected to the item. Links to: Contract.

Plateau : ArchiMate

An important premise in the TOGAF framework is that the various architectures are described for different stages in time. In each of the Phases B, C, and D of the ADM, a Baseline Architecture and Target Architecture are created, describing the current situation and the desired future situation. In Phase E (Opportunities and Solutions), so-called Transition Architectures are defined, showing the enterprise at incremental states reflecting periods of transition between the Baseline and Target Architectures. Transition Architectures are used to allow for individual work packages and projects to be grouped into managed portfolios and programs, illustrating the business value at each stage.
In order to support this, the plateau element is defined.Plateau propertiesThe Plateau tab

Property	Metamodel name	Description
Short description	ShortDescription
Implements	Implements	Links to: All templates.
BreaksDownTo	BreaksDownTo	Links to: All templates.

Policy

A policy is a symbol that represents a set of rules or guidelines that govern an organization’s behavior, decisions, or actions. Policies can be depicted in various types of diagrams, such as Requirement Model, Strategy Model, or Value Chain Model, among others.

Here are some examples of policies that could be represented as symbols in diagrams:

Acceptable Use Policy: a policy that outlines acceptable and unacceptable behaviors when using an organization’s technology or network resources.
Security Policy: a policy that defines how an organization’s information and technology assets should be protected from unauthorized access, use, disclosure, disruption, modification, or destruction.
Privacy Policy: a policy that informs individuals how their personal information is collected, used, stored, and shared by an organization.
Environmental Policy: a policy that establishes an organization’s commitment to sustainability and outlines its approach to minimizing its environmental impact.
Human Resources Policy: a policy that governs employee conduct, benefits, leave, compensation, and other employment-related matters within an organization.
Compliance Policy: a policy that outlines an organization’s commitment to complying with relevant laws, regulations, standards, and guidelines in its operations and activities.

These are just a few examples of policies that could be represented as symbols in diagrams. The specific content and format of policies may vary depending on the organization’s industry, size, mission, values, and other factors.

Pool

A Pool represents a Participant in the Process. A Participant can be a specific business entity (e.g, a company) or can be a more general business role (e.g., a buyer, seller, or manufacturer).

Graphically, a Pool is a container for partitioning a Process from other Pools, when modeling business-to-business situations, although a Pool need not have any internal details (i.e., it can be a “black box”). ° A Pool is a square-cornered rectangle that MUST be drawn with a solid single black line. One, and only one, Pool in a diagram MAY be presented without a boundary. If there is more than one Pool in the diagram, then the remaining Pools MUST have a boundary.

To help with the clarity of the Diagram, A Pool will extend the entire length of the Diagram, either horizontally or vertically. However, there is no specific restriction to the size and/or positioning of a Pool. Modelers and modeling tools can use Pools (and Lanes) in a flexible manner in the interest of conserving the “real estate” of a Diagram on a screen or a printed page.

A Pool acts as the container for the Sequence Flow between activities. The Sequence Flow can cross the boundaries between Lanes of a Pool, but cannot cross the boundaries of a Pool. The interaction between Pools, e.g., in a B2B context, is shown through Message Flow.

Another aspect of Pools is whether or not there is any activity detailed within the Pool. Thus, a given Pool may be shown as a “White Box,” with all details exposed, or as a “Black Box,” with all details hidden. No Sequence Flow is associated with a “Black Box” Pool, but Message Flow can attach to its boundaries.

For a “White Box” Pool, the activities within are organized by Sequence Flow. Message Flow can cross the Pool boundary to attach to the appropriate activity.
All BPDs contain at least one Pool. In most cases, a BPD that consists of a single Pool will only display the activities of the Process and not display the boundaries of the Pool. Furthermore, a BPD may show the “main” Pool without boundaries. In such cases there can be, at most, only one invisibly-bounded pool in the diagram and the name of that pool SHALL be the same as the diagram. Consequently, the activities that represent the work performed from the point of view of the modeler or the modeler’s organization are considered “internal” activities and need not be surrounded by the boundaries of a Pool, while the other Pools in the Diagram must have their boundary.

In QualiWare, the user can specify if the Pool is of a scope of Private (Internal), Abstract (Public), or Collaborative (Global).
The Participant field identifies the role associated with the Pool, or the process that is being executed within the Pool. Since there can be multiple Pools in one BusinessProcessDiagram in QualiWare, it is sometimes important to define the role that is being fulfilled within the Pool.

The Uses Parameter field in QualiWare, on the Pool tab of the Pool Object Editor, permits the user to specify if there is some specific parameter or value essential to the execution of the process that the Pool contains.

The Included in Service field allows the user to specify if there is a unique service associated with the process that is contained in the Pool.

The Target Namespace field allows the QualiWare user to define the scope of the process that is contained in the Pool.

Preventive Action

Definition of an action with the purpose of avoiding certain incidents

PreventiveAction properties

The PreventiveAction tab

Property	Metamodel name	Description
Short description	ShortDescription	Short verbal description of the PreventiveAction
Related Non-Conformance	RelatedNonConformance	Links to NonConformance related to this action Links to: NonConformance.
Responsible	HasResponsible	Link to responsible for this PreventiveAction Links to: InterestGroup, OrganizationUnit, Person, Position, Resource, Role.
Goals	HasGoal	Links to: Goal.
Plan of action	PlanOfAction	Link to ProjectActivity or WorkModelshowing dates and resources for plans to execute this PreventiveAction Links to: ProjectActivity, WorkModel.
Due date	DueDate
Estimated Cost	EstimatedCost	Estimated cost of carrying out this action

The Action taken tab

Property	Metamodel name	Description
Start Date	StartDate	Starting date.
End Date	EndDate	Ending date.
Action taken by	ActionTakenBy	Relation to person/group who executed the action. Links to: InterestGroup, OrganizationUnit, Person, Position, Role.
Cost of Non Conformance	CostOfNonConformance	Cost caused by the non conformance
Resources Spent	ResourcesSpent	Actual cost of corrective action
Corrective Action Taken	CorrectiveActionTaken	A description of the corrective action taken.
Closing date	ClosingDate	The closing date for this NonConformance

Principle : ArchiMate

Principles are strongly related to goals and requirements. Similar to requirements, principles define intended properties of systems. However, in contrast to requirements, principles are broader in scope and more abstract than requirements. A principle defines a general property that applies to any system in a certain context. A requirement defines a property that applies to a specific system as described by an architecture.
A principle needs to be made specific for a given system by means of one or more requirements, in order to enforce that the system conforms to the principle. For example, the principle “Information management processes comply with all relevant laws, policies, and regulations” is realized by the requirements that are imposed by the actual laws, policies, and regulations that apply to the specific system under design.
A principle is motivated by some goal or driver. For example, the aforementioned principle may be motivated by the goal to maintain a good reputation and/or the goal to avoid penalties. The principle provides a means to realize its motivating goal, which is generally formulated as a guideline. This guideline constrains the design of all systems in a given context by stating the general properties that are required from any system in this context to realize the goal. Principles are intended to be more stable than requirements in the sense that they do not change as quickly as requirements may do. Organizational values, best practices, and design knowledge may be reflected and made applicable in terms of principles.

Principle properties

The Principle tab

Property	Metamodel name	Description
Short description	ShortDescription
Implements	Implements	Links to: All templates.
BreaksDownTo	BreaksDownTo	Links to: All templates.

Printer

Use the printer symbol to specify a printer. For all other types of devices use the Peripheral template.

Printer properties

The Printer tab

Property	Metamodel name	Description
Short Description	ShortDescription	A short description of the item
Type	PrinterType	The type of the printer.
Show	ShowType	Display the type next to the symbol on diagrams. Initial value is off.
Hardware	HardwareComponent	Use this field to point to a HardwareComponent, if it is necessary to describe the hardware device that is the printer. Links to: HardwareComponent.
Serial number	SerialNumber	The serial number of the item. This field can be used if you have an internal serial number for all printers, while the manufacturers serial number is specifed in the HardwareComponent in the Hardware field.
IP Address	IPAddress	The IP address of the device if the address is fixed
Logical name/address	LogicalAddress	The logical name or address of the item.
Show	ShowNetworkName	Display the network name next to the symbol on diagrams. Initial value is off.
Shared	isShared	Check this box if the printer is connected to a computer but has been made available for other users in the network. Initial value is on.
Vendor	Vendor	The vendor of the item. The vendor might for instance be an internal organisation unit or an external supplier. Links to: BusinessConnection, ExternalEntity, OrganizationUnit.
Support	Support	The support provider. Links to: BusinessConnection, Person, ExternalEntity, OrganizationUnit.

The Economy tab

Property	Metamodel name	Description
Date of purchase	DateOfPurchase	When the item was purchased
Warranty expires	WarrantyExpires	When the warranty of the item expires
Contracts	HasContract	All the different contracts connected to the item. Links to: Contract.

Problem

A Problem represents a requirement from an interested party for a change in the way the business is running, the project is carried out, the content of a design component in the repository etc.

It is important to note that a problem should concidered a threat to the accomplishment of the business idea, the project or quality of the final product. As opposed to aChangeRequest that represents an opportunity to act.

It should always be clear to an organisation how to handle a Problem. The process of analyzing the scope of the problem, recommending an action and carrying out and action should be controlled by the project management or dedicated people.

Problem properties

The Problem tab

Property	Metamodel name	Description
Short Description	ShortDescription	Short verbal description.
Priority	Priority	The priority for this Problem. Choices are:
Originated Date	OriginatedDate	CreationDate for this Problem.
Originated By	OriginatedBy	The person who put forward this Problem. Links to: InterestGroup, OrganizationUnit, Person, Position, Role.
Status	Status	The status of this Problem. Choices are:
Responsible	HasResponsible	Person responsible for the problem handling Links to: InterestGroup, OrganizationUnit, Person, Position, Role.

The Recommend tab

Property	Metamodel name	Description
Recommended Date	RecommendedDate	CreationDate of this recommendation.
Recommended By	RecommendedBy	The Person/Group responsible for this recommendation. Links to: InterestGroup, OrganizationUnit, Person, Position, Role.
Estimated Resource Requirement	EstimatedResourceRequirement	Estimated cost to solve the problem.
Recommended Solution	RecommendSolution	Description of the recommended solution

The Actual tab

Property	Metamodel name	Description
Start Date	StartDate	Starting date.
Executed By	ExecutedBy	The person/group that carries out the solution Links to: InterestGroup, OrganizationUnit, Person, Position, Role.
End Date	EndDate	Ending date.
Resources Spent	ResourcesSpend	Resources used
Corrective Action	CorrectiveAction	Description of the action

The Breaks Down To tab

Property	Metamodel name	Description
Breaks Down To	BreaksDownTo	Link to models showing a decomposed picture of this entity Links to: RequirementModel, StrategyModel.

Product

This definition covers both intangible, services-based, or information products that are common in information-intensive organizations, and tangible, physical products. A financial or information product consists of a collection of services, and a contract that specifies the characteristics, rights, and requirements associated with the product. “Buying” a product gives the customer the right to use the associated services.
Generally, the product element is used to specify a product type. The number of product types in an organization is typically relatively stable compared to, for example, the processes that realize or support the products. “Buying” is usually one of the services associated with a product, which results in a new instance of that product (belonging to a specific customer). Similarly, there may be services to modify or destroy a product.
A product may aggregate or compose business services, application services, and technology services, business objects, data objects, and technology objects, as well as a contract. Hence a product may aggregate or compose elements from other layers than the Business Layer.
A value may be associated with a product. The name of a product is usually the name which is used in the communication with customers, or possibly a more generic noun (e.g., “travel insurance”).

Product properties

The Product tab

Property	Metamodel name	Description
Short description	ShortDescription
Implements	Implements	Links to: All templates.
BreaksDownTo	BreaksDownTo	Links to: All templates.

Project Activity

A ProjectActivity is used on a WorkModel to show the phases/activities planned to be carried out in a project. For each ProjectActivity the Results and the corresponding QualityControls are linked to the ProjectActivity and the documents produced and used in the project are specified in the form of DocumentStructures. Using this technique the quality plan for the project can be documented before project start, – project experiences may be related to the quality plan as the project moves along, – and the plan may be reused in future projects.
In a highlevel WorkModel the ProjectActivites may break down to a new WorkModel, but at the lowest level ProjectActivities may break down to low level ProjectActivites each producing a single deliverable (Result).

ProjectActivities are also used in CPMDiagram to describe the tasks and their mutual time constraints. This way a critical path through a given project can be discovered and a detailed plan of the relationships between dates, activities and resources can be made.
Since the nature of a ProjectActivity appearing on a work model is of a generic descriptive kind – especially on the higher levels of the work model hierarchy – it will be logical to break such an activity down to a CPMDiagram. The ProjectActivities on the CPMDiagram will then describe when and by whom the work is to be carried out in the project. The activities on a CPMDiagram satisfies precisely the requirements the project manager has while planning and monitoring the project. Whereas the activities on the work model are made with the purpose of guiding and controlling the organisation through standardized procedures and quality management strategies.

ProjectActivity properties

The ProjectActivity tab

Property	Metamodel name	Description
Short Description	ShortDescription	Short verbal description
Purpose	Purpose	Short clear description of the purpose of this activity in the project
Prerequisites	Prerequisites	Descriptions of deliverables and conditions for this activity to start
Responsible	HasResponsible	Link to the responsible for this activity Links to: InterestGroup, OrganizationUnit, Person, Position, Resource, Role.
Involved	Employs	The resources used by this activity Links to: InterestGroup, OrganizationUnit, Person, Position, Resource, Role.

The Dates tab

Property	Metamodel name	Description
Earliest start	EarliestStart	In this field the date for the earliest start of this Activity is entered. The date can be entered manually or the field can be filled with the use of the menu option Calculate earliest or Calculate both directions on a CPMDiagram.
Earliest finish	EarliestFinish	In this field the date for the earliest finish of this Activity is entered. The date can be entered manually or the field can be filled with the use of the menu option Calculate earliest or on Calculate both directions a CPMDiagram.
Latest start	LatestStart	In this field the date for the latest start of this Activity is entered. The date can be entered manually or the field can be filled with the use of the menu option Calculate latest or Calculate earliest on a CPMDiagram.
Latest finish	LatestFinish	In this field the date for the latest finish for this Activity is entered. The date can be entered manually or the field can be filled with the use of the menu option Calculate latest or Calculate earliest on a CPMDiagram.
Optimistic	OptimisticDuration	This field is used to give a very optimistic estimation of the duration of the activity. The value of the field should mark the 1 percentile of the propability distribution. This means that there should be less than 1 % propability that the duration will be shorter than the value of this field. The shortest possible time period used to perform this activity.
Total slack	TotalSlack	Gives a slack value based on the assumption, that all preceeding activities are carried out as early as possible, and all succeeding activities are carried out as late as possible. The field can be filled with the use of the menu point Calculate slack on a CPMDiagram.
Group
Group
Realistic	RealisticDuration	The most likely time period used to perform this activity.
Free slack	FreeSlack	Gives a slack value based on the assumption, that all preceeding and succeeding activities are carried out as early as possible. The field can be filled with the use of the menu option Calculate slack on a CPMDiagram.
Pessimistic	PessimisticDuration	This field is used to give a very pessimistic estimation of the duration of this activity. The value of the field should mark the 99 percentile of the propability distribution. This means that there should be less than 1 % propability that the duration will be longer than the value of this field. The longest possible time period used to perform this activity.
Independent slack	IndependentSlack	Gives a slack value based on the assumption, that all preceeding activities are carried out as late as possible, and all succeeding activities are carried out as early as possible. The field can be filled with the use of the menu option Calculate slack on a CPMDiagram.
Start Date	ActualStartDate	The actual starting date of the activity
End Date	ActualEndDate	The actual ending date of the activity
Group
Number of spent time units	ActualSpentTimeUnits	In this field the actual number of spent persondays for the activity is entered. If this field contains a value the value is used instead of the planned estimation parameters, when a total estimation including the activity is made. In this way an estimation process that includes allready finished activities will use the actual numbers instead of the planned numbers.
Time unit for Duration and Slack	TimeUnit	The unit for time measurement for this Activity. Choices are: Seconds Minutes Hours Days Weeks Months Years

The Breaks Down To tab

Property	Metamodel name	Description
Breaks Down To	BreaksDownTo	Links to entities specifying this project activity Links to: CPMDiagram, ProjectActivity, WorkBreakdownStructure, WorkModel.
Result	Produces	Link to deliverable for a low-level ProjectActivity Links to: Result.

The Relations tab

Property	Metamodel name	Description
Relevant generic processes	UsesGenericProcess	Links to: Activity, WorkFlowDiagram.
Relevant Documents	HasRelevantDocument	Links to: ConfigurationDiagram, ExternalDocument.
Belongs to Organization	BelongsToOrganization	Links to: OrganizationDiagram, OrganizationUnit.

The Cost tab

Property	Metamodel name	Description
Group
Multiplier	PlannedMultiplier	Planned estimation parameters. These parameters are used to define and store the cost estimation model an organization is using in order to estimate the size and costs for a specific project. Using the three fields multiplier, exponent and projectsize the definition of an exponential function relating project size to effort can be defined. Consequently a total estimated effort for a hierarchy of workmodels and activities can be calculated. This is done from the workmodel menu. Multiplier. In this field the planned multiplier for the activity can be entered. The multiplier will be calculated from the key figures for the organisation, based on the organizations experience with activities like the current, the skill level of the project group, the use of tools etc.
Exponent	PlannedExponent	In this field the exponent for the function can be entered. If the exponent has the value one, the multiplier will denote the slope of the curve of the function.
Size	PlannedProjectSize	In this field the project size can be entered. The project size can be measured in all kinds of units such as function points.
Group
Injections	PlannedInjections	In this multiline field the planned income to the project during the current activity can be entered. The purpose of doing this is to be able to calculate the cash flow of the project.
Withdrawals	PlannedWithdrawels	In this multiline field the planned cost for the activity can be entered
Group
Multiplier	ActualMultiplier	In this field the actual multiplier for the activity is entered.
Exponent	ActualExponent	In this field the actual value of the exponent for the activity is entered.
Size	ActualProjectSize	In this field the actual project size is entered.
Group
Injections	ActualInjections	In this multiline field the actual cost to the project during this activity is entered
Withdrawals	ActualWithdrawels	In this field the actual cost from the project during this activity is entered.

The Techniques tab

Property	Metamodel name	Description
Use technique	UseTechnique	Links to technique instructions Links to: Document, ExternalDocument, Technique.
Tool	Tool	Link to tool-specifications for this result Links to: ExternalDocument, InformationSystem.
Good Practice examples	GoodPractice	Link to files showing good examples Links to: All templates.

The Show tab

Property	Metamodel name	Description
Show on WorkModel	Show	Set diagram view for this ProjectActivity Choices are:

The Action tab

Property	Metamodel name	Description
Macro	Macro	This field is used to create a command language program that can be executed when the user double clicks on the symbol.
Execute on Double-click	ExecuteOnDoubleClick	Macro is always executed when double clicking on the symbol. Initial value is off.