Alice in Wonderland Essay Example for Free

Alice in Wonderland Essay As the Cheshire-Cat appears and sits on a limb of a tree with his grinning face while Alice is walking in the forest he explains to her that everyone in wonderland is mad even Alice, which is why she is there. Alice did not agree with the Cheshire-Cat but continued on her way to see the March Hare anyways. Being mad or crazy does not always make a person bad. In fact the Cheshire-Cat was right, all the people in Wonderland were indeed mad and they were all there for that reason. In every classic story there are good characters versus bad characters. In the book, Alice in Wonderland written by Lewis Carroll, there is no exception. The characters Alice, the White Rabbit, and the Cheshire-Cat are all positive characters in the story and the Queen of Hearts is the villain or the negative character in Wonderland. Positive characters can be identified in the story of Alice in Wonderland by their personalities and how each character interacts with one another. Lewis Carroll only made one distinctive negative character and the rest he made either positive characters or characters that are Just in the middle. Most of the characters in the ook are middle characters that do not have a good or bad sense of personality. Negative characters can be identified by color and personality as well. The Queen of Hearts for instance is represented by the color red with represents fury and anger. That describes the Queen perfectly. Alice is a positive character in the story of Alice in Wonderland. She is the main character of the story. Lewis Carroll does a good Job of portraying Alice as a young curious and well mannered lady. Youth and innocence can describe Alice as a positive character. Throughout the whole story Alice gets onfused quit easily when talking to the other people in Wonderland, the Mad Hatter and the Caterpillar especially. Although she is in an obscure and crazy world, Alice keeps her cool for the most part and tries to keep her senses. In the world of Wonderland, however, being sane is mad, which allows Alice to fit right in with the others (From Alice on Stage). The White Rabbit was made to contrast Alice in every way. He is timid, old, punctual, and often nervous. The White Rabbit can be seen as a positive character because he is white in color, also because he is somewhat helpful. Although he is shy and nervous he does not do anything that would make him be considered a negative character. I would say he is somewhat of a mediator, neither positive nor negative. The White Rabbit is significant in the story of Alice in Wonderland in order to understand Alice more (From Alice on Stage). Most unique of them all is the Cheshire-Cat. When Alice first comes across the Cheshire-Cat he is in the house of the Duchess and is grinning very widely. From the way he is first described I thought that he was going to be a negative character in the story. His grin seemed some what villainous and because he was mysterious led to the conclusion he was a negative character. After the book goes on the Cheshire-Cat is very calm and sensible in the mad world of Wonderland. He helps Alice when she need someone to talk to and when she has questions about Wonderland. The Cheshire-Cat is the most knowledgeable about Wonderland and fits right in when it comes to craziness (Spark Notes from Alice in Wonderland). Queen of Hearts. Some of the other characters have their moments of rudeness or snappy ways but none of them can be identified as complete negative characters esides the Queen of Hearts. When we first meet the Queen she comes into the yard yelling orders at everyone and being very rude. From the beginning you can tell that the Queen has anger and fury within her. Because she is red in color she can be identified as negative. Red usually has a bad connotation and is usually associated with anger and fire or fury. She makes irrational decisions, most of them affecting everyone but herself. Everyone in her court is afraid of her because she is known for prosecuting and beheading anything and anyone who gets in her way (From Alice on Stage). Of all the characters in Alice in Wonderland the Queen of Hearts and Alice are the most significant. I would not say that in this story there is a hero or villain, but Just positive and negative characters. A lot of the characters in the story were middle characters that had no sense of good or bad, they were Just mad. Everyone in Wonderland was mad, including Alice, that is why she ended up in Wonderland. Lewis Carroll defined each character using their personalities. The Queen of Hearts impatient, loud, and obnoxious and Alice is curious, sensible, and has a sense of uperiority.

Service Oriented Architecture (SOA) Design

