static class in relationship diagram
Hi all,
I'm in the final tedious stages of the final year project for my degree, and need to express in a relationship diagram that my class 'Node' contains a static instance of another class 'Board'.
I've never seen this expressed in a diagram before, how is this done? Did some googling and couldn't find out either, for a static member within a UML diagram of a single class you just underline the attribute that is static, but I'm talking about representing it graphically in a relationship diagram which doesn't show information about members of each specific class, just how they interact, i.e. composition/inheritance etc
Also, I wasn't sure whether to put this in general of lounge since it's not technically about c++, but meh.
Thanks.
I'm in the final tedious stages of the final year project for my degree, and need to express in a relationship diagram that my class 'Node' contains a static instance of another class 'Board'.
I've never seen this expressed in a diagram before, how is this done? Did some googling and couldn't find out either, for a static member within a UML diagram of a single class you just underline the attribute that is static, but I'm talking about representing it graphically in a relationship diagram which doesn't show information about members of each specific class, just how they interact, i.e. composition/inheritance etc
Also, I wasn't sure whether to put this in general of lounge since it's not technically about c++, but meh.
Thanks.
Reminds me of my Systems Analysis and Design course.
UML diagram sounds familiar hmmm..... the real "world" taught me whatever diagrams I have written will be "obsolete" in matter of months or even weeks!!!!! Reason being my employer business logic is very dynamic and changes based on situations/competitor strategies etc. Very often we spend a lot of time developing and not much time allocated to update those diagrams. It is not efficient to update a UML only to update again a few weeks later isn't it?
I am employed as an in-house developer so employer squeezes every ounce out of me. And for me, the most updated "diagrams" is in the source code itself as it is already running to deliver the most current business logic to the users.
I believe if you work in vendor companies, UML diagrams will hold a higher priority cuz it is part of the set of deliverables to the client and charges monies.
So once again, academic teaches one way but in reality depending on where you work, you cannot apply it effectively isn't it? :P
UML diagram sounds familiar hmmm..... the real "world" taught me whatever diagrams I have written will be "obsolete" in matter of months or even weeks!!!!! Reason being my employer business logic is very dynamic and changes based on situations/competitor strategies etc. Very often we spend a lot of time developing and not much time allocated to update those diagrams. It is not efficient to update a UML only to update again a few weeks later isn't it?
I am employed as an in-house developer so employer squeezes every ounce out of me. And for me, the most updated "diagrams" is in the source code itself as it is already running to deliver the most current business logic to the users.
I believe if you work in vendor companies, UML diagrams will hold a higher priority cuz it is part of the set of deliverables to the client and charges monies.
So once again, academic teaches one way but in reality depending on where you work, you cannot apply it effectively isn't it? :P
ok...yeah I don't like UML diagrams either but I need to do some for this project, and that didn't really answer my question.
Topic archived. No new replies allowed.