Requirements Managers | QualiWare Center of Excellence

Control Coverage Map

Purpose: The purpose of the Control Coverage Map is to provide an overview of uncovered risks, residual risks and potential cost of the risk occurring.

Core concerns: The Control Coverage Map concerns itself with Financial Risk Management and is created using the Actions tabs in QLM. It can be created based on the information in a Risk Heatmap or by using information from a diagram which contains risks that also have control actions.

Below, you can see an example of a Control Coverage map for four risks related to a Bellhouse, a Pump, a Suction pipe and using Check lists:

The Blue column represents the likelihood of the risk before the control action, the green column represents the likelihood of the risk after the implementation of a control action. The red columns represent the estimated cost if the risk is realized.

Relation to other templates: The Control Coverage Map presents graphical views of information from other diagrams the same as the Heatmap, Business Charts and the Graphical Matrix. It can be used by any diagram containing Activities with attached risks that have control activities.

Properties and metadata: The Control Coverage Map can for example retain the following information:

A description
Link to the owner
Link to the one responsible
Graphical specification for the headers of the X-axis and Y-axis
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the Control Coverage Map

The above picture shows the properties dialogue window for the Control Coverage Map template where you can view and edit the template’s properties in QualiWare Lifecycle Manager.

Conceptual Data Model

Purpose: The Conceptual Data Model template is used to describe a high-level business oriented structure of the information concept used in a specific business area. Below yo can se an example of a Conceptual Data Model where the data is divided into data for internal and external use:

Core concerns: The conceptual data model template enables you to model a preliminary high level data model. It may be abstract in content and sparse in attributes. Its preliminary structure allows for many-to-many relationships. When using the Conceptual Data Model, you can model Information Concepts, Subject Areas, and their interrelationships. Below, you can see a car rental service’s Conceptual Data Model for a customer’s data.

Relation to other templates: The conceptual data model is a means of communicating information structures between participants in a project or documenting the overall Information Concept of a specific organization. For a more detailed model you should use a Data Model Diagram.

Properties and metadata: The Conceptual Data Model can for example retain the following metadata:

A description of the diagram
Link to the owner of the diagram
Link to the one responsible for the accuracy of the diagram
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
Project status: information about budgeted and actual man-hours spent, percentage completed and the latest milestone, result and quality control of a change process.

In the picture below you can see the Conceptual Data Model’s properties dialogue window, where the information can be viewed and edited:

Composite Structure Diagram

Purpose: The purpose of the Composite Structure Diagram template is to document the internal structure of a class, Class interactions with the environment and behavior of collaborations. The Composite Structure Diagram is part of the UML version 2.5.

Core concerns: The Composite Structure Diagram enables you to model Collaborations, Collaboration Use, Properties, Classes, Interfaces and Ports. These elements can be connected by Connectors, Dependencies, Interface Realizations and Usage.

Below, you can see an example of a Composite Structure Diagram for a car safety inspection:

The Diagram shows internal structure of the Car-safety inspection class as well as the behavior of collaborations and the different classes’ interactions.

Relation to other templates: The Composite Structure Diagram is part of the UML templates QualiWare supports along with the Activity Diagram, Communication Diagram, Deployment Diagram, Class Diagram, State Diagram, Package Diagram, Component Diagram, Sequence Diagram, Use case diagram and Timing Diagram.

The Composite Structure Diagram can be defined as the components content along with the Component Diagrams, Class Diagrams, Classes, and Interfaces. The Component Object is a representation of a physical part from the system specification.

Properties and metadata: The Composite Structure Diagram can for example retain the following information:

A description of the diagram
Link to the owner of the diagram
Link to the one responsible for the diagram
Extensions (Stereotypes, constraints and tagged values)
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Composite Structure Diagram where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

For more information: about the UML, please visit the Object Management Group’s Website, where you can find the complete specification.

Communication Diagram

Purpose: The purpose of the Communication Diagram template is to document interactions between objects or parts, focusing on sequenced messages.

Core concerns: The Communication Diagram template is a simplified UML 2.0 alternative to the UML Collaboration Diagram. It enables you to model Lifelines and Annotation, which can be connected by messages.

Below you can see a simple example of a Communication Diagram:

Relation to other templates: Usually, Communication Diagrams would be modeled using information from Class Diagram, Sequence Diagram, and Use case diagram. It is related to the other UML interaction diagrams: Sequence Diagram, Interaction overview diagram and Timing Diagram.

While the Communication Diagram show much of the same information a Sequence Diagram does, the Communication Diagram conveys which elements each one interacts with better, while sequence diagrams show the order in which the interactions take place more clearly.

Other UML diagrams that QualiWare support include: Activity Diagram, Communication Diagram, Deployment Diagram, , Composite Structure Diagram, State Diagram, Package Diagram, Component Diagram, Composite structure Diagram, and Object Diagram.

Properties and metadata: The Communication Diagram can for example retain the following information:

A description of the diagrams
Link to related sequence diagram
Extensions (Stereotype, Constraints and Tagged values)
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Communication diagram, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

For more information: about the UML, please visit the Object Management Group’s Website, where you can find the complete specification.

Class Diagram

Purpose: The primary objective of the Class Diagram template is to visually represent and document the structural components of a system utilizing the Unified Modeling Language (UML). Displayed below is an example of a straightforward Class Diagram:

Core concerns: The Class Diagram effectively captures the various classes within a system, their attributes, operations, and the relationships between classes and other objects, such as packages. This comprehensive representation enables a clear understanding of the system’s structure, promoting efficient communication among stakeholders and facilitating system design and maintenance.

Example: In the Class Diagram below, the relationships between the classes “Customer” and “Internet User” and the packages “WEB-API”, “Reservation Control”, “GUI” (Graphical User Interface), and “Database” are illustrated. This example highlights the connections among different components and provides a visual overview of how they interact within the system:

Relation to other templates: The Class Diagram presents a detailed structural view of information. It can for example be a decomposition of an Information System which typically is presented in an Application Architecture Diagram. If a Class Diagram becomes too complex or large, a Package Diagram, where the classes are grouped into Packages, could be modelled instead.

Properties and metadata: The Class Diagram can for example retain the following information:

A description of the diagram
Link to the owner of the diagram
Link to the one responsible for the diagram
Audits (auto generated information regarding its current state and access rights)
Extensions regarding constraints and tagged values
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

In the picture below you can see the Class Diagrams properties dialogue window, where the information can be viewed and edited:

Business Process Network

Purpose: The purpose of the Business Process Network is to at document a mid- to high-level view of Business Processes and their interrelationships.

Core concerns: The Business Process Network template enables the documentation of top to mid-level processes. The core objects available to model with are Business Processes, Business Events, Business Objects, Business Scope, Information Systems, and different types of connections. Below you can see two examples of a Business Process Network modelled in different styles.

High level process view without business events or connections between processes:

High-level process view where business events and connections indicate a flow between processes, stakeholders and customers:

Relation to other templates: The top-level processes would typically be broken down to one or more levels of mid-level processes. The last level of Business Process Networks can then be broken down to several Workflow Diagrams or Business Process Diagrams detailing the activities contained within the business process

Properties and metadata: The Business Process Network can for example retain the following information:

Description of the diagram
Link to the owner of the diagram
Link to the one responsible for executing the processes in the diagram
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

In the picture below you can see the Business Process Network’s properties dialogue window, where the diagrams properties can be viewed and edited:

Business Process Diagram

Purpose: The purpose of the Business Process Diagram template is to enable workflow modelling using the industry standard BPMN (Business Process Modeling Notation).

Core concerns: The Business Process Diagram template supply you with the BPMN icons that enable you to draw a workflow diagram. These icons include different types of events, activities, gateways, connectors, as well as pools, lanes and artifacts such as data objects and messages. The Business Process Diagram is typically used to illustrate business processes and software processes used in requirement documentation. Below is an example of a classic BPMN diagram with swimlanes:

To ensure the right BPMN syntax, the Business Process Diagram template will continuously perform Graphic Syntax Checks while you model. When a graphic syntax error occurs, you will be met with an error message like the one shown below:

Other functionalities: The Business Process Diagram can enable the execution and automation of a process when the diagram is converted into XML type files.

If you don’t wish to have a visible pool in your diagram, you can choose to have a ‘default pool’ that doesn’t have to be graphically represented. You can see an example of a diagram without pool and lanes below:

Relation to other templates: The Business Process Diagram template is exclusively aimed at modeling using the BPMN standard. If the BPMN is not chosen as a mandatory standard, the WorkFlow Diagram template, which has fewer syntax limitations, can be used instead.

The Business Process Diagram is typically linked as a decomposition of a Business Process contained in a Business Process Network template.

Properties and metadata: The Business Process Diagram can for example retain the following information:

Description of the diagram
Expression and query language
Link to the owner of the process
Link to the one responsible for executing the process
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

In the picture above you can see the Business Process Diagram’s properties dialogue window, where the diagram’s properties can be viewed and edited:

For more information: about the BPMN standard please visit OMG’s dedicated website.

Business Diagram

Purpose: The purpose of a Business Diagram is to show the functional structure and relationships of the whole or part of an organization.

Core concerns: The Business Diagram template enables you to model Business Functions, Information Systems, Inventory, Business Scope, Lines of Business, Information Flow and Logistical Flow. The diagram’s syntax can be extended to also include strategic elements such as Goals, Objectives, Stakeholders and Performance Indicators.

The Business Diagram should be broken down into several levels of recurring Business Diagram templates. In the model below, you can see an example of a high-level Business Diagram showing Business Functions and their Information Flows and Logistical Flows – describing the flow of products and services – in this case for a car rental service.

The Business Functions are placed with the operational functions in the bottom together with the Logistical Flow and with management control at the top of the Business Diagram.

On lower levels (decompositions) of Business Diagrams, Information Systems are placed close to the Business Functions that are responsible for or own the Information Systems.

Relation to other templates: The Business Diagram can be used as an addition to a Business Process Network and Strategy Models, giving a practical view of how the organizations functions fit together, illuminating interdependencies.

Properties and metadata: The Business Diagram can for example retain the following information:

A description of the diagram
Link to the owner of the Diagram
Link to the one responsible for the Diagram
Indication of the diagram portrays an as-is situation or a to-be situation
The Perspective can be defined as either: Holistic, Sub-functional, Process, or IT Focused.
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Business Diagram where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Architecture Framework

Purpose: The purpose of the Architecture Framework template, is to provide an overview of the enterprise, and the context for a diagram, showing where in the architecture and repository it belongs. An Architecture Framework shows the overall structure of the architecture and the structure with which it is represented in the repository.

Core concerns: The Architecture Framework template consists of FrameWorkCells, FrameWorkColumns, FrameWorkRows and LineOfBusinesses. You can choose to model the framework to fit the one your organization is using – QualiWare supports a wide range of architecture frameworks out of the box such as Zachman, TOGAF , OIOEA, EA3 Cube, EDGY, QualiWare EA Framework, and many more.

Below, you can see an example of the QualiWare EA Framework:

Below, you can see an example of a TOGAF framework:

Relation to other templates: The Architecture Framework template is used to represent the repository’s architecture in the form of a specific framework. If CXO dashboards are to be created, the Strategy Model should be used instead.

An ArchitectureFramework can be modeled using FrameWorkRows, FrameWorkColumns, and FrameWorkCells

Properties and metadata: The Architecture Framework can for example retain the following information:

A description of the diagram
Link to Architecture principles and project models
Link to the owner of the framework
Link to the one responsible for the framework
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Architecture Framework where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Application Functionality Context

Purpose: The purpose of the Application Functionality Context template is to document the in which Activities and/or Business Processes a given Application Functionality is used.

Core concerns: The Application Functionality Context template can be used to create graphical views showing where Application Functionalities are used. The template enables you to model Application Functionalities, Activities and Business Processes. The Business Processes and Activities are connected to Application Functionalities using Functionality Usage.

Below, you can see an example of an Application functionality contest diagram, where the context for the DocCom – Create and Store Document functionality is shown:

The diagram shows which Business Processes use the Application Functionality as well as which Information System delivers it.

Relation to other templates: To map applications hardware, the Application Architecture Diagram or Infrastructure Diagram template should be used. The Application Functionality Context template graphically connects functionalities of Information Systems to the Processes and Activities in which they are used. It offers an additional view to Application Architecture Diagrams, Workflow Diagrams, Business Process Diagrams and Business Process Networks.

Properties and metadata: The Application Functionality Context template can for example retain the following information:

A description of the diagram
Audits (auto generated information regarding its current state and access rights)
Associated documents, diagrams and other objects
Inherent Risk detailing risk considerations
Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Application Functionality Context template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.