In Perspectives an Action has a Subject (Role) and an Object (Role). The first is the Agent that executes, or better is permitted to execute, the Action. In Object Oriented (OO) Analysis and Design there is not such a Subject Role. All behaviour, both calculations and control are distributed among the Objects.
OO lacks the notion of Agency. In other words: in OO modelling the question of  "Who" performs or requests behaviour is never asked. Let alone the question of who is permitted to do so. This means that the role of the user, as one of the possible Actors is not modelled intrinsically and will be an afterthought.
Moreover, OO lacks the notion of Context. This means that in OO it is not possible to modularise object behaviour other than that of the classes that define them.
Finally, OO lacks the notion of Role. Role in the sense of a concept that has different state and behaviour in different contexts. Of course in UML we can model Association Classes as placeholders for role-attributes but this seems to be an exception more than a fundamental pattern as in Perspectives.
This is not to say that OO is inadequate or useless. It is just not suited for modelling Business processes and their consequences for Information Management. Together the notions of (permitted) Agency, Context and Roles are essential in modelling business domains and the behaviour of Actors in these domains.