| Gabriel, Richard P. Patterns of Software: Tales from the software community. OUP, 1996. |
....languages. Traditionally flooded with technical content, the course has been redesigned to include case studies of practitioner s lives. There are several biographies and essays available that describe the lives of computer scientists who could be classified as programming language experts [7, 8, 9, 10]. Some of them have been designers of prominent programming languages, while some have led commercial ventures based on programming language products. Thus, a human element is included in the course without necessarily sacrificing the technical matter. Other so called technical courses in computer ....
Gabriel, Richard P., Patterns of Software: Tales from the software community . Oxford: Oxford University Press, 1996.
....approaches, shearing layers, software design, social theory, systems thinking. 1. A RESPONSE TO ALEXANDER S CRITICISM In his keynote speech at OOPSLA 96, architect Christopher Alexander invited because of the extent to which his work was being cited within the OO design patterns community [19,20] made the following observation: Please forgive me. I m going to be very directly blunt for a horrible second. But it could be viewed that the technical way in which you [software designers and theorists] look at programming at the moment is almost like guns for hire. In other words, ....
Richard P Gabriel. Patterns of Software: tales from the software community. Oxford University Press, 1996.
.... In other words, there are several kinds of objects (or, more typically, structures of objects) that are common in the worlds we wish to model, but that cannot be translated directly into objectoriented designs perhaps due to weaknesses or non orthogonality in programming or modelling languages [7, 11]. To give a couple of simple examples: modelling languages such as UML support multi directional, multi place relationships between objects that can be used metaphorically (and directly) to model re lationships in the real world. In a university course database, for example, the relationship ....
Richard P. Gabriel. Patterns of Software: Tales from the Software Community. Oxford University Press, 1996.
....in the planning and feature estimation part of our development process. Our team has become noticeably more courageous, more collaborative and more open. We can thus see our meetings, in whatever format, as a generative process a process that produces the generated quality indirectly [3]. Meeting together every week to invent and to experiment with practices of our own design has changed us as a team. We have not only gotten better at designing and carrying out these practices, we have become closer and more capable as a team. These benefits cannot be attributed solely to our ....
Gabriel, Richard P. Patterns of Software: Tales from the Software Community (New York, NY, 1996), Oxford University Press, 50.
....by the continual increase in software. Programming languages over time have grown in abstractness, expressiveness, and portability. The intended effect is what Richard Gabriel calls compactness the ability to express an idea in a smaller number of lines than in previous, lower level languages [26]. These characteristics force implementations toward dynamic solutions. For example, in object oriented programs, binding of specific instances to specific implementations is done at runtime. Similarly, in programs written in functional programming languages, direct jumps to routines cannot be ....
Richard P. Gabriel. Patterns of Software: Tales from the Software Community. Oxford University Press, 1996.
....RFPs would be documented with a set of patterns. Such designs take less time to complete. They are shorter and easier to understand. They are also reusable. The time saved could be used to justify the design choices and provide a solid set of use cases. To end with the words of Richard Gabriel [Gab96] The promise of object oriented programming and of programming languages themselves has yet to be fulfilled. To some degree, this failure can be attributed to a failure of the design methodologies we have used to guide our design of languages, and to a larger degree to our ....
Richard P. Gabriel. Patterns of Software---Tales from the Software Community. Oxford University Press, 1996.
....based on active objects. Thus, by using terms defined by Christopher Alexander [Ale 75] and highlighted by Richard Gabriel 13 We therefore use hierarchic parameterization of the architecture, i.e. decomposing further parameter methods as needed within the hierarchy, as discussed in [Bri 94] Gab 96] we could say that although the 94 framework provided more extensive and systematic modeling abilities, habitability and piecemeal growth was better achieved for the first lighter version of Actalk. 6.3 Related Work The pros of building object oriented (and more specifically ....
R.P. Gabriel, "Patterns of Software - Tales from the Software Community," Oxford University Press, 1996.
.... a short summary, a context, a problem statement (that includes a description of its forces) a solution statement (which covers descriptions of its structure, participants, basic dynamics and implementation steps) known uses and consequences (describing benefits and liabilities of the pattern) [1,4,5]. These elements provide a uniform template for writing and browsing pattern descriptions contained in a pattern system, making it easy to look for and find information about when and how to use each pattern. 3. Classification of Architectural Patterns for Parallel Programming Architectural ....
Richard Gabriel. Patterns of Software: Tales from the Software Community. Oxford University Press, 1996.
No context found.
Gabriel, Richard P. Patterns of Software: Tales from the software community. OUP, 1996.
No context found.
Richard P. Gabriel. Patterns of Software: Tales from the Software Community. Oxford University Press, 1996.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC