This document provides an overview of the Matrix42 Core solution documentation. Familiarizing with the documentation structure helps to get the most value out of the documentation. 

This document covers the Matrix42 Core solution documentation. Sales documentation and other documentation are excluded from this document's scope. 

Overview

The Matrix42 Core solution documentation is published in the Efecte Docs. It consists of four levels:

1. Solution introduction
2. Process overviews
3. Use case descriptions
4. Delivery instructions. 

The delivery tasks and test cases included in new customer deployments (starting from Q4 2023) are linked to the documentation in docs.efecte.com, as demonstrated in the figure below.   

Document types and content

Solution introduction

The solution introduction provides a high-level overview of the solution. It describes the solution on a high level, including its key capabilities and characteristics. 

The solution introduction is mainly targeted at customers.

Process overviews

The process overviews provide a summary of each process. It includes:

• A brief summary
• List of included use cases
• Use case diagram
• Process flowchart (if applicable)
• Process timeline (if applicable)
• Terminology
• Prerequisites
• Results
• Actors and roles
• The default delivery content  

Process timeline

Process timelines provide a visual overview of the process, from when the process is initiated to when it is terminated. The timelines also describe some time-based process performance indicators, for example, the Response and Resolution time in the case of Incident management. 

Terminology

The terminology chapter presents relevant terms and brief definitions for them. 

Prerequisites

Defines prerequisites for the process. 

Results

Defines the outputs and outcomes of the process. 

Actors & roles

Describes the actors involved in the process and maps the actors to technical roles in the Efecte Service Management Tool (ESM). 

Default delivery content

Describes the scope of the default delivery of an Matrix42 Core delivery. 

Use case descriptions

The use case descriptions describe the use cases belonging to the process. The use case descriptions do not serve as a user guide for the application since they do not provide detailed instructions on how to interact with the user interface. The following chapters describe the content of the use case documents.  

Example scenario

The example scenario provides a real-life example with contextual information for describing the use case in a practical way. The example scenarios strive to help the reader to understand the use case better.  

Use case diagram

The use case diagrams provide an overview of the actors, applications, and actions (use cases within the main use case). The use case diagrams are documented according to the UML standard. The use case diagrams describe actions and relationships without attempting to describe the process or data flow as a process flowchart would.  

Workflow

The workflows chapter describes one or more workflows associated with the use case. It can be seen as a subprocess for the main process. In practice, the workflows are described as numbered lists of steps.  

Results

The results chapter describes the outputs and outcomes of the use case. For example, as a result of the Resolving incidents uses case, the Ticket's status is set to Resolved and the issue has been resolved, or a workaround has been provided. 

Benefits

The benefits chapter describes the benefits the use case plans to provide to the organization.  

Delivery Instructions

The delivery instructions chapter includes links to delivery instructions relevant to the use case. 

The intended audiences for the documents