architecture - component diagram advice framework -


i've been tasked documenting our high-level software architecture uses in-house developed framework robotics (similar ros.) i'll try , keep simple.

in component diagram, how represent component instantiated class loader (based on type specified in xml file) in base framework application provided , ran in separate thread? component implements , instantiates services provided framework (i.e network communications.)

you can use <<instantiate>> relation in example taken uml 2.5 specs on p. 39:

in figure 7.19, carfactory class has dependency on car class. in case, dependency usage standard stereotype «instantiate» applied, indicating instance of carfactory class creates instances of car class.

enter image description here

note omg uses "artistic" arrow end (they not consistent in documentation should be). simple open triangle used more commonly. on p. 39:

a dependency shown dashed arrow between 2 model elements. model element @ tail of arrow (the client) depends on model element @ arrowhead (the supplier). arrow may labeled optional keyword or stereotype , optional name...

the line use resembles more dotted dashed line, though. sigh.


Comments

Popular posts from this blog

Is there a better way to structure post methods in Class Based Views -

performance - Why is XCHG reg, reg a 3 micro-op instruction on modern Intel architectures? -

jquery - Responsive Navbar with Sub Navbar -