Service Oriented Architecture (SOA) Design Introduction Objective The goal of a Service Oriented Architecture (SOA) is to achieve reusable assets in an agile manner that is aligned with the business needs of the organization. The SOA Reference Architecture provides guidelines for making architectural and implementation decisions. To that end it serves as a blueprint for creating or evaluating a solution architecture for different groups within the organization. In addition it provides insight and patterns for integrating the different elements of an SOA as illustrated by the different layers of an SOA. An SOA Reference Architecture is designed to answer some of the key questions and issues encountered while developing a solution such as: What are the aspects of an SOA as expressed in terms of layers that need to be considered when designing solutions based on SOA principles? What are the building blocks needed to include in each layer of a solution? What are some of the key architectural decisions that need to be made when designing a a solution that is based on SOA? Which roles in a project would benefit from using these principles and guidelines? To answer these questions this document provides the following: Establishes a common vocabulary and set of definitions for services and SOA. Identifies the different functions of an SOA implementation and define their interactions with each other and with functions outside the scope of the Rufus platform. Provides SOA guiding principles. Defines consistent design and implementation across services. Shows when and where to use SOA technologies. Supports SOA governance. Provides an architectural based design methodology. Overview This document presents the layers, building blocks, architectural and design decisions, patterns, options and the separation of concerns needed to design or evaluate an SOA architecture. The architecture consists of multiple components which are divided into the following categories: Quality of Service (QoS) Security Consumer Business Process Integration Services Information Infrastructure Governance Monitoring Management Center of Excellence (COE) Design Time Elements Component View Design Time Elements Design-Time Activities are the technical activities, guidelines, and deliverables that allow for everyday development within the SOA and Integration Architecture. Including: Service Modeling and Design Canonical Data Modeling Policy Specification Service Assembly Service Testing Service Identification Service Lifecycle Management Service Modeling and Design Services must be modeled and designed to support an extensible plug-and-play model by being: Reusable So that other Services leverage an existing Service. Composable So that a Service can leverage other Services. Interoperable So that Services can work with each other. Discoverable To support location independence. To enable the above qualities, each Service (except for Data and Utility Services) needs to have: A well-defined Service Contract To enable loose couple by hiding low-level implementation details from Service Consumers. SOAP-based Web Services achieve this by specifying a WSDL interface with XML-based document exchange. RESTful Web Services define a contract with HTTP input parameters and JSON/XML-based responses. Coarse-grained So that operations have enough data to carry out all tasks in a stateless manner. Stateless operations Statelessness (i.e., not maintaining state between invocations) enables a Service to be reused in many contexts. A way to handle Exceptions to notify its caller if there are problems carrying out an operation. To ensure that each type of Shared Service is designed and implemented in a uniform manner, a SOA Governance team should create SOA Best Practices documents for: Service Design, Web Service Design, and XML Message Design in Designers Guides (i.e., working agreements). Topics would include: Service Specification and Design Interface (including Canonical Data model for messages see section 3.5.2) Policies (see section 3.5.3) SLAs (Service Level Agreements) A description of what the Service does A description of the Services operations. Best practices for each type of Shared Service (Business, Common, Data, Integration, and Utility). Examples showing the difference between Service-Oriented Design and Object Oriented Design. How to develop a SOAP Web Service (and handle Exceptions). How to develop a RESTful Web Service (and handle Exceptions). Canonical Data Modeling (XML) Many organizations have several autonomous packaged and custom developments that have evolved independently of one another. Many times, each system has become a system with its own implementation methodology, culture, processes, business rules, and vocabulary. Many companies face the problem of using the business data to enable applications to communicate in a distributed systems environment. Organizations design Canonical Data Models (CDM) to help analyze the message exchange within the organization and with their trading partners. Data is embedded in the basic architecture of any organization. To develop the CDM, an organization must inventory business concepts and map the vocabulary into fundamental business concepts. The CDM provides a framework for integrating the disparate terms for each line of business. The CDM is a catalog of neutral terms defined in an XML Schema, including: Entities in the business domain (e.g., Order, Customer, etc.) Agreed-upon data structures so that a domain element has a single, common definition. Formatting rules. A CDM defines an organizations data in motion the XML messages exchanged between: Services within an enterprise. An enterprise and its external trading partners. Many industries have an industry standard (e.g., ACORD, for Insurance, or EDRM for e-Discovery) to define core concepts and define data exchanged between companies. A Canonical Data Model provides the following benefits: An enterprise can easily exchange data with its business partners. An enterprise can adopt a single approach to exchanging data across all services the enterprise. The canonical model helps define the interface for each Service (thus hiding the structure of the physical data in the database). Changes to the canonical data model are required only when an entirely new business concept arises. Policy Specification Policies provide service-level meta-data to Web Services consumers. Specifying these policies is an important step in Web Service design, and this is accomplished by attaching policy expressions to the WSDL. Specifically, these policies include: Security: Transport Protocol Algorithm (RSA, etc.). Messages Authentication/Authorization Level of Service (e.g., Silver, Gold, Platinum, etc.). For example, a Platinum customers requests execute on best-provisioned server for better performance (but also at a higher price). Performance For example, send notifications if performance for a particular service dips below the promised SLA. Auditing For example, begin auditing when a particular service consumer invokes an operation on a Service. Service Assembly A Business Analyst first develops a Business Process Diagram (using BPMN Business Process Modeling Notation) to model a business process at a business/requirements level. Then, designers and developers create a runtime model in either BPEL (Business Process Execution Language) or JBI (Java Business Integration) to: Assemble existing Shared Services into a Business Process Enable a BPMS product and/or ESB can run the business process. Designers use MEPs (Message-Exchange Patterns) to model the runtime characteristics of a business process. Typical MEPs include: Pipes and Filters Content-based Router Recipient List Wire Tap Dynamic Router These patterns are gaining in popularity and many of the newer ESB and BPMS products support executable MEP models. Please see the following for further information: Enterprise Integration Patterns Home Page Enterprise Integration Patterns, Gregor Hohpe, Bobby Woolf, et al. Service Testing Most Shared Services will be implemented as Web Services, and it is important to take a Test-Driven Development (TDD) approach to Web Services development because: Designers and developers need early feedback on the design, functionality, usability, and performance of each Web Service. QA personnel need to be able to test Web Services. Overall quality is very important because each Web Service could be used by multiple consumers. Service Testing includes: Inspecting Web Services: Documentation Generating HTML documentation from the Web Service interface. Debugging Show SOAP/HTTP requests that are sent received over the wire. Invoking Web Services: Generating Web Services requests from WSDL to set the Web Service. Simulating/Mocking Web Services Generating Unit Tests based on the Web Service interface. Functional/Performance Testing Web Services Simulating load conditions. Reporting on performance under load conditions. Commercial products include: Eviware soapUI Pro iTKO LISA Open Source products include: Eviware soapUI Community Edition WebInject PushToTest TestMaker Points to Ponder (for Evaluation) Does the product support both SOAP and RESTful Web Services? How? Does the product enable you to view SOAP/HTTP messages over the wire? Does the product have a good/usable Web UI to make it easy to test? Can a QA/Tester use the product without developer intervention? What level of SOAP, WSDL, and HTTP does the product support? Does the product support an Agile/TDD approach with Unit Tests and Mocking? Does the product generate Unit Tests to support Continuous Integration? Can the product simulate load conditions and report on performance/scalability? How much setup is involved? How does the licensing work? Service Identification Service Identification is one of the key steps in designing a Service-Oriented solution because it defines and identifies high-level Business Services by using the following the following approaches: Top Down: Analyze and model business processes. Design new Services that enable the tasks and activities in the business processes. Bottom Up: Service-enable existing and applications systems. Create business processes from the Services. Middle Out: Analyze and model business processes. Catalog existing applications and services. Determine which can be Service-enabled. Create Service Adapters. Map tasks and activities from the business processes to existing Services. Create new Services to fill in the gaps. A Middle-out approach is recommend because it takes the best parts of the other approaches: The bottom-up approach creates isolated silos that dont align with the business. The top-down approach takes a long time, and the enterprise cant wait for every business process to be defined in order to begin designing and developing Services. A compromise approach takes into account the need for timeliness, but also instills enough discipline to design Business Services that match up with the goals and objectives from the Business Architecture by: Taking a first cut at the Business Services from Marketing materials and meetings with the CMO and other business stakeholders. Starting with only a few Business Processes. Driving toward a thin/vertical slice of functionality based on the business processes. Service Lifecycle Management Service implementations are software like any other software module or application. As such, they go through a similar lifecycle. The service lifecycle is depicted in the following diagram. The lifecycle starts with Service Identification. Services are part of more general business processes. As such, new services are usually identified by the design of a new business process. This is not the only way that new services are identified however. Sometimes services are identified as part of portfolio management. This involves analyzing the requirements for a service across the breadth of the enterprise. The level of analysis required for this type of identification is difficult to gauge and therefore CIBER does not recommend using portfolio management for service discovery at this time. Once a service has been identified, it follows an iterative development process. Iterative processes use the feedback from subsequent phases to make corrections in previous phases based on lesson learned or issues that may crop up. Services are part of a greater distributed system however and any changes made can have an impact on other development efforts. Therefore it is important to be mindful of the effect change can have even during development of a service. The Service Specification and Design phase produces at a minimum the specification for the service interface. This interface specification includes the semantics and data that the service supports. This represents the contract between the service and its consumers. Diligence should be applied to the design of this interface as changes to the interface have the greatest impact to subsequent phases. Changes to the service interface can impact both clients that may be developed in parallel, implementation of the service, as well as test plans that have been implemented to test the service. This does not mean that a service interface must never be changed once it is designed. Designs are not perfect and in todays IT environment it is not always possible to take the time required to produce an interface definition that is ideal. Therefore it is prudent to put processes in place that take into account that service interfaces may change. Whenever implementing a service take into account tha t the interface may change to the extent possible to minimize the impact of that change. This also applies to the implementers of consumers of the service. In some cases, consumers may want to wait until the service has been through some number of rounds of testing before starting their implementation. This allows for some experience to be developed with using the service thereby (hopefully) minimizing the possibility of change to the interface. Once the service has been designed it proceeds to the Service Implementation phase. In this phase the service will be developed based upon architectural standards developed by the university OIT group. Any issues encountered trying to implement the design of the service should be fed back to the designer in order to refine the design if necessary. Finally, service need to be tested before being deployed into production use. Testing of services involves four primary areas of focus: Security testing is essential to assess the risk of a service with regard to vulnerability, data privacy and data integrity. Tests need to be developed to test boundary conditions which can assess the robustness of the service handling inputs outside the range of anticipated values. Tests should also be created that ensure the service performs as expected based on the roles as defined within the system. Type of Testing Description Functional This area of testing focuses on ensuring the service performs its function according to the requirement of the business process it support. Automated test suites should be developed to perform regression testing to quickly verify functionality during the life cycle changes that may occur. Performance This area of testing focuses on performance characteristics of the service including measurement of time to perform the service and load testing of the service. The output from this type of testing forms the basis of understanding how to configure and deploy the service in a production environment. Interoperability This area of testing ensures the service adheres to its service specification. Early identification of interoperability issues is key to integration of the service through exposure to university partners and clients. This type of testing is especially important when the service interacts with multiple data sources and/or systems. Security Security testing is essential to assess the risk of a service with regard to vulnerability, data privacy and data integrity. Tests need to be developed to test boundary conditions which can assess the robustness of the service handling inputs outside the range of anticipated values. Tests should also be created that ensure the service performs as expected based on the roles as defined within the system. Regression One of the more important types of testing related to usage of services is regression testing. The more applications that depend on a given service, the more impact a change to that service can have on the environment. As such, when changes are made to services, regression testing must be undertaken to ensure that the service not only supports new or updated functions but all other functions upon which the service relies. Table 1 Service Testing Types Once the service is ready it is deployed into production use. At this point the service enters the maintenance cycle as opposed to the development cycle. Services in production sometimes require change. The change may be due to a defect in the system or a request to add more functionality to the service. It is important to understand how this change should be handled based on its nature. Defects that are a result of a fault in the underlying implementation of the service and do not change the behavior of the service may be handled by a Defect Remediation process. In this case it is desirable to apply a fix as quickly as possible to the existing service as it may be affecting multiple university processes and causing a disruption to the universities ability to perform its function. Changes that modify the behavior of an existing service or its interface are best handled by identifying a new service or a separate version of the service. In this scenario versions are really new services that are separate from the original. Taking this route minimizes impact on consumers using the original service but can cause a proliferation of services within the enterprise. This may not always be desirable however and some effort should be put into defining conditions under which an existing service in production may be modified (for instance, only one business consumer is affected and the change is well understood). This should be documented so that everyone understands the conditions and ensure that changes are handled in a consistent manner. Service Withdrawal is the final step of the lifecycle. Eventually services will start ballooning (especially when changing production services leads to the creation of new services) and some services will stop being used. Removing service can be problematic as a service may support multiple business process owned by different colleges and departments. A procedure needs to be adopted to define and orderly withdrawal of services from the system. Such a procedure may start with deprecating the service (with a note explaining why and some suggestion as to another service to replace it). Secondly, services can be monitored for use and the consumers identified. Finally, if the service is still being used the consumers should be contacted to discuss a solution. This should result in establishing a schedule for the consumers to switch over to another service so that the service may be withdrawn. Consumers of a deprecated service may not have incentive to change. Making changes requires effort and possibly some risk to the consumer. This needs to be recognized when seeking collaboration from consumers to switch over to another service. In this case it will be necessary to be creative in coming up with a common understanding of the benefit of switching to a newer service so the deprecated one may be withdrawn. Center of Excellence (COE) An online community to: Impart the SOA Vision. Educate IT and business staff on SOA. Communicate SOA best practices. Gain feedback on how to adapt the SOA Governance process and overall SOA program. Provide support advice for new and ongoing SOA implementations. Provide SOA Resources: Books Web Sites Industry Standards Quality of Service Logging Most applications and systems use some form of logging that stores messages to a persistent medium (DBMS, file, etc.). Logging provides the following benefits: Troubleshooting Applications log errors upon failure, and system personnel use this information to repair the problem. Reviewing System personnel examine log messages to check for problems. Auditing Security personnel can review log messages to see what actions a user performed in the system. Debugging Developers generate log messages to debug their programs. Identity Management Identity Management is the ability to identify a requestors (person or system) true identity and relationships between people and organizations (groups). The current policies and level of enforcement are expected to continue into Managed Services by using Microsofts Active Directory as the source for identity management. Confidentiality Confidentiality assures that during transport of the data it was never visible, accessible or viewed other than by authorized recipients. There currently is no Smart Energy or Smart Grid requirement to secure messages for Confidentiality. Authentication Authentication is also done within Microsofts Active Directory and adds authorization policies to the verified identity. Authorization Authorization is currently done at the application level. Within Managed Services (stage MS3) authorization will be performed to determine whether the requestor (person, application, service) is authorized to access the requested service, data and even the Managed Data Repository. Integrity / Non-repudiation Integrity requires that during transport and even as read by the sender there were no unauthorized modifications of the content of the message. Non-repudiation assures the sending service that the receiving service has received the intended message. Current Smart Energy and Smart Grid projected needs do not require message Integrity, but for sensitive messages (time, confidentiality, event, or priority) there is Non-repudiation. Consumers Service Consumers are the end consumer/user of the services provided by an enterprise. The consumer has the flexibility to process and display useful and relevant information provided by Services. Service Consumers access Services through a consistent interface (or contract) exposed by that Service. Service Consumers can be: User Interfaces B2B Applications Business Processes User Interaction Users can access enterprise services through variety of mechanisms, including Portals, web sites, or PDAs. A web site provides a web-based interface to enable users to perform daily, job-related tasks. A web site leverage the services created provided the organization, as a part of SOA implementation, and do not contain any business logic themselves. The site seamlessly integrates with back-end services (using SOAP/WSDL, REST/JSON) and business processes. The site can be secured by global security policies, but also can include role based authentication that limits access to only relevant information making it easier to manage. A Portal is a web site that enables users to access highly personalized information and services. It can increase the productivity and effectiveness of employees within an organization through a consolidated view of available services and information. Typically the site is highly interactive, allowing the user to run a wide variety of tools and functions such as, global search queries, and custom dashboard and advanced business intelligence tools. Portals provide a unified entry point to the organization and provide common look and feel all across applications. Portals form the front end for business processes and custom applications created as composite applications. The site can also be utilized to mash-up other applications or services from 3rd party sites. Wikis, Blogs, RSS feeds, and content can all be made available within the site. A PDA enables mobile users to access enterprise services. Like sites and portals, a PDA has no business logic of its own, but it allows the end user to interact with back-end services by seamlessly accessing the Web Services exposed by an enterprise. However, a PDAs interface and functionality is much more limited than that of a web site because of display and memory constraints. B2B Applications An organization normally collaborates with external business partners such as suppliers and customers to achieve its business objectives. An external partners B2B application (e.g., a web site or portal) will invoke a Web Service exposed by an enterprise, which in turn executes business functionality on behalf of the client. Business Processes A Business Process codifies and streamlines the rules, practices, and business s activities in an enterprise. Business analysts create Business Process Diagrams using the industry-standard Business Process Modeling Notation (BPMN) to document a set of coordinated tasks and activities that lead to an organizational goal. You can think of a business process as a graphical representation of a Use Case (RUP) or User Epic (Agile / Scrum) in that it shows normal and alternate flows along with exceptions encountered during processing. In SOA, a business process coordinates the business services (see section 3.2.1) developed by an enterprise. SOA architects and developers derive business services from the tasks and decision points in a business process diagram. Business logic is used to form business flows as parallel tasks or sequential tasks based on business rules, policies, and other business requirements. Examples of Business Processes include: Purchasing a product Time Entry / Approval Billing Service Provisioning For information on tools and products, please the Workflow / Orchestration section (3.4.5). Collaboration Services Presentation Services Presentation Services define a common set of services to manage interaction with users or trading partners (to the extent this second interaction is needed). Presentation services are provided by: web servers, portal servers, and application servers that provide the capability to quickly create the front end of business processes and composite applications to respond to changes in user needs through channels, portals, rich clients, and other mechanisms. Presentation services integrate with other foundational services, such as security (e.g., single sign-on). Users can access enterprise services through variety of mechanisms, including Portals, web sites, or PDAs. A web site provides a web-based interface to enable users to perform daily, job-related tasks. A web site leverage the services created provided the organization, as a part of SOA implementation, and do not contain any business logic themselves. The site seamlessly integrates with back-end services (using SOAP/WSDL, REST/JSON) and business processes. The site can be secured by global security policies, but also can include role based authentication that limits access to only relevant information making it easier to manage. A Portal is a web site that enables users to access highly personalized information and services. It can increase the productivity and effectiveness of employees within an organization through a consolidated view of available services and information. Typically the site is highly interactive, allowing the user to run a wide variety of tools and functions such as, global search queries, and custom dashboard and advanced business intelligence tools. Portals provide a unified entry point to the organization and provide common look and feel all across applications. Portals form the front end for business processes and custom applications created as composite applications. The site can also be utilized to mash-up other applications or services from 3rd party sites. Wikis, Blogs, RSS feeds, and content can all be made available within the site. A PDA enables mobile users to access enterprise services. Like sites and portals, a PDA has no business logic of its own, but it allows the end user to interact with back-end services by seamlessly accessing the Web Services exposed by an enterprise. However, a PDAs interface and functionality is much more limited than that of a web site because of display and memory constraints. BI / Reporting BI (Business Intelligence) / Reporting provides a high-level view of KPIs (Key Performance Indicators) to business stakeholders to enable them to make decisions and manage the business. Examples of KPIs include: Efficiency of business processes. Job Costing. New customers acquired. Sales information by demographic (age, ethnicity, geographic region, etc.). Churn / turnover of accounts by demographic. A BI product uses the information stored in a Data Warehouse to present it to the user. A BI tool (such as Business Objects) uses Key Performance Indicators (KPIs e.g., sales conversion rate, in-force polices, market penetration, for example) to report on data, identify trends, perform data analysis, etc. to enable business users to make decisions and operate the business as efficiently as possible while advancing a business strategy. BI increases business agility and shortens timeframes for decision-making. It gives companies the ability to identify and anticipate opportunities represented by seemingly unrelated events. It is a key enabler of strategic and tactical decision making. Commercial products include: IBM COGNOS MicroStrategy O

Prostitution Should be Legalized :: essays research papers

During the 1700s, New York and Boston women began soliciting their bodies to soldiers stationed in the large cities. These women were mostly European immigrants who were looking for money to support themselves. Prostitution rose in these cities due to rapid urbanization, and an expansion of the male population. So, you may be thinking, â€Å"prostitution is illegal and evil, right?† Well, you are correct, but in my opinion, only by the standards of which you have been living in, which is that prostitution is illegal, and therefore, â€Å"risky business.† In my hometown of Elko, Nevada, population thirty-five thousand, prostitution is legal. People who hear of this tend to think there are scantily clad women on every street corner. I, however, have never seen a prostitute, or haven't noticed her if I did, because they are only allowed, by law, to â€Å"do their business† in a brothel that is in a small section of the town. These brothels are brightly painted, and there are almost no windows in the building. Unlike prostitution that is run in the cities, brothels in my town are run by a management of three or more people, not one pimp. As the customer gets buzzed in to the building, the management checks his identification to make sure he is at a legal age. The customer can then choose between any of the ladies lined up. The prostitute and customer go into a room, and negotiate a price, which is overheard by the management. The amount is anywhere from one hundred to three hundred dollars, the house receiving half. The prostitute receives the other half of the profit. In illegal prostitution, the female usually receives anywhere from six to fifteen percent of the profit off a customer. If she were to make one hundred dollars, she would only get around six to fifteen dollars off it. The pimp would get the rest. Here are another three reasons that prostitution should be legal in the United States. A law was passed in 1986, requiring legal prostitutes to engage in a sexually transmitted disease test every two weeks at the Northeastern Nevada Regional Hospital. If a prostitute is found with a sexually transmitted disease, she is quarantined, until the disease is cured. If the disease cannot be cured, then she is no longer allowed to work, and is put into a home.

