Comments (3)
I was able to implement:
• Model.la.all_functional_chains is not implemented
• Model.la.all_component_exchanges[x].Kind == [UNSET | ASSEMBLY | DELEGATION | FLOW] missing
• Model.la.all_functions[x].Kind == [DUPLICATE | FUNCTION | SPLIT | ROUTE | SELECT | GATHER] missing
The others are a bit unclear for me. In FunctionalChain diagrams one is able to describe the FunctionalChain with Functions, Exchanges, ControlNodes and SequenceLinks. One can reference other chains, but there is no nesting. What can be achieved is to create a new FunctionalChain underneath the existing Chain. But I don't see how this is then an involvement. Usually Capella manages involvements via an extra dummy XML element. Then how can you involve Components here? And last: what is the difference between involved and involving?
Cheers
from py-capellambse.
I need to look into the comment further, but quick answer to the last question: involved / involving are the two different directions of the relationship.
Heating water is involved in making coffee
Making coffee involves heating water
It is clearer for realized/ realizing or deployed/ deploying for me tbh.
Thanks for the support, cheers
from py-capellambse.
I was able to implement: • Model.la.all_functional_chains is not implemented • Model.la.all_component_exchanges[x].Kind == [UNSET | ASSEMBLY | DELEGATION | FLOW] missing • Model.la.all_functions[x].Kind == [DUPLICATE | FUNCTION | SPLIT | ROUTE | SELECT | GATHER] missing
The others are a bit unclear for me. In FunctionalChain diagrams one is able to describe the FunctionalChain with Functions, Exchanges, ControlNodes and SequenceLinks. One can reference other chains, but there is no nesting. What can be achieved is to create a new FunctionalChain underneath the existing Chain. But I don't see how this is then an involvement. Usually Capella manages involvements via an extra dummy XML element. Then how can you involve Components here? And last: what is the difference between involved and involving?
Cheers
Let me try to answer your questions.
"One can reference other chains, but there is no nesting."
This is correct and what was meant here. When I understand it correctly this is modelled inside Capella as 'Functional Chain Reference'. The term nesting was not really correct when phrasing the problem.
"Usually Capella manages involvements via an extra dummy XML element. Then how can you involve Components here?"
Here I can't help. I have no knowledge about the XML representation of the model.
"And last: what is the difference between involved and involving?"
These terms just refer to the two directions you can look at a functional chain involvement by another functional chain. It is comparable with the parent - owned component relation that exists for logical components.
involved: one functional chain B can involve (make use of) several other functional chains (A, D)) and hence are visible within the LFCD for functional chain B. This property gives a list of all functional chains (A,D) that are used (involved) in one functional chain B.
involving: one functional chain A can be involved by several other functional chains B/C, which means it is visible in several different LFCDs (one for B and one for C). This property gives a list of all functional chains (B,C) that involve functional chain A.
B involves A
B involves D
A is involved by B
D is involved by B
C involves A
A is involved by C
I hope this helps a little.
from py-capellambse.
Related Issues (20)
- Broken diagram SVG in documentation HOT 2
- PA demo notebook uses private `_filter` method (and fails)
- Missing Physical Path,Physical Link and component icons in generated images HOT 3
- Missing unconnected comments in generated images HOT 4
- Collapse Component Physical Ports makes edges dissapear
- Cannot save back to Git if revision wasn't passed in explicitly
- Additional model arguments are silently ignored when passing a FileHandler object as "path"
- CSA - Missing connectors and actor symbols between Actors and System
- `capellacommon.State.functions` always empty (model.search broken?) HOT 1
- Error: FIP/FOPSymbol wasn't found in factories HOT 1
- Distance between icon and label text is not uniform
- Diagram UUID inconsistent with Capella GUI HOT 1
- Declarative modelling : Problems when declaring new functions / components HOT 4
- Capella model loading failure due to Duplicate UUID HOT 4
- Model.save() breaks the model even without modifying anything HOT 1
- Functional chains (and other objects) not in order
- Automatic namespace management sometimes removes needed namespaces
- Enhancement of State / Mode objects
- Committing to Git sometimes fails with "object is unavailable"
- Support filtering of model elements with FilterCriterions during diagram export
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from py-capellambse.