Just to make sure we are all on the same page, here is a simple example of what I am thinking. Suppose you are building an Order Entry System. In the class model, I would expect to see packages like: Customer, Product, Order, Shipping, etc. Each package would have several classes that are included. They would also contain references to classes from other packages. For example, the Order package may have an Order and Order Line Item classes included in it. It would have references to Customer and Product classes.
In the component model, the structure would be more aligned to implementation architecture. There could be a package for the Presentation tier, the Business tier, and the Data tier. Components in these tiers could realize classes from many of the packages described above.
In essence, what I am looking for is that the relationship between components and classes will represent the transition from the business realm to the technical realm.
For me, this seems like an intuitive interpretation of UML. I am not sure why Sparx has not implemented this capability in EA.
The example above is overly simplified. For any large real world application, with many people on each team, the issues become far more complicated.
Take Care
