Hi There, after playing around quite a lot with AI, MCP and different extensions inside Polarion, I wanted to try something slightly different. Instead of building another isolated AI Use Case, I wanted to connect several of them. The question was basically: What happens if AI does not only support one individual engineering activity, butContinue reading “From Meeting Notes to Risk – Building an AI-Supported Change Process in Polarion”
Tag Archives: V-Model
TracePilot – Bringing AI Agents into Polarion
Hi there, during the last weeks I spent quite some time experimenting with Polarion, MCP and AI Agents.There was no big product plan at the beginning. I was simply curious: What can we actually achieve when an AI Agent gets access to Polarion through an MCP server? Not only access to a few exported Requirements.Continue reading “TracePilot – Bringing AI Agents into Polarion”
SYS.4 – System Integration and Integration Verification (A-SPICE 4.0)
SYS.4 System Integration and Integration Verification – focuses on brining all system elements together and ensuring they work as intended. It verifies that interfaces, data flows and interactions align with the system architecture and meet release expectations. This process ensures integration issues are detected early, traceability is maintained and clear results are communicated to stakeholders,Continue reading “SYS.4 – System Integration and Integration Verification (A-SPICE 4.0)”
SWE.5 – Software Integration and Integration test
Hi everyone,its time to continue the A-SPICE series with the upcoming SWE.5 process. Last time we had a look onto the SWE.4 – Software Unit Verification process. ID: SWE.5Process name: Software Integration and Integration TestProcess purpose: The goal of the process for software integration and integration testing is to combine individual software units into largerContinue reading “SWE.5 – Software Integration and Integration test”
SWE.3 – Software Detailed Design and Unit Construction
Welcome,to my series about A-SPICE and its related processes. Today we want to take a deeper look into SWE.3 – Software Detailed Design. In the last post we covered the software architectural design and prepared all relevant project development data for this process. Shall we begin? ID: SWE.3Process name: Software Detailed Design and Unit ConstructionProcessContinue reading “SWE.3 – Software Detailed Design and Unit Construction”
SWE.2 – Software Architectural Design
Hi there,hope you´re doing well. I would like to continue today with our A-SPICE series. Todays scope will focus on the SWE.2 – Software Architectural Design process. Previously we had a closer look onto SWE.1 – Software Requirements Analysis, which provides us the relevant information for this process. Let´s go!! Lets get started ID: SWE.2ProcessContinue reading “SWE.2 – Software Architectural Design”
A-SPICE – the journey continues
Hi there, It´s NotDenis again. Welcome back to my series of A-SPICE related thoughts and findings. In case you find it hard to understand the content here, try reading my first post. It should explain all the basics, so its easier for you to follow.First post What do we know so far? In our lastContinue reading “A-SPICE – the journey continues”
A-SPICE – start of a journey
Hi there, I´m NotDenis and I want to welcome you on my first blog post ever. Why am I doing this?In my job I often encounter the challenge of fulfilling or understanding a ISO/norm. And I must say. Its not a easy task! Often I hear terms like ISO26262, A-SPICE etc. But what does thisContinue reading “A-SPICE – start of a journey”
The Polarion Blog 