Is Rhapsody's component use not according to UML standard?
This topic was discussed again and again: Why doesn't IBM Rhapsody behave exactly as the UML standard specifies when using component diagrams? Why can't I model components at architecture level with IBM Rhapsody?
The reason is quickly explained: IBM Rhapsody has mature and frequently used functions, that support the generation and further processing of source code from UML models. To make this as convenient as possible, component diagrams in IBM Rhapsody are used to define helpful supplementary parameters, that are necessary for the compile and build process to run smoothly. The below figure 1 shows an example.