Role-oriented programming: Difference between revisions

Revision as of 16:28, 4 March 2015

Latest revision as of 11:01, 8 August 2025

(21 intermediate revisions by 16 users not shown)

Line 1:

{{Short description|Programming paradigm based on conceptual understanding of objects}}

{{Programming paradigms}}

{{Use mdy dates|date=January 2019}}

{{Use American English|date=January 2019}}

'''Role-oriented programming''' isas a form of [[programming language|computer programming]] aimedaims at expressing things in terms that are analogous to human [[concept]]ual understanding of the World[[world]]. This should make programs easier to understand and maintain.{{citation needed|date= August 2016}}

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, yet hethat 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_(programming)|delegation]] mechanism.

In the older literature and in the field of [[databasesdatabase]]s, it seems{{or|date=March 2018}} 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]]. 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.<ref>{{cite book

| last1 = Carpenter

| first1 = Tom

| title = Microsoft Windows Server Administration Essentials

| url = https://books.google.com/books?id=6_mmL45Zw0IC

| series = Sybex Serious Skills

| date = July 18, 2011

| ___location = Indianapolis

| publisher = John Wiley & Sons

| publication-date = 2011

| page = 9

| isbn = 9781118148693

| access-date = 2018-03-07

| quote = [...] 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.}}</ref>

Many{{quantify|date=March 2018}} researchers have argued the advantages of roles in [[Computercomputer model|modeling]] and implementation. Roles allow objects to evolve over time, they enable independent and [[Concurrency (computer science)|concurrently]] existing views (interfaces) of the object, explicating the different contexts of the object, and [[separation of concerns | separating concerns]]. Generally roles are a natural element of ourhuman daily concept -forming. Roles in programming languages enable objects to have changing interfaces, as we see it in [[real life]] - things change over time, are used differently in different contexts, etc.

==Authors of role literature==

* [http://www.informatik.uni-trier.de/~ley/db/indices/a-tree/p/Pernici%3ABarbara.html Barbara Pernici]

* [http://www.mip.sdu.dk/people/Staff/bbk.html Bent Bruun Kristensen]<ref>{{cite web |url=http://www.sigmod.org/dblp/db/indices/a-tree/k/Kristensen%3ABent_Bruun.html |url-status=dead |archive-url=https://web.archive.org/web/20070927210129/http://www.sigmod.org/dblp/db/indices/a-tree/k/Kristensen:Bent_Bruun.html |archive-date=September 27, 2007 |title=DBLP: Bent Bruun Kristensen}}</ref>

* [httphttps://existentialprogramming.blogspot.com/search/label/roles Bruce Wallace]

* [[Charles Bachman]]<ref>{{cite web |url=http://www.computerhistory.org/events/lectures/bachman_04162002/bachman.shtml |title=Computer History Museum - Lectures - Charles W. (Charlie) Bachman |access-date=2013-01-03 |url-status=dead |archive-url=https://web.archive.org/web/20130103023948/http://www.computerhistory.org/events/lectures/bachman_04162002/bachman.shtml |archive-date=2013-01-03 }}</ref>

* [http://www.kbs.uni-hannover.de/~steimann/ Friedrich Steimann]

* [http://www.informatik.uni-trier.de/~ley/db/indices/a-tree/g/Gottlob%3AGeorg.html Georg Gottlob]

* [httphttps://www.itu.dk/people/kbilsted/ Kasper B. Graversen]

* [httphttps://www.itu.dk/people/kasper/ Kasper Østerbye]

* [http://www.informatik.uni-trier.de/~ley/db/indices/a-tree/h/Herrmann%3AStephan.html Stephan Herrmann]

* [[Trygve Reenskaug]]<ref>{{cite web |url=http://www.informatik.uni-trier.de/~ley/db/indices/a-tree/r/Reenskaug%3ATrygve.html |title = dblp: Trygve Reenskaug}}</ref>

* [https://wwwpub.zih.tu-dresden.de/~s4560758/ Thomas Kühn]

==Programming languages with explicit support for roles==

* [[Cameleon_(programming_language)|Cameleon]]

* [http://www.itu.dk/~kbilsted/chameleon.html Chameleon]

* [httphttps://www.gracoeclipse.c.u-tokyo.ac.jporg/~tamaiepsilon/epsilon.html EpsilonJ]

* [[JavaScript#Implicit_and_explicit_delegationDelegative|JavaScript Delegation - Functions as Roles (Traits and Mixins)]]

* [httphttps://www.eclipse.org/objectteams Object Teams]

* [[Moose (Perl)#Roles|Perl 5 (Moose)]]

* [[PerlRaku 6(programming language)#Roles|Perl 6Raku]]

* [http://portal.acm.org/citation.cfm?id=1141277.1141606 powerJava]

* [https://github.com/max-leuthaeuser/SCROLL SCala ROLes Language]

==References==

<references/>

==See also==

Line 41 ⟶ 55:

* [[Subject-oriented programming]]

* [[Traits (computer science)]]

==References==

{{reflist|30em}}

==External links==

* [ftphttps://web.archive.org/web/20060910101027/http://ftp.ccs.neu.edu/pub/people/lieber/appcs.pdf Adaptive Plug-and-Play Components for Evolutionary Software Development], by Mira Mezini and Karl Lieberherr

* [http://www.iit.edu/~concur/asc/cassservices.html Context Aspect Sensitive Services]

* [httphttps://www.itu.dk/people/kbilsted/graversen06thesis.pdf Overview and taxonomy of Role languages]

* [httphttps://doi.ieeecomputersociety.org/10.1109/COOPIS.1999.792181 ROPE: Role Oriented Programming Environment for Multiagent Systems]

{{Programming paradigms navbox}}

{{compu-prog-stub}}