Non-Graphical | QualiWare Center of Excellence

Asset Group

The Asset Group template enables you to create groupings of assets. It is useful to have group categories for your assets to easily create overviews of the specific asset groups.

Properties

The AssetGroup tab

Property	Metamodel name	Description
Group category	GroupCategory
Short description	ShortDescription

You use the ArchitecturePrinciple template to document architecture principles – meaning rules you have defined or adopted to document a coherent enterprise architecture. You can link the ArchitecturePrinciple to the FrameWorkCells they apply to under the FrameWorkCell’s Architecture principles field under the ‘relations’ tab. You can also link the architecture principle directly to the ArchitectureFramework’s properites under its Principles-field.

Architecture Domain

The Architecture Domain template is used in FrameWorkCells that populates ArchitectureFrameworks. The Architecture Domain is linked to the FrameWorkCell in the FrameWorkCells properties and help describe what type of domain the framework cell represents – such as Technology, Application, Process and so on. You can then give the architecture domain an adequate description in its properties and link it to multiple framework cells if you create different views for the same domains. You are also able to link multiple domains to the same framework cell if domains overlap.

Properties

Property	Metamodel name	Description
Description	Description	Long verbal description.

Active Directory Sync Setup

The ActiveDirectorySyncSetup template is a system template previously used to synchronize objects between the active directory and QLM. This however is now done in QEF or via the tools menu:

Acknowledge List

The Acknowledge list function enables you to keep track of and document which of your employees have read which relevant documentation.

An acknowledge list is used to select a group of people who must digitally acknowledge that they have read or studied specific sets of documentation. This can for example be a diagram, a document, or a set of regulations. An acknowledge list can be a one to one or a many to many relationships between objects and people. This means that you can have several people, InterestGroups, OrganizationalUnits or several objects listed in the same acknowledge list.

Once a user is assigned to acknowledge an object, the user will get a govenance task, when a new revision of the object is approved. Note as standard the object should be part of the standard “Change Management” governance workflow and the object state, and the Acknowledge is shown when the object is in “Approved” state (read more about the governance workflows here).

An “Acknowledge” action-button is shown in relation to e.g. the Diagram:

The Acknowledge history can be seen on the “Acknowledge History” tab:

A user can access their ackowledge task(s) via their “My task” action button in the top right

And from their “To Do list” from the desktop.

Function Point Estimate

A FunctionPointEstimate uses a combination parameters and complexity factors to compute an estimated number of function points for the system.

Since the estimation follows the algorithme described in general available litterature it will not be described in details here.

In addition to the fields of the main tab the window contains tabs for ‘External Input’, ‘External Output’, ‘Inquiries’, External Data’ and ‘Internal Data’ are used.

The user is supposed to enter values for the number of ‘Simple’, ‘Average’ and ‘Complex’ parameters. In the buttom row of the dialogs the company standards can be entered.

The subdialog ‘Complexityfactors’ gives a list of factors – each with a scale of importance ranging from 1 to 6.

When all parameters are set up, the compute button can be pressed.

The properties of a FunctionPointEstimate are:

– Number Of Implemented Function Points Per Personday (AvgProductivity).
This field is used to enter the productivity of the project group.

– Function Points (FunctionPoints).

– Estimated Total Effort In Persondays (EstimatedTotalEffort).

– Count (ExtInSimpleCount).

– Count (ExtInMediumCount).

– Count (ExtInComplexCount).

– Weight (ExtInSimpleWeight).

– Weight (ExtInMediumWeight).

– Weight (ExtInComplexWeight).

– Count (ExtOutSimpleCount).

– Count (ExtOutMediumCount).

– Count (ExtOutComplexCount).

– Weight (ExtOutSimpleWeight).

– Weight (ExtOutMediumWeight).

– Weight (ExtOutComplexWeight).

– Count (QueriesSimpleCount).

– Count (QueriesMediumCount).

– Count (QueriesComplexCount).

– Weight (QueriesSimpleWeight).

– Weight (QueriesMediumWeight).

– Weight (QueriesComplexWeight).

– Count (ExtDatSimpleCount).

– Count (ExtDatMediumCount).

– Count (ExtDatComplexCount).

– Weight (ExtDatSimpleWeight).

– Weight (ExtDatMediumWeight).

– Weight (ExtDatComplexWeight).

– Count (IntDatSimpleCount).

– Count (IntDatMediumCount).

– Count (IntDatComplexCount).

– Weight (IntDatSimpleWeight).

– Weight (IntDatMediumWeight).

– Weight (IntDatComplexWeight).

– Reliable Backup/Recovery (BackupRecovery).