Effects of Marijuana :: Free Essays Online

The dominant fear about marijuana has been that its effects were somehow similar to the dangerously addictive effects of opiates such as morphine and heroin. Scientists feared that , like opiates, it had an extremely high potential for abuse and addiction. Despite widespread decriminalization of marijuana in the United States in the 1970's, this concern has remained the basis for federal law and policies regarding the use and study of marijuana. But the discovery of THC receptor sites in the brain refutes that thinking and may force scientists to re-evaluate their positions. The 1988 discovery of the THC receptor site in the brain was the pivotal event which led to the legalization of marijuana. The receptor breakthrough occurred in 1988 at the St. Louis University Medical School where Allyn Howlett, William Devane, and their associates identified and characterized a cannabinoid receptor in a rat brain. Receptors are binding sites for chemicals in the brain, chemicals that instruct brain cells to start, stop, or otherwise regulate various brain and body functions. Before this discovery, no one knew for sure just how the psychoactive chemical in marijuana workes on the brain. Throughout the 1970's and 1980's, researchers made tremendous strides in understanding how the brain works by using receptor sites as switches which respond to various chemicals by regulating brain and body functions. The chemicals which trigger receptors are known as neurotransmitters. The brain's neurotransmitters are known as endogenous ligands. In many instances, drugs mimic thes e natural chemicals working in the brain. Scientists are just now confirming their determinations as to which endogenous ligands work on the cannabinoid receptors. It is likely that the neurotransmitter which naturally triggers cannabinoid receptors is one known as anandamide. Many important brain functions which affect human behavior involve the neurotransmitter dopamine. Serious drugs of abuse such as heroin and cocaine, interfere with the brain's use of dopamine in manners that can seriously alter an individual's behavior. A drug's ability to affect the neural systems related to dopamine production has now become the defining characteristic of drugs with serious abuse potential. The discovery of a previously unknown system of cannabinoid neural transmitters is profound. While century-old questions such as why marijuana is nontoxic are finally being answered, new fascinating questions are emerging. In the words of Israeli researcher Raphael Mechoulam, the man who first isolated the structure of THC, "Why do we have cannabinoid receptors?

