fix(examples): replace illegal Assignment relationships with Composition/Serving/Realization#76
Merged
Merged
Conversation
…ion/Serving/Realization For each removed Assignment violation, adds the semantically correct replacement: - SystemSoftware/Device → Node → Composition (Node ◆→ SW) - SW → SW → Composition (host ◆→ guest) - ApplicationComponent → SystemSoftware → Serving (SW → AppComp) - ApplicationComponent → Node (direct) → Serving (Node → AppComp) - TechnologyService → Node → Realization (Node →→ Service) 57 replacements in archimetal-extended.xml, 39 in archisurance-extended.xml. The one remaining Assignment (Grouping→TechnologyProcess, diagram-referenced) is intentionally left pending a manual redesign of that diagram.
Deploying archipulse with
|
| Latest commit: |
130c96e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6908bd39.archipulse.pages.dev |
| Branch Preview URL: | https://fix-technology-stack-relatio.archipulse.pages.dev |
…ix query The query only recognized Assignment/Realization as app-tech links. After replacing illegal Assignment relationships with Serving (Tech→App) and Composition, the matrix returned zero matches. Now includes all four valid relationship types that connect Application and Technology layers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces the 57+39 Assignment relationships removed in #75 with semantically correct ArchiMate 3.1 alternatives, restoring the Technology Stack information in both extended models.
Replacement logic
SystemSoftware → Node(Assignment)Composition(Node ◆→ SW)SW → SW(Assignment)Composition(host ◆→ guest)ApplicationComponent → SystemSoftware(Assignment)Serving(SW → AppComp)ApplicationComponent → Nodedirecto (Assignment)Serving(Node → AppComp)TechnologyService → Node(Assignment)Realization(Node →→ Service)Estado tras el cambio
Grouping→TechnologyProcess, referenciado en diagrama) se mantiene intencionalmente pendiente de rediseño manualTest plan
archimetal-extended.xmlen Archi — sin errores de relaciones ilegalesarchisurance-extended.xmlen Archi — sin errores de relaciones ilegalesgo test ./internal/parser/... ./internal/exporter/...pasa🤖 Generated with Claude Code