Role-oriented programming: Difference between revisions

Content deleted Content added
Soir (talk | contribs)
wikify
m Bot: http → https
 
(67 intermediate revisions by 47 users not shown)
Line 1:
{{Short description|Programming paradigm based on conceptual understanding of objects}}
{{wikify}}
{{Use mdy dates|date=January 2019}}
The main inspiration for role-oriented programming is to make programming languages similar to the human conceptual understanding of the world. Role-Oriented Programming is an attempt to make programs be expressed in the same terms as our conceptual understanding of the world. The hypothesis is that this should make programs easier to understand and maintain. Humans think in terms of roles. This claim is often backed up by examples of social relations. Typically the examples are given where a person is attending a conference and being a reviewer or a person being a student at an educational institution. A person being a student and being at a party is in a way the same person. But in a way it is not the same person, the interactions with the person will be different. Typically this in the theory of human sciences so that the person plays the role of being a student and being an attendee at a party. Typically the two roles share commonality---the intrinsic properties of being a person. This sharing of properties is often handled by the [[delegation]] mechanism.
{{Use American English|date=January 2019}}
 
'''Role-oriented programming''' as a form of [[programming language|computer programming]] aims at expressing things in terms that are analogous to human [[concept]]ual understanding of the [[world]]. This should make programs easier to understand and maintain.{{citation needed|date= August 2016}}
Much research has been carried out in the field of role-oriented programming. 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 PyMeleon and Object Teams.
 
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 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_(programming)|delegation]] mechanism.
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
our 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.
 
Much research has been carried out in the field of role-oriented programming. In the older literature and in the field of databases[[database]]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]] languages such as PyMeleon and [[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
Authors of role literature
| 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 [[computer 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 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.
* Reenskaug
 
* Gottlob
==Authors of role literature==
* B. B. Kristensen
* [http://www.informatik.uni-trier.de/~ley/db/indices/a-tree/p/Pernici%3ABarbara.html Barbara Pernici]
* K. Østerbye
* [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>
* Friedrich Steimann
* [https://existentialprogramming.blogspot.com/search/label/roles Bruce Wallace]
* Stephan Herrmann
* [[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>
* Pernici
* [http://www.kbs.uni-hannover.de/~steimann/ Friedrich Steimann]
* K. Graversen
* [http://www.informatik.uni-trier.de/~ley/db/indices/a-tree/g/Gottlob%3AGeorg.html Georg Gottlob]
* [https://www.itu.dk/people/kbilsted/ Kasper B. Graversen]
* [https://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]]
* [https://www.eclipse.org/epsilon/ EpsilonJ]
* [[JavaScript#Delegative|JavaScript Delegation - Functions as Roles (Traits and Mixins)]]
* [https://www.eclipse.org/objectteams Object Teams]
* [[Moose (Perl)#Roles|Perl (Moose)]]
* [[Raku (programming language)#Roles|Raku]]
* [http://portal.acm.org/citation.cfm?id=1141277.1141606 powerJava]
* [https://github.com/max-leuthaeuser/SCROLL SCala ROLes Language]
 
==See also==
* [[Aspect-oriented programming]]
* [[Data, context and interaction]]
* [[Object Oriented Role Analysis Method]]
* [[Object-role modeling]]
* [[Subject (programming)]]
* [[Subject-oriented programming]]
* [[Traits (computer science)]]
 
==References==
{{reflist|30em}}
 
==External links==
* [https://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]
* [https://www.itu.dk/people/kbilsted/graversen06thesis.pdf Overview and taxonomy of Role languages]
* [https://doi.ieeecomputersociety.org/10.1109/COOPIS.1999.792181 ROPE: Role Oriented Programming Environment for Multiagent Systems]
 
{{Programming paradigms navbox}}
{{compu-prog-stub}}
 
[[Category:Object-based programming languages]]
[[Category:Programming paradigms]]