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.

Sign up for GitHub

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

Jump to bottom

list versus cardinality #4

Open
elsdvlee opened this issue Dec 15, 2021 · 1 comment
Open

list versus cardinality #4

elsdvlee opened this issue Dec 15, 2021 · 1 comment

Comments

@elsdvlee
Copy link

Is it needed to have a list symbol , if there is also a cardinality specified?
Is the list symbol used?

example:
class SupplierLocation {
@type scro:StorageFacility

Customer[] servableCustomers sc:servableCustomer

}

SupplierLocation -- "0..*" Customer

Customer[] vs "0..*" Customer
@pheyvaer
Copy link
Contributor

It's only used in the diagram at the moment. In other words is coming from the UML spec. It's not used for our processing. So in theory it can be removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pheyvaer @elsdvlee