INTRODUCTION Analysis Essay Example For Students

INTRODUCTION Analysis Essay How can 130 acres of resort nestle anywhere, especially in the heart of a thriving metropolis known as The Valley of the Sun?Yet, through the combination of landscaping and architecture, this slice of desert heaven does seem to discreetly nestle against Camelback Mountain, its sandstone terraces barely discernible. Even in the heart of Arizonas Sonoran desert, the well manicured landscaping is lush and mature, accented with a scenic cactus garden boasting 350 varieties of blooming succulents that attract colorful desert hummingbirds. Architecture is at once impressive and unobtrusive. The Phoenician Resort, a lavish stretch of desert chic, is home to 18 PGA-approved holes scattered across lush green fairways. The Resort boasts 580 elegant rooms, suites, and casitas; a lighted 11-court tennis complex; seven swimming pools; plus a Centre for Well Being that soothes and challenges body and soul. Restaurants cater to tastes ranging from Mediterranean Country to Southwestern Casual to traditional English tea. A skilled and attentive hotel staff provide impeccable guest service (Rice, 1994). The Phoenician also offers superb meeting facilities with 60,000 square feet of meeting space, a 22,000 square-foot grand ballroom, 21 conference rooms, and two boardrooms. A Business Center, an individualized Butler Program, as well as in-house Audio-Visual and Destination Services Departments cater to a groups and attendees every need. From the beginning, the Phoenician was envisioned as a resort that would combine the luxury of Europes top hostelries with the colors, textures, and ambiance of the Southwest. Since its opening in October, 1988, The Phoenician has attracted vacationers, business clientele, and notoriety from around the world. A lobby graced with imported Italian marble, Persian rugs, crystal chandeliers, soft carpets, deep couches, gold leaf detailing, and mile-high flower arrangements flown in from Europe and Hawaii (Davis, 1993) suggests more than an ordinary luxury hotel. Each of the Phoenicians luxurious guest room accommodations have a view, including the Resorts two 3,200-square-foot presidential suites that come complete with baby grand piano, gourmet kitchen, formal dining room, casual living room with fireplace, and 24-hour butler service. With Charles Keatings monogram erased from the middle of the stunning lobbys star burst-pattern marble floor, and in the hands of new owners Sheraton ITT, The Phoenician is an ode to success, not wretched excess (Reinman, 1994). What continues to make The Phoenician successful is its ability to carry out its simply stated goal: provide guests with unparalleled luxury service. Certainly, well refined organizational communication skills are necessary in order to accomplish this goal successfully. This portion of the observation plan focuses on the effectiveness of communication between the Resort and the customer in understanding the customers needs and expectations for a group function, as well as the effectiveness of communication between the Resort management and employees in successfully meeting the customers needs and expectations for a group function. Additionally, the observation plan looks at the forms of feedback received from customers after an event, which w!ould assist the Resort in providing continued superior service in future events. OBSERVATIONSPre-Conference MeetingFocusing on the written, verbal, and non-verbal communication within the Convention Services and Banquet Operations Departments, I attended a pre-conference meeting with the guest/group representatives of the International Association of Convention and Visitors Bureau (IACVB) and The Phoenician management. Each department affected by the scheduled event was represented, including both the Resort and General Manager. In a spacious, well pointed meeting room set up with water service, refreshments, writing tablets and pencils, hotel participants convened prior to the arrival of the guest/group representatives. Resort staff members resembled cast performers in a long running Broadway play, made up to appear larger than life in the production they were about to take part. Fashionably dressed in conservative business attire, well groomed, and with bright, attentive gazes, each participant arrived well versed with the Groups Resume, as well as the Time and Event Schedule for a!total of 182 individual events, each of which had been distributed to the departments prior to the pre-conference meeting. At the formal start of the meeting, Mr. Steve Therriault, Convention Services Manager, introduced Ms. Wendy Shapiro as the guest/group representative for the IACVB, and he introduced the local representative from the Phoenix Convention and Visitors Bureau. Ms. Shapiro profiled the IACVB as a global organization, representing more than 415 member bureaus in 28 countries. She related that the organization was founded in 1914 to promote sound professional practices in the solicitation and servicing of meetings, conventions, and tourism, and Ms. Shapiro characterized this years annual convention at The Phoenician as both an educational and social gathering of IACVB members. Americas Involvement In World War Two When War Broke Out , There Was EssaypSather differs from concurrent object-oriented languages that try to unify the notions of objects and processes by following the actors model 1. There can be a grave performance impact for the implicit synchronization this model imposes on threads even when they do not conflict. While allowing for actors, pSather treats object-orientation and parallelism as orthogonal concepts, explicitly exposing the synchronization with new language constructs. pSather follows the Sather philosophy of shielding programmers from common sources of bugs. One of the great difficulties of parallel programming is avoiding bugs introduced by incorrect synchronization. Such bugs cause completely erroneous values to be silently propagated, threads to be starved out of computational time, or programs to deadlock. They can be especially troublesome because they may only manifest themselves under timing conditions that rarely occur (race conditions) and may be sensitive enough that they dont appear when a program is instrumented for debugging (heisenbugs). pSather makes it easier to write deadlock and starvation free code by providing structured facilities for synchronization. A lock statement automatically performs unlocking when its body exits, even if this occurs under exceptional conditions. It automatically avoids deadlocks when multiple locks are used together. It also guarantees reasonable properties of fairness when several threads are contendi ng for the same lock. Data placementpSather allows the programmer to direct data placement. Machines do not need to have large latencies to make data placement important. Because processor speeds are outpacing memory speeds, attention to locality can have a profound effect on the performance of even ordinary serial programs. Some existing languages can make life difficult for the performance-minded programmer because they do not allow much leeway in expressing placement. For example, extensions allowing the programmer to describe array layout as block-cyclic is helpful for matrix-oriented code but of no use for general data structures. Because high performance appears to require explicit human-directed placement, pSather implements a shared memory abstraction using the most efficient facilities of the target platform available, while allowing the programmer to provide placement directives for control and data (without requiring them). This decouples the performance-related placement from code correctness, making it easy to develop and maintain code enjoying the language benefits available to serial code. Parallel programs can be developed on simulators running on serial machines. A powerful object-oriented approach is to write both serial and parallel machine versions of the fundamental classes in such a way that a users code remains unchanged when moving between them. 1.6 HistorySather is still growing rapidly. The initial Sather compiler (for Version 0 of the language) was written in Sather (bootstrapped by hand-translating to C) over the summer of 1990. ICSI made the language publicly available (version 0.1) June of 1991 4. The project has been snowballing since then, with language updates to 0.2 and 0.5, each compiler bootstrapped from the previous. These versions of the language are most indebted to Stephen Omohundro, Chu-Cheow Lim, and Heinz Schmidt. pSather co-evolved with primary contributions by Jerome Feldman, Chu-Cheow Lim, Franco Mazzanti and Stephan Murer. The first pSather compiler 3 was implemented by Chu-cheow Lim on the Sequent Symmetry, workstations and the CM-5. Sather 1.0 was a major language change, introducing bound routines, iterators, proper separation of typing and code inclusion, contravariant typing, strongly typed parameterization, exceptions, stronger optional runtime checks and a new library design 6. The 1.0 compiler was a completely fresh effort by Stephen Omohundro, David Stoutamire and Robert Greisemer. It was written in 0.5 with the 1.0 features introduced as they became functional. The 1.0 compiler was first released in the summer of 1994, and Stephen left the project shortly afterwards. The pSather 1.0 design was largely due to Jerome Feldman, Stephan Murer and David Stoutamire. This document describes Sather 1.1, released the summer of 1996. The compiler was originally designed and implemented by S. Omohundro, D. Stoutamire and (later) Robert Griesemer. Boris Vaysman is the current Sather czar and feature implementor. Claudio Fleiner implemented most of the common optimizations , a lot of debugging support, the pSather runtime and back-end support for pSather. Michael Philippsen implmented the front/middle support for pSather. Holger Klawitter implemented type checking of parametrized classes. Arno Jacobsen worked on bound iterators. Illya Varnasky implemented inlining support and Trevor Paring implemented an early version of common subexpression elimination. A group at the University of Karlsruhe under the direction of Gerhard Goos created a compiler for Sather 0.1. The language their compiler supports, Sather-K, diverged from the ICSI specification when Sather 1.0 was released. Karlsruhe has created a large class library called Karla using Sather-K. More information about Sather-K can be found at:http://i44www.info.uni-karlsruhe.de/frick/SatherK1.6.1 The NameSather was developed at the International Computer Science Institute, a research institute affiliated with the computer science department of the University of California at Berkeley. The Sather language gets its name from the Sather Tower (popularly known as the Campanile), the best-known landmark on campus. A symbol of the city and the university, it is the Berkeley equivalent of the Golden Gate bridge across the bay. Erected in 1914, the tower is modeled after St. Marks Campanile in Venice, Italy. It is smaller and a bit younger than the Eiffel tower. The way most people say the name of the language rhymes with bather. The name Sather is a pun of sorts Sather was originally envisioned as a smaller, efficient, cleaned-up alternative to the language Eiffel. However, since its conception the two languages have evolved to be quite distinct. 1.6.2 Sathers AntecedentsSather has adopted ideas from a number of other languages. Its primary debt is to Eiffel, designed by Bertrand Meyer, but it has also been influenced by C, C++, Cecil, CLOS, CLU, Common Lisp, Dylan, ML, Modula-3, Oberon, Objective C, Pascal, SAIL, School, Self, and Smalltalk. Steve Omohundro was the original driving force behind Sather, keeping the language specification from being pillaged by the unwashed hordes and serving as point man for the Sather community until he left in 1994. Chu-Cheow Lim bootstrapped the original compiler and was largely responsible for the original 0.x compiler and the first implementation of pSather. David Stoutamire took over as language tsar and compiler writer after Stephen left. That position was, in turn, taken over by Boris Vaysman in late 1995. Sather has been very much a group effort; many, many people have been involved in the language design discussions including: Subutai Ahmad, Krste Asanovic, Jonathan Bachrach, David Bailey, Joachim Beer, Jeff Bilmes, Chris Bitmead, Peter Blicher, John Boyland, Matthew Brand, Henry Cejtin, Alex Cozzi, Richard Durbin, Jerry Feldman, Carl Feynman, Claudio Fleiner, Ben Gomes, Gerhard Goos, Robert Griesemer, Hermann Hertig, John Hauser, Ari Huttunen, Roberto Ierusalimschy, Arno Jacobsen, Matt Kennel, Holger Klawitter, Phil Kohn, Franz Kurfess, Franco Mazzanti, Stephan Murer, Michael Philippsen, Thomas Rauber, Steve Renals, Noemi de La Rocque Rodriguez, Hans Rohnert, Heinz Schmidt, Carlo Sequin, Andreas Stolcke, Clemens Szyperski, Martin Trapp, Boris Vaysman, and Bob Weiner. Countless others have assisted with practical matters such as porting the compiler and libraries. 1.6.3 References1 G. Agha, Actors: A Model of Concurrent Computation in Distributed Systems, The MIT Press, Cambridge, Massachusetts, 1986. 2 S. Burson, The Nightmare of C++, Advanced Systems November 1994, pp. 57-62. Excerpted from The UNIX-Haters Handbook, IDG Books, San Mateo, CA, 1994. 3 C. Lim. A Parallel Object-Oriented System for Realizing Reusable and Efficient Data Abstractions, PhD thesis, University of California at Berkeley, October 1993. Available at the Sather WWW page. 4 C. Lim, A. Stolcke. Sather language design and performance evaluation. TR-91-034, International Computer Science Institute, May 1991. Also available at the Sather WWW page. 5 S. Murer, S. Omohundro, D. Stoutamire, C. Szyperski, Iteration abstraction in Sather, Transactions on Programming Languages and Systems, Vol. 18, No. 1, Jan 1996 p. 1-15. Available at the Sather WWW page. 6 S. Omohundro. The Sather programming language. Dr. Dobbs Journal, 18 (11) pp. 42-48, October 1993. Available at the Sather WWW page. 7 C. Szyperski, S. Omohundro, S. Murer. Engineering a programming language: The type and class system of Sather, In Jurg Gutknecht, ed., Programming Languages and System Architectures, p. 208-227. Springer Verlag, Lecture Notes in Computer Science 782, November 1993. Available at the Sather WWW page.