Skip to content

AxivionSuite

Jump to bottom
Rainer Koschke edited this page Oct 30, 2023 · 9 revisions

Visual Studio Plugin

Certificate for the Axivion Dashboard Server

Our Axivion Dashboard Server for SEE uses an official, non-selfsigned CA certificate. Hence, it should not be needed to install any CA certificate in your system's certificate store (OS/browser, Java, Python) to trust the Axivion Dashboard Server.

Axivion IDE Plug-Ins

Axivion offers plug-ins for multiple IDEs, including Visual Studio and Visual Studio Code. In the following, we explain how to install the Visual Studio plug-in, which is our preferred IDE. The installation for other plug-ins offered by Axivion are similar.

Download, install, and configure the Visual Studio Plugin

  1. Go to the Axivion Dashboard. The necessary credentials can be received from Rainer.
  2. After having logged in, click on the book icon at the top right corner to unfold a menu. Select the menu entry Visual Studio Plugin.
  3. On the next page, select your version of Visual Studio. This will start the download of the Visual Studio plugin. Select "Open with VisualStudioLauncher.vsix" and install the plugin.
  4. Then follow the instruction provided here and in particular the instructions on how to configure the plugin provided here. The URL of the Axivion Dashboard must be https://stvr2.informatik.uni-bremen.de:9443/axivion.
  5. A dialog should open asking you for your credentials for the Axivion Dashboard. These are the same you have used to login to the Axivion Dashboard. The dialog can also be opened via menu entry Tools/Options/Axivion and then Edit or Add dashboard, respectively.

Viewing the software-erosion data of SEE's implementation in SEE

  1. In the scene SEEWorld in the game object Scene Settings activate the component DashboardRetriever. The base URL must be https://stvr2.informatik.uni-bremen.de:9443/axivion/projects/SEE/, the public key is listed below, and the API Token can be retrieved from the Axivion Dashboard by the Preferences menu entry of the menu that unfolds when you click on your user name in the top right corner. This click will lead you to another page, where you can hit the "Create new Token" button in the section "Application Tokens". The token should be a "General Purpose" token. Copy and paste this token into the Token field of the DashboardRetriever component in SEE via the inspector.
  2. In the code city showing the data for SEE's implementation, select the appropriate GXL file in the "Data Files" section. An RFG file from which to extract the RFG file can be retrieved from the project overview on the starting page of the Axivion Dashboard by selecting the project SEE and then "Download RFG File". Note that you need the Axivion Suite to process this file. If you have access to the Axivion Suite (it is installed on stvr2.informatik.uni-bremen.de), you can either use the tool Gravis or rfgexport to export a GXL file from the RFG file. Consult an expert on this.
  3. In the section Erosion of the "SEECity" component of the code-city object, turn on "Show inner erosions", "Show leaf erosions", and "Load Dashboard Metrics".
  4. To view the issues also in the code windows, you should enable "Show Issues in Code Windows". The GXL files for the SEE dependency graph has relative paths for the contained declarations. So that the source-code files can be loaded from your local disk, you may need to adjust the "Source Code Directory" in the "Data" section.
  5. Then generate the visualization for this code city as usual. If the metric data can be retrieved from the Axivion Dashboard, the message "Loading metrics and added issues from the Axivion Dashboard for start version EMPTY." will be emitted in the console of the Unity editor. Likewise, when you start the game and the graph data are read from the GXL file associated with the code city, a message "Updated metric values and issues using the Axivion dashboard." where and are the numbers metric values and issues, respectively.

Public key:

3082020A0282020100B20ACB6E1639D673B6AF9E9F36578F66068AFDA50327DC2AB0F804E2F83765BCB7AD74FED31EC8812FF9AA9C2461D53F7DC08449C765F0ECFA9C0787B9D1E1AE92F8D1919EDB6871E70601DB0834FF34389EDBA30BFF48F3EA8D07786E976B04F5232AC3A63D07DA5EAD5F5450026C9E2FB9294D32FC0172E9F0DFF33CDCB35180DB22E6985C15B02BBFAD02499D0E52AA916ADD5F9E7A40E22B8EC5427E02E47FD78CFEF30B5A2EDB53EA47E8B70230FB9EAE57B4B7042BD8829F67F4DCDA0230BB933741AF42992CD9164C4F5E2C126A46DC42AE5BD22682C97880F8D0A82FA36FEC89CE9318E0DE2CAA3352F92F6231B18DF29913445AA323931106B0764066DB4A2F8764CE4FAC2500F5A084AE3133C6C82D18181655FC1050629257A54B44FBACB1BE43E51C7FA80DD7CE68D2F86AF448CA2E03B3C81A1289AA355E926CF221D881BFCD82BE7B0FA99F1B04A95D23F9B030B6CDF81E90197868BC72F314E2DFBA5F9965517F8C33BF056C0050DB08D285C988EFF7F212CC9D652E70B8FE67BC632F17ECFAE57603F5592C831951442F821575139D193B4DC4F2EB46FEE09495CCF67259A3F4516873612582B84512019A1157F621B46D45BCEE471BCE855C068B701F40C4CBB78F8E11550C83D7E6897967FD0B90C4BD25B0E388449266293CF52814112B7F1A95A8EC3D6CBB5567B6B0916A995D5EB8254E31647B2F810203010001
Clone this wiki locally