ALM Sync - RB01 Group 4
Project description
Main Research Question
- How do we design a solution that synchronizes the workflow between Helix and Azure DevOps Work Items with the target performance in mind?
Sub-Questions
- What is the client’s workflow between Helix and Azure?
- What is the client’s target performance?
- How do we use clients' environments to create our solution?
- How can bug reporting from Helix to Azure DevOps be automated and be easily configurable by the client?
- How can our solution be developed with protection in mind while adhering to all the GDPR laws?
Context
The problem comes from the usage of different tools, that essentially have the same functionality, but are used with different means by separate company teams. Here’s a diagram showcasing the usage of the software by the different roles:
Currently, when a client reports a bug to the service desk, the process involves checking whether the bug exists in the Helix ALM environment. If not, a new entry is created. Subsequently, the software teams receive a notification with the BugID from Helix, prompting developers to verify and replicate the issue in Azure. The bug is then assigned to developers for resolution. After implementing the solution, it undergoes testing by the QA team. If the testing reveals issues or introduces new problems, the bug is returned to the developers for further refinement. This iterative cycle continues until the solution is thoroughly tested. Once the Software Development team deems the bug is resolved, it is marked as completed in Azure, and the progress is updated in Helix ALM. Finally, the service desk is notified of the completed resolution.
Results
After executing our research we analyzed the different possibilities of technologies and practices our solution might use. In the end our solution shows how a proof of concept would function.
About the project group
We're doing the Advanced Software semester 6.
We are in class RB01, group 4.
