Role-oriented programming
Role-oriented programming as a form of computer programming aims at expressing things in terms that are analogous to human conceptual 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 roles. 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, yet that person plays two different roles. In particular, the interactions of this person with the outside world depend 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 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 languages such as Object Teams. Compare the use of "role" as "a set of software programs (services) that enable a server to perform specific functions for users or computers on the network" in Windows Server jargon. Many researchers have argued the advantages of roles in modeling and implementation. Roles allow objects to evolve over time, they enable independent and concurrently existing views (interfaces) of the object, explicating the different contexts of the object, and separating concerns. Generally roles are a natural element of human daily concept-forming. Roles in programming languages enable objects to have changing interfaces, as we see in real life - things change over time, are used differently in different contexts, etc.
Role-oriented programming as a form of computer programming aims at expressing things in terms that are analogous to human conceptual understanding of the world. This should make programs easier to understand and maintain.[citation needed]
The main idea of role-oriented programming is that humans think in terms of roles. 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, yet that person plays two different roles. In particular, the interactions of this person with the outside world depend 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 mechanism.
In the older literature and in the field of databases, it seems[original research?] 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 languages such as Object Teams. Compare the use of "role" as "a set of software programs (services) that enable a server to perform specific functions for users or computers on the network" in Windows Server jargon.[1]
Many[quantify] researchers have argued the advantages of roles in modeling and implementation. Roles allow objects to evolve over time, they enable independent and concurrently existing views (interfaces) of the object, explicating the different contexts of the object, and separating concerns. Generally roles are a natural element of human daily concept-forming. Roles in programming languages enable objects to have changing interfaces, as we see in real life - things change over time, are used differently in different contexts, etc.
Authors of role literature
[edit]- Barbara Pernici
- Bent Bruun Kristensen[2]
- Bruce Wallace
- Charles Bachman[3]
- Friedrich Steimann
- Georg Gottlob
- Kasper B. Graversen
- Kasper Østerbye
- Stephan Herrmann
- Trygve Reenskaug[4]
- Thomas Kühn
Programming languages with explicit support for roles
[edit]- Cameleon
- EpsilonJ
- JavaScript Delegation - Functions as Roles (Traits and Mixins)
- Object Teams
- Perl (Moose)
- Raku
- powerJava
- SCala ROLes Language
See also
[edit]- Aspect-oriented programming
- Data, context and interaction
- Object Oriented Role Analysis Method
- Object-role modeling
- Subject (programming)
- Subject-oriented programming
- Traits (computer science)
References
[edit]- ^ Carpenter, Tom (July 18, 2011). Microsoft Windows Server Administration Essentials. Sybex Serious Skills. Indianapolis: John Wiley & Sons (published 2011). p. 9. ISBN 9781118148693. Retrieved March 7, 2018.
[...] a server role is a set of software programs (services) that enable a server to perform specific functions for users or computers on the network.
- ^ "DBLP: Bent Bruun Kristensen". Archived from the original on September 27, 2007.
- ^ "Computer History Museum - Lectures - Charles W. (Charlie) Bachman". Archived from the original on January 3, 2013. Retrieved January 3, 2013.
- ^ "dblp: Trygve Reenskaug".
External links
[edit]- Adaptive Plug-and-Play Components for Evolutionary Software Development, by Mira Mezini and Karl Lieberherr
- Context Aspect Sensitive Services
- Overview and taxonomy of Role languages
- ROPE: Role Oriented Programming Environment for Multiagent Systems
 | This computer-programming-related article is a stub. You can help Wikipedia by adding missing information. |