Add to QualiHelp

• New Dashboard feature
• New Table-to-model feature
• More ready made statics for GRC
• Cloud Architecture Metamodel
• API Architecture Metamodel
• G-OWL Metamodel
• EDGY Metamodel
• Parameterized GenericQueries
• Cluster analysis in 3D visualization
• Model Gallery
• RepositoryExplorer – treeview
• New predefined reports
• Required actions on governance tasks
• Unattended installation

QualiWare 10.8 introduces a new Dashboard layout with multiple new features:

• it is possible to set up multiple layouts for a diagram type, e.g. browsing view for the content user; and a analyzing and improving view for for the content owner
• the dashboards can be customized by the user
• the content is responsive, showing associated data either for the diagram as a whole or for the selected object
• a set of new tiles have been added to provide easy access to associated features, well known as well as cool new features

See more details about the new Dashboards on the feature page.

A new table-to-model feature has been introducced in the webmodeller to facilitate a fast and efficient creation of workflow diagrams and BPMN diagrams.

See more about the web-modeler here

“Business Process Network – GRC”  lists all the business process network with the essentional revison information (revision number, validation dates and governance state), along with information about the owner and responsible.

The list is configured, using “Postions” as process owner and responsible, and shows the person holding the position, as well as Termination Date (if available) of the person.

This list gives you get a comprehensive status of all the processes, and can used to monitors the status of the processes:

• when has is last been modified (are they updated recently)
• is the process still valid
• does the process have an assigned postion as process owner and process responsible
• does the position have a postion holder
• and is the person still employed, or will he/she leave the company soon?

If the termination date has passed the cell will be collered red.

“BPN, WFD, BPD – GRC” are structured the same way, as the one above, showing status of all process diagrams (Business Process Networks, Work Flow Diagrams and Business Process Networks) in the repository.

“Business Process Completion” lists all the Business Process Networks and their Business Process and calculates a compleness score for the diagram as well as each business process.

The compleness score of the diagram is a calculated based upon how many of the following fields have been filled out:

1. Owner (OwnedBy),
2. Responsible (HasResponsible),
3. Description (Description),
4. Valid from (RevisionValidFrom),
5. Valid to (RevisionValidTo)

The compleness score of the business process is a calculated based upon how many of the following fields have been filled out:

1. Owner (OwnedBy),
2. Responsible (HasResponsible),
3. ShortDescription (ShortDescription),
4. Description (Description),
5. Purpose (Purpose),
6. Ressources (Employs),
7. UsesInformation (UsesInformation),
8. IT Support (HasITSupport),
9. Deliver Capability (DeliverCapability),
10. Compliance With (ComplianceWith),
11. Associated Document (AssociatedDocument),
12. Valid from (RevisionValidFrom),
13. Valid to (RevisionValidTo)

It is possible to configure the scope of the completeness score, selecting the approprate fields in the underlying query.

“Work Process Completion”  lists all WorkFlowDiagrams and BusinessProcessDiagrams and their Activities, and calculates their completeness score for the diagram and each of the activities.

The calculation is similar to the one above for the Business Process Network. The only exception is that the activity completion is calculated based upon 12 fields, since “Purpose” is not part of an activity-object.

New charts on the Compliance Desktop

In addition to the new list a new set of statistics charts have been included in the Compliance Desktop, showing the distribution of the different types of process diagrams, audit, non-conformancies, and change requests according to their governance status.

This Meta Model customization has been created with the aim to embrace various Cloud Services providers’ solutions. In this customization, cloud services are “first” provider agnostic (they appear as “green cloud” symbols), but at time the provider is defined for a “Cloud Architecture Diagram”, the symbols in the diagram adapt their appearance to the corresponding symbol of the provider, as characterized along categories and instances defined for this provider.

As an example, the sample diagram, in the picture below, is a “Cloud Architecture Diagram” qualified with “AWS” as provider.

Another example in the picture below, is a “Cloud Architecture Diagram” qualified with “Azure” as provider.

Read more about the Cloud Architecture Metamodel here.

QualiWare now supports a range of new templates to enable enterprise architects to model APIs within their existing EA repository. These templates are automatically leveraged upon the creation of an API using OpenAPI.

Architecting APIs in QualiWare can be automated using our new Web Ontology Diagrams, and the APIs themselves can be tested and interacted with directly from the QualiWare front-end by leveraging our adoption of the OpenAPI specification.

See more about the API Architecture metamodel, and how it can be used here.

QualiWare 10.8 includes a G-OWL metamodel.

G-OWL is a Graphical Ontology Web Language, used to document ontologies.

An ontology is a representation of concepts and relationships among them within a domain of interest

Read more about ontologies and how QualiWare supports it here

QualiWare support the EDGY-language created by the Intersection Group.

EDGY introduces a set of reusable Enterprise Elements as a simple but powerful graphical language everybody can understand and relate to. This is a tool that enables designers, architects and change makers to co-design a coherent enterprise by collaboratively exploring the most impactful perspectives and translating between them.

In QualiWare 10.8 we have introduced a new parameterized feature related to the generic queries. This allows you to re-use your the same generic query for multiple purpose.

A example of how this is used, can be seen in the new charts on the compliance desktop.

Learn more about how to create parameterized generic queries.

Clustering provides users with a new way of interacting with content in their repository. It provides an enhanced analysis capability directly from the 3D Visualiser by logically grouping objects based on their relationships, concepts, and definitions. Filters can be applied to the clusters through the table-based view using existing functionality to focus analysis efforts (for example only clustering objects that are related to a risk with a high impact). The number of clusters can also be defined by the user to provide a broader or more concise result.

Once clusters have been created, users can select a specific cluster or sub-cluster to view the relevant grouping of objects. Users will also be provided with a word-cloud which is generated from various attributes of the objects in the cluster.

These clusters can be given a specific name or theme, and the selected objects can be “tagged” using an existing hashtag or by creating a new hashtag. Once the objects from a cluster have been tagged, users can easily navigate to the repository explorer to further interact with individual objects for further analysis. This provides an entirely new way of creating logical groupings of objects based on their concepts or relationships without needing to create custom folders. Identifying patterns and outliers in the repository is a valuable tool for conducting analysis, rationalisation, and transformation activities.

See more details about the new clustering feature here.

A new visualization feature has been created, which make it possible to visualize multiple diagrams in one picture.

In the example below all diagrams on the “next level” is shown.

You can also explore the processes end-to-end via the connecting business event.

Click here to learn more about the Model Gallery

A treeview has been added to the web Repository Explorer.

This feature allows the ability to explore links between objects, such as objects contained on a diagram, or links through other attributes.

A set of new standard reports have been created.

The reports are available from the new dashboards for the following diagrams: BusinessProcessNetwork, WorkflowDiagram, BusinessProcessDiagram, ApplicationArchitectureDiagram.

It is still possible to access available report(s) via the “Print” icon in the toolbar in the top right corner.

Here, the new standard report for the OrganizationDiagram can be found.

There has been added a new tab “Required Actions” on the governance state. This is a text field, where you can use to describe/guide the user what actions that is required for the governance task.

QualiWare version 10.8 now includes an unattended installer.

The unattended installer is meant for IT departments with high volume of installations, automatic deployment environments and environments with a high focus on correct initial configuration. For single deployments, the tutorial based graphical installer is recommended.

The unattended installer will install QualiWare Execution Framework (QEF) and all available modules. After the installation configuration of AccessLog databases, Repository databases, licenses and directory services must be completed.

• Videos about QualiWare X
• Governance, Risk and Compliance
• Enterprise Architecture Use Cases
• Configuration QualiWare 10.8
• Configuration QualiWare

