Polarion on Software Factory

Polarion/Jira integration

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Get traces of requirements and tests impacted by Agile activities

---
config:
 theme: neutral
 layout: elk
---
 graph LR
 %% Définition des sous-graphes
 subgraph Polarion
 R1(Requirement)
 R2(Requirement)
 end

 subgraph JIRA
 E(Epic)
 S1(Story)
 S2(Story)
 end

 %% Relations
 E --> R1
 E --> R2
 E --> S1
 E --> S2
 S1 --> R1
 S2 --> R2 


 %% Application des styles
 class Polarion,JIRA system;
 class R1,R2,E,S1,S2 item;

 %% Ajustement de la direction
 linkStyle default stroke:#000000,stroke-width:1px;

In an Agile project, stories and epics serve as developmental artifacts. They are instrumental in organizing sprints and are not designed to store long-term data about needs. Therefore, it is logical to link these Agile artifacts to requirements.

Polarion/Tests integration

Mon, 01 Jan 0001 00:00:00 +0000

Concept

Import data from automatic test execution result files to produce conformity matrixes

---
config:
 theme: neutral
 layout: elk
---
graph LR
 %% Sous-graphes
 subgraph Polarion
 R(Requirement)
 TC(Test Case)
 TR(Test Run)
 end

 subgraph Gitlab-ci
 AT(automatic tests)
 end

 %% Relations
 AT -->|"&lt;optional&gt; import"| TC
 AT -->|"import"| TR
 R --> TC
 TC --> TR
 

 class Polarion,Gitlab-ci system;
 class R,TC,TR,AT item;

Test results can be imported using two XML file formats:

JUnit file format
XML from Vivaldi (See Distributed Systems document)

JUnit-Like Format for Test Results

JUnit is a commonly used format for reporting test results in XML format. Polarion supports the import of JUnit XML reports, enabling the automatic creation or update of test runs and test results within Polarion. + This document primarily focuses on the JUnit-like format and elaborates on the structure necessary for importing into Polarion.

Traceability, conformity and conformance

Mon, 01 Jan 0001 00:00:00 +0000

Overview & Expected Benefits

Software engineering projects that work with system engineering face key challenges in communication, development processes, and compliance with specifications.

Five specific areas of focus typically arise and require careful attention.

Specification Transfer and Collaborative Development Processes

One of the primary challenges is the effective transfer of specifications from the system engineering team to the software development team. Clear communication and collaborative documentation are essential to ensure a mutual understanding of requirements. Misinterpretations at this stage can lead to significant setbacks later in the project. In a co-engineering environment, collaboration between system and software teams is essential. Both teams must engage in parallel activities throughout the development phase. This means aligning their engineering efforts and providing real-time feedback to ensure that the project adheres to system specifications.