E.e. Cummings, Poem, Anyone Li Essay -- essays research papers

E.E. Cummings "anyone lived in a pretty how town" I first read this poem and I thought of love, two people in love. Anyone and noone are in love and that is what matters to them, to be in love with each other and with life. It involves the day, the night, and how the weather changes. The seasons revolve and the children grow up to become adults. As I read the poem I realized there were three sections to it. Which consist of anyone and noone, "women and men" in line four, and the children. The first stanza is strange the first time you read it. You do not understand "anyone" is a person and not just anyone. I believe that line six is referring to all of the adults in the town, Cummings does not want us to think of the town people as separate people but as a whole group undistinguishable from on another. This is told in line five where it states "little and small", he is grouping them in very close together. The children are separated into there own group. As they grow through the seasons in lines ni ne, ten, and eleven, they pass on into adulthood. They in essence no longer exist in the poem. The bells ringing might have something to do with them becoming adults, since I do not see them relating to any other parts of the poem. The bells seem to be an important part of the town since they are mentioned in the second line of the poem and those exact lines are repeated in line twenty-four, sixth stanza of th...

The Company Man Analysis Essay

ANALYSIS 7 Essay: The Company Man The typical business man involved in corporate America works anywhere from six to ten hours per day. Phil, â€Å"the Company Man† worked six days a week sometimes until eight or nine at night, making himself a true workaholic. Using his life story before he died Goodman is able to convey her liking toward Phil but her dislike of what the business world has turned him into. Not only does Goodman use a number of rhetorical devices but she also uses Phil’s past as well as the people who were once in Phil’s life to get her message across to her reader. Ellen Goodman sarcastically creates the obituary of a man who dedicated his life to his job and the company he worked for. Goodman uses anaphora, satire, diction, sentence structure, and selection of detail to complete her obituary of this â€Å"Company Man†. Emphasizing the fact that Phil worked himself to death, Goodman chose pure sarcasm to make this particular emphasis. She shows through this repeated phrases, that he must have chosen work over family quite often, working to provide for his family which resulted in the simple fact that â€Å"he worked himself to death, finally and precisely, at 3:00a. m Sunday morning. Goodman’s use of repetition leads to show her satirical writing. â€Å"On Saturdays, Phil wore a sports jacket to the office instead of a suit, because it was the weekend† shows Goodman’s use of satire in one of the many examples throughout the obituary. Toward the end of the essay, Goodman describes how the company president starts the funeral with a hint of sarcasm, â€Å"discreetly of course, with care and taste† using a tongue and cheek method to provide a subtle shift in tone. The president then begins to question who will replace Phil ending with a paradoxical sentence â€Å"‘Who’s been working the hardest? † getting down to the business of replacing Phil, providing another example of a stereotypical business approach. The vivid diction describes the sarcasm that Goodman has towards Phil. Goodman composes her paragraphs with careful rhythm and beat; she repeats â€Å"finally,† â€Å"precisely† and â€Å"perfect† three times. Phil’s constancy and lack of variation are embodied in rigid words such as â€Å"always,† â€Å"of course,† and â€Å"Type A. † Extreme diction such as â€Å"overweight,† â€Å"nervous,† and â€Å"workaholic† convey Phil as a worrywart with no fun at all in his life. These words mock Phil as a man sincerely obsessed with work that had lost track of his priorities. Goodman deepens her point when she introduces Phil’s family, using diction in relation to business to further emphasize the importance of work to Phil. To Phil’s wife Helen, â€Å"A company friend said ‘I know how much you will miss him. ’ And she answered, ‘I already have. ’† His eldest son tells the reader of how he went around the neighborhood gathering research on his father. His daughter recalls how whenever she was alone with him they had nothing to say to each other. When Phil’s youngest son reminisces on how he tried to mean enough to his father to keep him at home. Goodman informs the reader that the youngest child was Phil’s favorite. Goodman’s sentence structure of long, short, long, helps the shorter sentence stick out more to the reader. But she ends the paragraph with a sad ironic sentence, â€Å"My father and I only board here. † implying that he never really was successful. The descriptions of Phil in â€Å"The Company Man† are sardonically accusatory of the present way people live in society. Goodman makes light of how Phil is a heart attack waiting to happen, his seventy-hour workweeks and egg sandwiches. â€Å"Of course,† used thee times, translates as the acceptance that we have towards intolerable living conditions in order to fulfill the American dream. Like many Americans, Phil is constantly obsessed about his work and whether or not he will ascend to the top position. Through these details she describes the monotonous, repetitive way that society exists today. Throughout the column, images negatively portray the lifestyle that Phil lives. Superficially, all seems well because his family lives a comfortable existence. Emotionally, however, his family has missed his emotional support for years. His wife, Helen, gave up â€Å"trying to compete with his work years ago. † All of his children grew up in a so-called normal family with a father and mother. At his funeral, though, they do not have enough memories about him to say a proper eulogy. Phil himself was â€Å"overweight† and unhealthy, obsessed with work and negligent with his personal life. Goodman condemns the lifestyle that Phil leads by using negative and poignant imagery. Ellen Goodman develops an attitude of pity for Phil, and resentment for the company through rhetorical techniques by portraying that to his wife and to his children, Phil had become so consumed with his position as one of the Important People that he had all but completely removed himself from their emotional reach for the sake of his company life. Goodman’s vision of the corporate world and its influence and affect on our lives is portrayed through her diction and choice of detail in her anecdote of the reflection of the life of the A-Type, workaholic, Phil.