QualiWare X Search Engine (QSE) enables users to quickly search through the whole repository from both the web and QLM. Where the Quick Search tile only searches the names of targeted objects, the new smart content search includes searches of objects’ attributes (such as description fields and links to responsible and owners). Aside from this, the new smart content search can search though documents that have been uploaded to QualiWare. 

The search engine can be found in the upper right corner on the web by clicking on the small magnifying glass:

The search engine indexes and searches through all repository objects and their content – including the content of files that are uploaded to QualiWare via ExternalDocuments. From the web, the search result is then presented with the search term highlighted for usability:

In QLM, the search engine can be found in the right side of the tools menu, also illustrated by a magnifying glass:

In QLM, the search result is presented in an expanded message window with the search term presented in bold writing:

In QLM you can also access a search function via the top-menu, from the “Edit” menu:

From this function you have the possibility to specify search criterias, e.g. searching the whole repository or a specific template type:

If your repository has any language variants, the search engine can search through the current working language of the user as well as the repository default language. If no search results are found in the working language the search is automatically expanded to include objects from the default repository language.

QualiWare X Search Engine is built using the Lucene.Net search component and supports advanced conditional queries such as (Description:Postage) AND (AuditGS: Approved) AND (Date#AuditMD: [2017 201806]) which returns all the approved objects modified between 2017 and June 2018 with the word “Postage” in the description field.

Additional examples of supported queries can be found here.

For Administrators

In order to work, the search engine must be enabled and the repository indexed. This is done from the Repository Administrator module, which can be accessed from QEF.

The Repository Administrator module can be found in QEF under Modules:

In Repository Administrator, you need to index the repository. This is done under “Service Operations” where you click on “Recreate” under “Full-Text Search Index”. Here you can also see when the repository was last indexed:

You also need to enable the Full-Text Search. This is done under “Full-Text Search” for the Repository. Here you need to check the Status box, which can be accessed by pressing “Edit” (se the picture below). If the Full-Text Search is marked as not up-to-date, it means that you need to index the repository. Note that the repository must be offline when you implement these changes.

The Repository Compare functionality has the potential to aid all types of users. Quality Managers can for example promote the right subsets of their work from a project repository to the base configuration – thus ensuring that all of the Quality Team’s work has been considered. Project Managers on the other hand can use this feature to re-use information from other projects in their project repository, thus decreasing the need for re-work.

The Repository Compare feature enables you to open a repository explorer for two different repositories at the same time, with a column in the middle to show whether the content is alike or not. Thus differences between different configurations and/or repositories can easily be analyzed – for example between a private workspace and its base or different project repositories on the same QualiWare Integration Server.

For convenience the compare functionality is available from the Repository Explorer on the web front-end.

Video Highlight

Using the Repository Compare Feature

When on the web front-end click on the Repository Explorer button in the upper right corner. This makes the Repository Compare button available.

Once clicked the Repository Compare feature will open and enable you to select two different repositories and/or configurations from the drop-down menus.

As soon as both repositories have loaded the column in the center will display any differences between the two repositories.

3 different types of signs are used to display the difference between the two repositories:

•  The repository on the right contains an object that is not present in the location on the left
•  The repository on the left contains an object that is not present in the location on the right
•  Both repositories contain the same object, but the properties of the object differ across the two locations
•  Both repositories contain the same object and the properties of the object are consistent across the two locations

For a better overview it is possible to toggle the desired comparison options to be shown via the toolbar.

The first option shows all objects. The second option shows only objects that are alike across the two repositories. The third option shows only the objects that are different across the two repositories.

If there is a difference in the properties of an object across the two locations the property difference can be analyzed by clicking on the drop-down arrow to display the difference.

The contents can then be copied either from the left location to the right or vice versa.

Added in QualiWare 10.1

Use tasks to schedule replication between repositories
Use the new “shopping cart” functionality to create lists of repository objects. If no lists exist, click in the top of the Repository Compare and click Create.
To add repository objects to a list, select one or more objects, right click on the object. Under the “Add to list” available lists will be shown. Select the list where objects should be added.

A new task scheduler enables a timer-based trigger to copy a list of objects from one repository to another. To access the task scheduler, press the “Tasks” button at the top of the object list
This will open the task schedule overview:

A Task contains:

• Trigger: The trigger is the timer triggering the task. This can be defined as one time, minute, hour, day, week, month and year.
• Action: The action contains the sources, destinations and lists. The Source and destination are lists of repositories with configuration/private workspace, role and language specified. The list is a selection of lists to be copied.

When adding a new source or destination it is possible to add a new QEF instance. This new feature provides the ability to copy lists between QualiWare installations.

Folders and hashtags, make it easier for users to find the content they are looking for. Folders and hashtags, enable you to find content in the same way as you do on social media. You can organize content according to many different views together with people you don’t know.

• Hashtags are markers that can be attached to any object regardless if it is frozen. They can be added to an object from either QLM or the web.
• Folders offer access to specific groupings of objects, making objects easily accessible to the relevant stakeholders. The groupings can be based on dynamic search criteria, for example showing objects the viewer has created, or pointing to a set of objects that satisfy the criteria specified for that folder.

By using hashtags and folders, you can structure and organize content in QualiWare targeting specific users or user groups.

Video Highlight

Hashtags

You can edit the hashtags for objects in both QLM and on the web. The hashtags can be added and removed from objects regardless if the objects are approved or in development.

From the web, you edit the hashtags for a diagram by clicking the “Hashtags” icon in the diagram’s toolbar:

When clicking the hashtags icon, a dialog will appear where you can add new hashtags by typing them and choosing submit. You can also remove hashtags. When you hover your curser over the hashtags an X will appear. If you click on the X, that hashtag will be removed from the diagram. To save the changes, close the dialog by clicking “Submit”:

In QLM, hashtags are added and removed from the objects property dialog in the “Tags” tab

When pressing on ‘Add Tag’ you get to ad either an existing tag or create a new tag:

There will be an organization of your content into the groups where it belongs – just because you add the hashtags. Once you have added hashtags to objects in QualiWare, they can easily be linked to corresponding folders. This means that stakeholder specific views now can become easily available.

Folders

Folders offer access to specific groupings of objects, making objects easily accessible to the relevant stakeholders. The template name for folders in QualiWare is “RepositoryFolder”.

The folders all point to a logical set of objects in the repository, meaning a folder points to a set of objects that satisfy the criteria specified for that folder. As such, an object may be present in multiple folders, but only exist as a single object in the repository.

By creating standard setup structures in the folders, you can replicate the structure of the business that people work. This means, that if people are familiar with the organizational structure, they can easily find the relevant content under their department. If they are more familiar with the product structure, they can find the same content under the product names, partner names and so on.

On the web, you can find the folders in the Repository Explorer menu, which can be navigated to via the new tool bar:

Here you can create new folders and edit existing ones by using the tool menu. This is also where you can browse selected template types for easy access.

In QLM, the folders can be accessed and edited in the repository explorer by clicking on the folders icon in the repository views (see picture below). This will prompt a list of folders to pop up in the repository explorer.

When you expand a folder by clicking on the plus on its left, content and sub-folders are shown. There may be several folders within the folders.

When right-clicking on a folder, you can choose to add content to it, add a new sub-folder or open the properties for the folder.

There are four tabs in the properties of the folders you can edit:

• RepositoryFolder: here you can add a short description, include objects based on tags, exclude objects based on tags, and define the folder as a root folder – meaning the folder is present at the first level of the folder structure.
• Objects: Here, you can include specific objects or repository folders.
• Advanced: In this tab, you can include objects based on search conditions or relations.
• Visibility: In this tab, you can specify which persons and roles the folder should be visible to

For more details see the description of the Repository Folder template