Role-oriented programming as a form ofcomputer programming aims at expressing things in terms that are analogous to humanconceptual understanding of theworld. This should make programs easier to understand and maintain.[citation needed]
The main idea of role-oriented programming is that humans think in terms ofroles. This claim is often backed up by examples ofsocial 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 thedelegation mechanism.
In the older literature and in the field ofdatabases, 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- andaspect-oriented programming languages such asObject 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" inWindows Server jargon.[1]
Many[quantify] researchers have argued the advantages of roles inmodeling and implementation. Roles allow objects to evolve over time, they enable independent andconcurrently 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 inreal life - things change over time, are used differently in different contexts, etc.
[...] 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.
Thiscomputer-programming-related article is astub. You can help Wikipedia byadding missing information. |