Thomas,
I do understand what they are used for. My problem is, how does EA figures out whether I'm using a business class or a "sofware" class?
For when introducing new stereotypes, one has either to choose, either to define the stereotype on both classes (which are pretty much, stereotypes by themselves alread -:)
By the way, I do use the boundary-control-entity stuff only on software analysis. Obviously, any system description, including business systems, could be described that way. For a number of reasons, I prefer classical business modeling the depict businesses, with use cases in support of processes, leading to the MVC view in functional analysis. All this with a pretty much component based mind set.
For the latter delivers sound and universal organisation principles one can weave throughout the whole study from business to operations.