I am new to UML and I have a best practices question. I would like to model separately:
- logical architecture: logically interconnected software components;
- physical architecture: physical installations of operating systems with possibility of physical interconnections like Ethernet;
- mapping of one to another, modelled as the last step which does not modify models of the above two architectures.
For example, an engineer can decide, that software components App1 and App2 should both be installed on operating system Linux1, and communicate using sockets. Within this process of mapping, it is not allowed to modify the logical and physical architecture models, only a respective third model should be produced. The two former models need to be read-only, as any number of independent mappings is possible.
This all should be modelled in UML 2. I can imagine the logical architecture as a communication diagram, the physical architecture as a deployment diagram. What I do not known is how to link these using a mappings in question, so that it is easy and intuitive for the engineer (so to avoid documentation rust), and also following the current best practices.
Can all this be realised in a generic UML drawing software like UMLet or MagicDraw?