Peter Singer: Famine, Affluence, and Morality Essay

Human Rights: Consequential or Deontological View? Consequential ethics and deontological ethics (DE) mutually maintain that there is a right action that we morally ought to do. However, these normative ethical theories differ in the derivation of what is valued. In the case of human rights, both accounts are supportive of human rights, but for different reasons. Deontological ethics has as its basic thrust, the concept of a duty to do what is right. For one’s actions to be in accordance with DE, those actions must be realized out of a â€Å"notion of right (that) is not derived from a prior notion of good†, as explained by Illies (Illies, 2011, p. 107). A person should choose to perform an act solely because it is the right thing to do, irrespective of the act’s outcome or the consequences thereof. According to Illies transcendental argument, human beings have, by their nature, the inherent ability to distinguish between, the concepts of good and bad. Humans possess the capability to have an â€Å"active pro-attitude† toward good, as well as the freedom to act toward the same (Illies, 2011, p. 108-109). This translates to the concept of moral freedom in that the ability to perform free action toward this good specifically is simply, and unarguably, inherently good. Because of this fact, one should purpose, as it is one’s duty, to promote the moral freedom of another unequivocally, regardless of whose moral freedom one is promoting or as importantly, from a DE viewpoint, what the resulting potential outcome might be. Illies does stress that it is imperative to obtain as much information as possible surrounding the facts as to why a certain peoples’ rights are being suppressed, in order to promote those rights in the most lasting and efficient manner (Illies, 2011, p. 114). When one examines human rights, the concept of personhood is of paramount importance. DE calls for the treatment of others as an end and not as a means. This requires the respect of persons for whom they are as individuals and never as conduits through which one might accomplish a goal or achieve a benefit on their own behalf. In this light, one who holds to the DE concept of human rights has at his imperative the treatment of all individuals with equal respect, and the duty to promote their freedom with an â€Å"active pro-attitude†. Why does one do this? One does because this action, an â€Å"active pro-attitude† is good and the action of good is inherently good. As opposed to the deontological account, the consequentialist believes in the prior conception of the good. If something is good then it is right to promote something good according to consequentialism (Lillehammer, 2011, p. 90). Moreover, the actions with the best end results or consequences are what are to be evaluated as good. It must be clear that good intentions are not, at all, of value to consequentialists. Further, it is important to note that in decision-making, a consequentialist must hold to the demands of impartiality. Consequentialism upholds the idea that no one person is worth more than another (Lillehammer, 2011, p. 90). As we read in â€Å"Famine, Affluence and Morality,† Singer asserts that suffering from lack of food, shelter and medical care are bad. If we accept this assumption, and if we can, by our actions, prevent this bad from occurring, we are morally obligated to do so unless in so doing we sacrifice something that is of â€Å"comparable moral importance† (Singer, 1972, p. 500). Not all consequentialists agree with giving to Singer’s suggested â€Å"level of marginal utility† but there is basis for supporting human rights in consequentialism. According to consequentialists, human rights should be promoted because the rightness of supporting those rights is what is best for the world. It is clear that suffering is bad, and if we can alleviate suffering by supporting human rights then we clearly should promote them. If the consequence of the action is resultant from an actor who is promulgating the purist sense of consequentialism, it very well has the potential to be counter to his own individual interest. For the consequentialist, the overall consequence of an action is of primary importance. Consequentialists view impartial importance so â€Å"the good of everyone should count for everyone, no matter their identity, location, or personal and social attachments, now or hereafter† (Lillehammer, 2011, p. 92). This view supports the notion that the human rights of those who are far away are just as deserving, and just as valid, as the rights of those who are near. Furthermore, the universe will be better off by the rightness of supporting human rights. Maximizing the good is required from the consequentialist perspective. As noted earlier, consequentialist and deontological accounts differ from one another from their foundations. While consequentialists focus on the good being promoted only as in relationship to its overall effect on humanity as a whole, deontologists view principles affecting individuals’ actions. Rules guide the deontological approach and the best consequence for most people is the consequential concern. For example, a consequentialist would look at the issue of child labor differently from the deontologist. The consequentialist would evaluate the overall outcome of allowing young children to be employed in a factory full-time, with little pay. In a poverty-stricken country, these children may bring home much needed monies in order for their families to survive. The deontologist would view child labor as unethical in that children working long hours for little pay is unarguably wrong. Another illustration of their differing views is that of the U. S. drone attacks in Pakistan that killed innocent civilians. The consequentialist would say that sending those drones to kill an Al-Qaeda leader is the best outcome to thwart the attack of US citizens. The deontologist would say that the killing of innocent civilians is never justified as this violates their individual human rights. In the realm of human rights, the problem with adopting a consequentialist approach is that one cannot truly determine what is to be the proper or preferred result of a specific act on a group of peoples; even thoug h, with all good intentions, it may be supposed. Although a good and moral outcome may be realized from an action, to base that action solely on the intended consequence of that action, rather than the inherent goodness of the action, one does not insure that the action will result in result in, truly, what is best. Moreover, when the best possible outcome is the preferred result then individuals’ rights can be violated. The deontological account offers worldwide moral support of (individual) human rights. That is what human rights require. As asserted by Robert Paul Churchill, â€Å"The grounds for human rights remain the same as long as human beings, or moral person exist. The inherent worth of humans does not cease to justify certain forms of respect due to them, and thus human rights do not cease, even when addresses are genuinely unable to fulfill correlative obligations and therefore have legitimate excuses† (Churchill, 2011, p. 12). Choosing an action because it is right and good, without looking downstream at the resultant consequences of that action, allows one to make decisions on the duty to act based on purely the rightness and goodness of that act, and nothing more. Now, this assumes that those making these decisions possess the proper moral compass to know a right act from a wrong one. In support of the deontological approach, I maintain that one will â€Å"get it right† when they choose an action because the action is right, more so, than when they try to determine what the consequence might be from that action and work backwards in order to make the â€Å"right† decision. References Churchill, R. P. (2011). Global human rights. In M. Boylan (Ed.), The Morality and Global Justice Reader (7-25). Boulder, CO: Westview Press. Illies, C. (2011). How to think about global duties. In M. Boylan (Ed.), The Morality and Global Justice Reader (103-126). Boulder, CO: Westview Press. Lillehammer, H. (2011). Consequentialism and global ethics. In M. Boylan (Ed.), The Morality and Global Justice Reader (89-102). Boulder, CO: Westview Press. Singer, P. (1972). Famine, affluence, and morality. Philosophy and Public Affairs, 1(1), 229-243.