|
|
Re: Reg Exp Layers by association to class (OCL) [message #1769871 is a reply to message #1769741] |
Fri, 04 August 2017 10:42 |
|
Hi André,
your approach is very common in the domains CAD, PCB design and other incarnations of graphical design. Different annotations of the design are separated using layers.
Well as written before both, CAD and PCB design is graphic design. Your drawings look very much like the product these represent. Given that, it is the natural approach using layers to annotate the drawings of the product.
With UML/SysML the diagrams in general do not represent something visible. The diagrams do not look like the products these represent. The level of abstraction is completely different. The approach Ed sketched in his post for me proved[1] much more powerful in the domain of systems engineering. So I advise you to follow this approach.
/Carsten
[1] based on my experience with BridgePoint (https://xtuml.org/) a systems engineering tool that, at the time I used it only supported the layer approach.
[Updated on: Fri, 04 August 2017 11:35] Report message to a moderator
|
|
|
Re: Reg Exp Layers by association to class (OCL) [message #1769960 is a reply to message #1769871] |
Mon, 07 August 2017 06:47 |
André Spindler Messages: 3 Registered: August 2017 |
Junior Member |
|
|
Allright, thank you. I can well follow your answers. Although what I am doing is also closely related to software development, I wasn't quite aware to be so totally in that world using UML. We are modeling something more "real", a facility structure. And we are, too, integrating different roles/views in that model. At this point all my classes have more or less direct associations in real live.
An example: "A box is an asset. An example of a box is a cardbox. Boxes are also geometric objects, for example cuboids which would make them rectangles in the horizontal projection. Boxes are storaging devices. A storaging devices has an empty volume, ... . Boxes can be made out of... ."
So there are some main classes/interfaces representing different views and everythin that is an asset can also take a role in each of the other views. For the development of the model I would have found it convenient to use the layering functionality but it is also, of course, possible to make a single model for each view.
Thanks again for your support.
André
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03947 seconds