Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for mixed or messed up component exchange contexts #83

Open
vik378 opened this issue Apr 11, 2024 · 0 comments · May be fixed by #111
Open

Add support for mixed or messed up component exchange contexts #83

vik378 opened this issue Apr 11, 2024 · 0 comments · May be fixed by #111
Assignees

Comments

@vik378
Copy link
Member

vik378 commented Apr 11, 2024

  • Scenario1:

    • There is a component exchange CEX1 between 2 LCs, LC1 and LC2
    • LC1 has a function F1
    • LC2 has functions F2
    • LC2 has function F4 that is a child of F2
    • F1 has functional exchange FEX1 with F4
    • FEX1 is allocated to CEX1

    Expectation:

    • LC1 and LC2 are shown
    • F1 and F4 are shown with FEX1 in between
    • F1 is shown inside of LC1
    • F4 is shown inside of LC2
  • Scenario2:

    • There is a component exchange CEX1 between 2 LCs, LC1 and LC2
    • LC1 has a function F1, F5
    • LC2 has functions F2
    • LC2 has function F4 that is a child of F2
    • F1 has functional exchange FEX1 with F4
    • F5 has functional exchange FEX2 with F2
    • FEX1 is allocated to CEX1

    Expectation:
    something like this but with blue boxes around the green boxes
    image

  • Scenario3:

    • There is a component exchange CEX1 between 2 LCs, LC1 and LC2
    • There is LC3
    • LC1 had F1 but not anymore
    • LC3 has F1
    • LC2 has functions F2
    • F1 has functional exchange FEX1 with F2
    • FEX1 is still allocated to CEX1 even though the source/target F1 was moved away to another component, Capella did not clean up the old and now erroneous allocation
@huyenngn huyenngn self-assigned this Jun 19, 2024
@huyenngn huyenngn linked a pull request Jun 19, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants