Role-oriented programming: Difference between revisions

Revision as of 12:48, 1 December 2010

Revision as of 20:34, 19 July 2011

Line 3:

'''Role-oriented programming''' is a form of [[programming language|computer programming]] aimed at expressing things in terms which are analogous to our [[concept]]ual understanding of the world. This should make programs easier to understand and maintain.

The main idea of role-oriented programming is that humans think in terms of [[role]]s. This claim is often backed up by examples of [[social relations]]. For example, a student attending a class and the same student at a party are the same person, but yet he plays in two different roles. In particular, the interactions of this person with the outside world depends on his current role. The roles typically share features, e.g., the intrinsic properties of being a person. This sharing of properties is often handled by the [[Delegation_(programming)|delegation]] mechanism.

In the older literature and in the field of [[databases]], it seems that there has been little consideration for the context in which roles interplay with each other. Such a context is being established in newer role- and [[aspect-oriented programming|aspect-]]oriented programming languages such as Object Teams [http://www.objectteams.org/].