Book Reporter of Swim the Fly Essay Example for Free

Book Reporter of Swim the Fly Essay Their plan failed because Matt almost got recognized by Kelly in the girl’s changing room. However, Kelly and her best friends Valerie started to pay attention to Matt because his brave move of volunteering in the 100-m butterfly (or his appearance in the girl’s changing room? ). Ms. Luntz (their swimming couch) put Matt, a poor guy who can’t even manage a single lap, in the butterfly medley relay without even asking Matt. Sean and Coop came up with an idea to pretend having a stomachache in order to avoid the embarrassment. Matt’s grandpa sent a kitten to Mrs. Hoogenboom in order to get her attention which turned out Mrs. Hoogenboom almost found out he is the one who tried to suffocate the cat. Relate: T-S connection: I also have friends like Sean and Coop in my life that can not only have fun with but also share sadness with. T-T connection: Matt volunteered for the 100-m butterfly stroke championships so Ms. Luntz figured he wouldn’t mind doing another butterfly medley relay. However, Matt couldn’t even do one stroke and weren’t capable of swimming the fly. T-W connection: I saw a movie called American Pie which described similar situation in this book, a few guys fall in love with the hottest girls in their school and manage to date them out. Reflect: There are always some friends in your life who always make fun of you yet you never get angry with them. It is normal in the western culture for an old man to impress a widow who has just lost her husband? It is kind of unacceptable for me. This part of the book is the rising action because they hadn’t achieved their goal yet. The narrator is 1st person which is Matt himself. How does Matt’s grandpa’s relationship with Mrs. Hoogenboom relate to the story? Why did the author even mention it? Always be prepared, so when the opportunity comes you will be the one grabs it. ( If Matt can do butterfly stoke well enough, he will be able to join not only the medley relay but also the championships in order to impress the girl he likes. )

Model Driven Development Vs Test Driven Development Computer Science Essay

Model Driven Development Vs Test Driven Development Computer Science Essay Model driven development is a top-down, traditional approach that has been around for a long time. Test Driven Development (TDD) is a bottom-up, new approach in the sense that it has picked up its value in the recent years. The focus of MDD as the name implies is on the models rather than on code that guides the development of software whereas focus of TDD is on the tests. There have been several changes to MDD since the beginning to deal with the changing environment and complexities raised by projects. TDD started as a part of extreme programming (XP) methodology and has gained popularity among many developers as a separate practice itself. Traditional, hard cored MDD developers are accustomed to developing software that seems more natural to them considering it to be an Engineering approach. TDD developers approach the problem in a totally different perspective concentrating on customer views of the system. There are advantages and disadvantages to both approaches. For a high qual ity software product that meets the goals of the organization, it is important to understand and apply the most suitable methodology while making certain trade-offs if necessary. The best approach to follow depends on several factors including the type of organization, type of project, and experience the developers have. This paper is aimed at explaining Model driven and Test Driven development along with case study and observations. 1. Model Driven Development or MDD. Model can be precisely defined as â€Å"a description of a system from a particular perspective, omitting irrelevant detail so that the characteristics of interest are seen more clearly†. (Source: Patterns: Model-Driven Development Using IBM Rational Software Architect) Consider an example in which there is a pressing business need such as automation of certain processes and understanding the data collected in the business. In this situation a Business exists and there are people who are performing certain business activities in certain way. These are the people who are thinking of having a tool or a software product to help them increase their productivity and their functionality. These people who are called Domain Experts or Subject Matter experts or Business Experts know what they want. However, they currently do not have any software product that will help them to meet their needs. In this situation Domain Experts are the driving force. They do things in a certain way and expect the software product developed for them meet their needs should also do things in that manner. However, they do not know how a new software product will look like and how it will help them to meet their needs. People who develop this software product understand the needs , but they may miss the intricacies of the desired end product. Building a MODEL will help alleviate this situation. A MODEL can be a diagram, an animation or a presentation. If the Software that has to be developed is very small or involves 1 or 2 people, then the process need not be so much structured, even though it helps. However, while developing a large product which will involve tens or hundreds of people having different expertise, model will help them to accomplish this easily. A new product development building a Model is absolutely necessary. This is analogous to a civil Engineer creating a model of Building before it is actually built. Model Driven Development (MDD) is a methodology that focuses on designing models at an abstract level without considering the implementation details that guide the development process, focusing on one part of the system to manage complexity. Models help to analyze the problem and visualize the process. Most commonly used language for this purpose is Unified Modeling Language (UML). It establishes certain vocabulary and structure so as to understand and communicate between various developers. Artifacts are produced from the models, so the models are machine-readable, which is an important aspect of MDD. MDD is also called as â€Å"Model Driven Engineering†. An implementation of MDD is given by Object Management Group (OMG)s Model Driven Architecture (MDA). Focus of MDA is on forward engineering, i.e. creating code from modeling diagrams. Apart from MDA, there are also other views of MDD such as Domain Oriented Programming, Agile Model Driven Development, etc. MDA uses platform-independent model (PIM) to describe the system functionality as the first step. Platform Independent Model (PIM) is a generic way of representing the end view of the product without considering any technology or platforms going to be used. This model just transforms the Business requirements into a Model. This format does not contain any particular software code but shows the end state of the product in one of the Model development modes such as Diagrams, Flow Charts, and Animations etc. Based on the PIM and considering some economic conditions or availability, a proper platform is selected to develop the software. A model is then converted from PIM to platform specific model or PSM. . This contains software code at a higher level. Platform is a loose word in this context. This can be referred to type of hardware, software, operating system, programming language or combination of any of these put together. That is why choosing a platform is related to economic viability also. PSM can be thought of Developers model where as PIM can be thought of Domain Experts or End users model. UML representation using IBMs Rational Rose can be considered as PIM. Whereas, tools like IBM WebSphere Studio and Borland Together/J are used for developing PSM. In these, we have CODE VIEW and MODEL VIEW. These two views are synchronized together. When code is changed in Code View, it is reflected in the Model View and vice versa. The models may contain fixed and variable data, business requirements, presentation elements (forms, reports). If one of these elements changes, they can be incorporated into the model to see the changes that occur due to interdependencies. Based on the affects, all the other depending code can be changed accordingly to accommodate these changes. Models also describe what is called the Gap Analysis. Models are first built with an Ideal situation, but in reality the business processes and other aspects may be different. Therefore, the models will show the difference between the Real Life situation and the End State Ideal situations. This will help the Business units to define the changes in Business Practices or the Developers to meet the Business needs and bridge the gap. A well defined Structured System Analysis and Design (SSAD) is required to develop software based on Models. In this process, the design (Model) is taken as the basis to start with the development and as the development process is advanced, it is analyzed with the design and tested against the Model and re-visited to meet the requirements. Hence, software development using MDD approach requires Domain (Business) experts, software developers, Team leaders and Integration experts. Someone should also be able to play a Liaison role to understand both sides of the table Business side and Software side. This person will help each of the expert groups to understand the needs of other groups and will bridge the gap. Number of iterations in the project development process will be reduced drastically if this Liaison person has good knowledge and is an expert on both sides. MDD is used with many development processes such as waterfall model, iterative model, spiral model, etc. In MDD approach, a model plays an important role and forms the basis or driving mechanism to develop a software product. Test Driven Development: Test Driven Development (TDD) started its roots in Extreme Programming (XP) approach. Later on, it became a popular method by itself. TDD was originally called â€Å"Test First Programming†. TDD can best be described in three words as â€Å"Red-Green-Refactor† (source: Kent Beck). Simple essence of TDD is to write tests before the code is written. First, unit tests are written from the requirements. These tests will definitely fail because the code for it has not been written. In order to write the tests, it is necessary for the developer to understand the requirements well. Then, code that implements the test cases is written. The code that is written should be just enough so that the tests pass, no more, no less. This means that no prediction about the future story must be made. Test driven approach is â€Å"then there† approach. This means that code is written at that time from the user story requirements without making any assumptions or predictions about fu ture. After writing the code, the tests are run and seen if they succeed. If they do, then programmer can be assured that the requirements were met. After this, a process called refactoring is done. This refers to improving the quality of code and removing any duplication in the code. If the design is changed for the better, the developer can be sure he is not breaking any functionality by running the tests again. This process is repeated for the test cases that follow. This process is shown as a flowchart below: Source: http://en.wikipedia.org/wiki/Test-driven_development There are different issues to consider in this process. Test cases are written taking small steps at a time, such as implementation of one method. It is important to know the size of the test case and when the test case exceeds its limit of functionality to test. A test case contains the following: condition that specifies the systems state, an event that is to be tested, and finally systems state after the event has occurred. Almost every language has associated tools for writing these tests. In general, they are XUnit tests available for each language. For example, java has JUnit, C++ has cppUnit, .Net has NUnit, etc. The amount of designing that has to be done in TDD depends on developer. In Extreme Programming, no designing is done, directly jumping to test cases. However, some developers prefer to spend some time on design. Too much time should not be spent on the designs and deciding on that right amount of time to spend on it comes with experience. As suggested by Dave Chaplin, it takes almost a year for a good developer to learn most of the techniques in TDD. He divides the learning process in three stages. First stage would take three months to master writing the tests correctly. TDD is a totally different approach to take in developing software and most developers believe that hardest part about it is getting used to it and thinking in that direction. It takes another six months to learn about Mock objects. Last would be to be able to draw UML diagrams in a TDD perspective. This takes about three months. Those that become familiar with TDD find many advantages in it. These advantages are explained later in the paper. Pair programming is considered one of the best ways to develop a program using TDD. This is because another person can make sure you are going in right path. It is hard to make developers believe that this approach works. Also, management believes that it is a waste of money to make two people work on one feature while they can work on different features. Through test driven development, the focus is on customers requirements. TDD is now part of many other methodologies, such as Scrum, Agile Unified Process (AUP), and Rational Unified Process (AUP). TDD gives confidence to the developer and produces enthusiasm as they can see parts of the program coming together when they run the tests and see them pass. Case Study: Results of TDD and MDD are seen more effective by example. Therefore, I consider a case in which a Software Engineering class was given a choice of either doing MDD or TDD project. The projects were done for the same problem using different approaches. It was a calendar program that consisted of certain functionalities to fulfill. For TDD people, six user stories were given one after another without knowing what the next user story is. MDD people were given a problem definition and they were to submit GUI, design, code, tests at regular intervals. The functionalities that had to be implemented included finding the following: next date, previous date, zodiac sign, day of the week, next Friday the 13th, number of shopping days left until Christmas. These were each given as a user stories to TDD people. From the results of these, the following statistics were made: Model Driven Development approach results Criteria MDD User 1 User 2 User 3 User 4 User 5 User 6 Time To Code (hrs) 8 52 89 8.67 11 17 Time to Test (hrs) 2 15 13 3 3.3 2 NCSS (non comment source statements) 275 600 692 499 280 Number of Test Cases 109 142 51 Technology Used VBA Java Java (using Eclipse) C#.NET VS2008 C# VS Express C# Decision Complexity 79 59 Referential Complexity 26 52 Cyclomatic Complexity 105 111 83 GUI yes yes yes yes yes yes Test Driven Development approach results Criteria TDD User 7 User 8 User 9 User 10 User 11 User 12 User 13 User 14 User 15 User 16 User 17 User 18 Time to code 16.5 22 17 33 28 13.5 33 19.5 33 15 28 12.75 NCSS(non comment source Statements) 349 397 276 654 240 233 1095 279 196 298 328 277 Test cases 150 84 124 70 107 247 112 88 262 56 889 128 Technology C#.NET VS2008 Java Java Java VB.Net Express C VB .Net VBA Java Java VB.NET Java Decisional Complexity 106 66 76 76 97 115 62 57 77 145 81 Referential Complexity 12 43 40 24 24 34 19 102 9 160 29 Cyclomatic Complexity 118 109 117 100 65 121 149 81 159 86 115 110 GUI no no no no yes no no no no no No no Number of Times Refactored none 1 2 none 5 none 5 4 6 1 1 3 Observations: Even though there were almost twice as many people who did TDD as MDD, certain trends can be seen from the statistics. Since majority of the projects were developed using object oriented technology such as Java and C#, most of the observations are made based on these languages only. First and major difference that can be seen is creation of GUI. Only 1 out of 12 TDD people developed GUI while all of the six people who did through MDD developed it. One of the reasons for this is that in MDD, designing of GUI was first part of the task. In TDD, although there are tools that test a user interface, it is hard to obtain them and so user has to manually test them. Since it wasnt part of the requirement also, many had chosen to omit it. I noticed that neatest and well designed code came from most of MDD people. Even though there is refactoring in TDD, many had chosen not to do it. This can be seen by the statistics that 6 out of 12 people have either not done refactoring at all or did it only once. As research suggests, TDD is supposed to lead to high quality code. However, most of TDD projects code was of less quality. This comes to the point that in order to successfully carry out TDD, experience is needed. The lack of experience that most people had in doing a TDD might have been a factor for such quality. Many of TDD people had no experience in TDD methodology including me. As suggested by Dave Chaplin, in order to carry out TDD effectively, minimum one year of learning the techniques involved in the approach is needed for a good developer. Even though the quality and design is neater in MDD, number of lines of code was much less in TDD than MDD projects. In object oriented languages such as Java and C#, MDD projects had lines of code as 518 on an average while TDD projects had 350. This is partly due to refactoring eliminating unnecessary conditions and mostly due to the reason that since code was developed based on test cases, just about enough code that was necessary was written. Since the whole point of TDD is to start out with test cases, TDD projects have more test cases compared to MDD projects. For object oriented languages, TDD tests were 124 on average while MDD was 100. Although theory says that TDD results in highly cohesive and loosely coupled, but in practice, it is seldom like that. This point can be seen in this study. Most of the MDD projects were more cohesive and loosely coupled resulting in more reusable code compared to TDD. In TDD projects, it was seen that most of them had 2 or 3 classes at a maximum reducing cohesive nature and reusability. I observed that this is due to unpredictability of future user stories. MDD people can carefully plan the code such that it results in certain functions that can be used by other functions. In object oriented languages, correct amount of responsibilities and collaboration among objects in my opinion can be done more effectively if more designing is done. This is because it is much easier to see visually through the models. The reusability of the code in TDD also depends on the order of the user stories given. Most people reused day of the week code in shopping days till Christmas user story or Friday the 13th user story. Suppose that the user stories are given in a different order, then different approaches might be taken that might not result in the efficient piece of code. Refactoring tells you to remove duplications and keep the code clean, but the logic of the code will not change. In our case, if suppose number of shopping days left before Christmas was given before day of the week user story, then different approach might have been taken and the reusability of the day of the week code wouldnt have existed. It is easier to see collaborations and responsibilities of objects when the whole picture of the problem is present. Even the small amount of reusability that existed in TDD was due to the logical order in which the user stories were given. The time spent on the whole project for TDD is much less than MDD. Considering object oriented languages, TDD average time spent was 21 hours while MDD was 42 hours (almost double!!). TDD is proven to be faster and easier technique than MDD. In TDD, concentration is on current user story and it is faster to write test cases and code directly from user requirements. The time spent on test cases is paid off since no debugging has to be done at the end. Time and effort can be distributed and planned in advance in MDD. However, in TDD, since the amount of time and effort for the next user stories is hard to predict, it is difficult to plan. Some user stories take less amount of time while others consume lot of time. This can be seen in the case study. Most people said that finding zodiac sign took very less time and effort compared to finding the number of shopping days till Christmas . Pros and Cons of Using MDD approach From research and experience, these are some of the observations that were made on the MDD approach in general. A model in projects has following advantages It helps to break down the project into smaller code development pieces or modules which can be assigned to different teams. It helps each team to understand their role and how their part of the development is integrated into the whole product development The project managers and team leaders will understand on how to integrate all the modules and do testing. The end user will be able to visualize the integrated end product. If enough of time is spent in building a model properly, even though it takes time and effort, it will greatly reduce the time to build the product. A properly built model will also help in reducing the iterations of testing process, thus creating the integrations much quicker. There is also an economic advantage of building the models. A model will help to present a product to the investors easily and attract investments to fund the projects. Some disadvantages of using MDD approach The disadvantages of using MDD approach are not related to the approach itself, but rather it is related to the application of this approach. If MDD is not used properly, there will be extended delays in the product developments. Some of these possible setbacks are Building a Model will take lot of time and resources. MDD is not always â€Å"fit for all approach†. The project and product has to be analyzed before this approach is taken. Some people visualize a Model as an abstraction layer hiding all the complications of the product development process. Too much of abstraction may be good to certain audience in the project, but it over all defeats the purpose of building a model in the first place. So, care should be taken as not to ABSTRACT too much. If proper resources, such as, proper Domain experts are not involved while building a model, then the model as well as end product will be disastrous failure. MDD should not always be thought of the end point. Always underlying approach for each module should be associated with proper testing. Failure to consider the real life situations also causes the MDD unusable. The key to the whole process of Product development using MDD approach is having a proper liaison between Business group and IT group. Pros and Cons of Using TDD approach Some of the advantages of using TDD are: Since test cases are developed first, developer understands the requirements thoroughly in order to write them. The focus is on the functionality perspective of the client. TDD involves taking small steps at a time and focusing on one task at a time. Even though it consumes lot of time to write many unit test cases covering all possibilities, this makes it an advantage as it avoids debugging at later stages in the project. Finding bugs as early as possible is always beneficiary in terms of time and cost. Fixing bugs at a later stage is difficult because it is hard to determine what caused the bug. Since just enough code to pass the test is written, TDD will result in thorough testing covering all possible paths. If tests are written well, then it will produce stable code. Code is developed faster and there is working piece of code at every level, which inspires confidence and encourages the developer. Developer is aware of the progress made and can set goals to achieve a particular goal. TDD results in good design because of many factors. With experience, TDD can be a very effective method as it lets the developer think in small units of code leading to modularity and good design. This is also the result of looking at the problem from customers perspective to understand how it will be implemented. Refactoring also leads to producing good designs. Mocking and faking is beneficial in the sense that it will define the boundaries of the classes. This is because through mocking, you will find out what your classes should and should not know about the other class. This is the basic essence of encapsulation in any object oriented language. The test cases provide support for faster regression testing. On next iteration or anytime in future, when you add more tests, you can run all the tests to make sure that it works and if it doesnt, it is easy to see what part of the code broke. Some disadvantages with TDD approach are: TDD requires commitment and supporting management. Developers should be committed and write proper tests. If the tests are deleted or changed accidentally or purposefully, it will give false impression that the code is bugs-free. Support from management is important and they have to believe that this methodology works. If either of them does not exist, then TDD approach fails. Functional tests need to be done for programs that use a database or for creating user interfaces. For such things, using TDD approach is difficult. Tests and code are written by the same person most of the time and if the developer overlooks certain things, then it will affect the code as well and may not result in what is supposed to happen. If he interprets the requirements wrong, then the tests he writes and the code that implements them will turn out to be wrong and will lead to code that will not be as efficient as it should be. Another example would be if the developer doesnt check for certain specific inputs, then the code that needs to implement that will never be implemented. Having large number of working unit tests may build up over confidence that will lead to less concentrations on additional activities such as quality assurance evaluations. Unit tests only tell if the piece of code you wrote works. Other tests such as domain testing, integration testing, etc have to be done. Amount of coverage and details of testing that is done in TDD development cannot be reproduced at a later stage. So, these tests become an important aspect and it is necessary that they are well-written. There is no way to predict the type of user stories and it is not possible to gain a complete understanding of the system from the user stories. This leads to extensive code rewriting and refactoring. WHEN to use WHAT? This leads to the question of when is it appropriate to use TDD and when is it appropriate to use MDD. Software development is a process of developing a product to meet a certain business need. In a well defined environment and in large houses Software Development is done using the techniques described in Software Engineering and experience gained over the years. Many factors have to be taken into consideration when deciding on the methodology to use. These include things such as type of organization, management, type of project, experience of the developers, and availability of effective tools. Type of Project: Software development is done under two major circumstances 1. To develop altogether a new product a. A product that never existed before, but there is a need in the minds of people. A great example of this in recent years is ‘Youtube. There was no such product before, however, people had thought about having some kind of sharing videos. So, there is direc

Dominant Women in Society :: essays research papers

In the story Hunger as Ideology by Susan Bordo women are portrayed as passive and inferior to men. Bordo looks into advertisements to prove her point about how visible it is that women are how they are suppose to be dainty and quaint. In the movie â€Å"The Thomas Crown Affair† it is totally opposite; the woman in this story is independent, strong, and self-reliant. She is able to outsmart him and prove to him that she is able to survive without any help. The modern women has transformed and broken the stereotype and have made their way into society as an equal. Nowadays, advertisements depict how women should act, dress, and eat. For example in Hunger as Ideology, it show two different advertisements for Haagen-Dazs Ice cream, one with a man who just finished a half-pint smiling, the other with a woman who just took a bite from her ice cream bar. Although very discreet, the message is visible to consumers. Another example, are the sugar-free Jell-o ads, where an attractive slender woman is leaning back on a chair eating jell-o from a glass. Above the picture is a quote which says, â€Å"I’m a girl who just can’t say no. I insist on dessert†. To the side of the ad, it states, â€Å"Every woman is entitles to her just desserts. Just as long as dessert is Sugar Free Jell-O Gelatin. It’s light and fruity and fun. And it’s only calories.† This ad emphasizes on how women want dessert, but its only okay to have it if its sugar free. â€Å"The dessert you don’t have to desert† because itâ€⠄¢s sugar free. Same concept with the Wonder Light Bread, in this ad two women are side by side on a park bench one holding a carrot, the other happily smiling with a sandwich and the ad saying, â€Å" You’ll think your cheating, but you know your not†¦It’s Wonder Light bread†. These ads accentuate how its okay to eat a lot, as long as you eat â€Å"light†. Women look upon these ads and are convinced that this is how they are suppose to be, but in the Thomas Crown Affair, the message is completely opposite. Catherine Banning, is the insurance lawyer for the case against the stolen Monet painting in the â€Å"Thomas Crown Affair†. It is evident that she is a strong independent woman who needs not to rely on anyone especially a man.

Lawrence Ferlinghettis Politics :: essays research papers fc

Lawrence Ferlinghetti's Politics I hope I won't seem too politically incorrect for saying this but after immersing myself in the writings of the guilt-obsessed asexual Jack Kerouac, the ridiculously horny Allen Ginsberg and the just plain sordid William S. Boroughs... it's nice to read a few poems by a guy who can get excited about a little candy store under the El or a pretty woman letting a stocking drop to the floor (â€Å"Literary Kicks†). For casual reading, Lawrence Ferlinghetti's poetry is cheerful and humorous. At best it is a welcome break for the mainstream of the â€Å"beat generation.† Inside his poetry, deep rooted criticisms of the United States exist. Ferlinghetti has had an anti-government attitude since the 1950's. His beliefs strengthened when he was put on trial for publishing a highly controversial collection of poems written by Allen Ginsberg. Lawrence Ferlinghetti has chosen to express his political views through his poetry. Additionally, Ferlinghetti became more vocal with the use of protests and further publication of controversial and/or anti-government materials through his publishing house, New Directions. By using poetry, Ferlinghetti was able to reach a vast audience including those whom he was criticizing. Through his poetry, Lawrence Ferlinghetti blatantly and subtly criticized the American democratic system and politicians.   Ã‚  Ã‚  Ã‚  Ã‚  In 1957, Ferlinghetti received his first national attention. Ferlinghetti was arrested and brought to trial as the publisher of a collection of obscene poetry, Howl and Other Poems by Allen Ginsberg (Alspaugh 1148). Eventually he was cleared of the charges of â€Å"publishing and sale of obscene writings.† Since his involvement in the obscenity trial, Ferlinghetti became quite cynical of the government. After the trial ended, Lawrence Ferlinghetti canceled all government grants coming to him and to any writers under his publishing house. Currently he still disallows the acceptance of government grants to any of his writers (Alspaugh 1146). Economically speaking, Ferlinghetti did benefit from the trial. The publicity created by the trial attracted new names to New Directions Publishing. The publicity also was great enough to propel Lawrence Ferlinghetti's image to the degree where he could successfully release his second collection of poetry, A Coney Island of the Mind. In most of Ferlinghetti's work, he has shown a concern with political issues. â€Å" His poetry often addresses political subjects...† (Nasso 196). The Kennedy Assassination, McCarthyism and the Vietnam conflict were all topics in several Ferlinghetti poems (Oppenheimer 136). Lawrence Ferlinghetti's past incidents involving the government influenced his poetry and consequentially he has little respect for government. â€Å"Ferlinghetti's... poetry offered blatant tirades against the destructive tendencies of America's political leadership† (Trosky 136).   Ã‚  Ã‚  Ã‚  Ã‚  Politics are themes in virtually all of Ferlinghetti's works.

I Never Promised You a Rose Garden by Joanne Greenberg Essay examples -

"I Never Promised You a Rose Garden" by Joanne Greenberg Schizophrenia has long been a devastating mental illness and only recently have we begun to see an improvement in our capabilities to treat this disorder. The development of neuroleptics such as, Haldol, Risperidal, and Zyprexa have given psychiatrists, psychologists and their patients great hope in the battle against this mental disease. However, during the 1960s, drugs were not available and psychologists relied upon psychotherapy in order to treat patients. I Never Promised You a Rose Garden, is a description of a sixteen-year-old girl's battle with schizophrenia, in the 1960s. Deborah Blau’s illness spanned three years, in which she spent her life in a mental institution. The book itself is a semi-autobiographical account of Joanne Greenberg’s experiences in a mental hospital during her own bout with schizophrenia. She presents her experiences by relating them to Deborah. The novel was written to help fight the stigmatisms and prejudices held against mental illness. In the late 1960s, reactions to mental illness generally fell between two polarized attitudes. One, popular with the counterculture generation, romanticized mental illness as an altered state of consciousness that was rich in artistic, creative inspiration. The protagonist of this myth was the tortured artist who poured out his or her soul in writing or art between periods of mental breakdown; Sylvia Plath, Vincent Van Gogh, and Virginia Woolf are only a few such individuals whose artistry is practically inseparable from the idealized myths of their mental instability. Often their periods of mental breakdown were a source of inspiration, but before one romanticizes their mental illnesses, it necessary to remember that all three committed suicide. On the other end of the spectrum, mental illness was stigmatized as a weakness or fatal flaw on the part of the sufferer. Even today, many uninformed people regard mental illness as a stigmatized condition, shrouded in shameful secrecy and negative stereotypes, to be described with frightening or belittling euphemisms. In the late 1960s, when Greenberg's novel was published, mental illness was even more misunderstood and feared. The reading public had absorbed centuries of inaccurate information about mental illness, all based on prejudice, ignorance, and fear. Because of he... ... is sufficient to treat schizophrenia. Still, these new findings certainly do not invalidate the importance of empathy and understanding in the treatment of schizophrenia. Greenberg's desire to garner sympathy, respect, and understanding for sufferers of mental illness is still a valid concern, and her novel remains valuable as a sympathetic portrayal of mental illness. Although this novel uses outdated treatment methods, it does succeed in allowing the reader to see into the mind of a mentally ill person. Greenberg portrays the problem of mental illness from different perspectives. She details Jacob and Esther Blau's struggle with self-doubt, blame, and the stigma of their daughter's sickness. The novel also portrays the difficult, stressful work required of the medical professionals and the staff who work with mentally ill patients. However, most importantly, Greenberg portrays the experience of mental illness from the patient's point of view. Struggling with mental illness is not glamorous or easy. The road to recovery is lined with setbacks, doubt, and fear. It takes a great deal of courage and perseverance on Deborah's part to face her illness and fight it through treatment.

What Continues to Make Othello Worthy of Study

William Shakespeare's classic tragedy, ‘Othello’ written in approximately 1603, continues to be studied and appreciated even now in modern society, more than four hundred years after it was written. Apart from the obviousness of Shakespeare’s ability to use diction to draw in the audience, ‘Othello’ has many qualities which allow it to be interpreted and re-interpreted through time. It can relate to any audience and context because its varied themes, values and ideas, remain relevant to all societies making it possible for anyone to relate to ‘Othello’ on some level. This, along with Shakespeare’s depiction of common human emotions, and his ability to portray these in such a realistic manner continues to make ‘Othello’ worthy of critical study. The universality of Shakespeare’s themes are evident not only in ‘Othello’ but in almost all of his works. The most apparent theme in the text is that of jealousy. Iago importantly warns, ‘O, beware, my lord, of Jealousy. It is the green-eyed monster which doth mock the meat it feeds on’ (act 3, scene 3). This warning is directed at Othello, but is also important for Roderigo and Iago himself. Although Iago could be called one of the most diabolical antagonist/villains in literature, his actions are spurred by such common human emotions; jealousy and greed. Jealousy acts as a great literary device in the text because it is an extremely universal emotion which almost all living creatures are capable of feeling, and this gives the audience an emotional attachment to the characters and plot. It allows the audience to feel sympathy for the characters. Othello’ plays with the jealous nature of the characters, such as Iago’s envy of power and position, along with his suspicions about his wife. These things encourage the plot, and initiate the series of events to unfold during the text. Through Iago, Shakespeare conveys the lengths to which a man will go to achieve his objective. Iago’s manipulativeness causes Othello to become a victim of unfounded jealousy, and this drives the entire plot. Furthermore, Iago’s hatred and jealousy is fueled by his racism. The audience is constantly reminded of Othello’s colouring through the character’s dialogue, motives and actions. Shakespeare creates vulgar visual imagery with the metaphor, â€Å"Very now, an old black ram / Is tupping your white ewe. † (act 1, scene 1) . Unfortunately, racism and prejudice are common throughout history as minorities and groups are deemed lower than others, and this continues still to this day. Division and stereotyping of groups due to race, sex, sexuality and ability have existed through the ages, and unfortunately will continue to exist. Another discernible theme in ‘Othello’ is love. This emotion too is universal emotion, and the impulsiveness and compulsion to disobey family that love can generate is shown through Desdemona’s willingness to deliberately disobey her father in order to secretly marry Othello. Romance today is one of the most popular literary genres, and can be enjoyed by all ages, in all societies. Shakespeare’s ‘Othello’ has been adapted to suit modern society such as in the film ‘O’, and interpreted in different media, including dramatical performances, opera, ballet, television shows and films. All of these provide different interpretations of the text and demonstrate the adaptability of ‘Othello’. Shakespeare’s poetic and beautiful language and his use of themes such as love, power, revenge, war and jealousy are timeless. His depiction of human ideas and paths of action are also timeless, as humans basic senses will remain the same. These factors, compounded with Shakespeare’s ability to continually challenge oncoming generations, both in the literature and dramatical sense, make ‘Othello’ timeless and worthy to continue to be studied in modern society and after.

Effectiveness Of Temporary Anchorage Devices Health And Social Care Essay

One of the most normally treated orthodontic jobs is the Class II molar malocclusion. Class II malocclusions represents a important part of the patients who typically present for orthodontic intervention. Deciding Class II molar relationships by distalizing maxillary grinders may be indicated for patients with maxillary dentoalveolar bulge or minor skeletal disagreements ( but non for those patients who besides exhibit important dental crowding ) . Maxillary molar distalization is a often used intervention method in instances with herding associated with dental Class II grinder relationship and Class I skeletal relationship To rectify a Class II dental malocclusion or to make infinite in the maxillary arch by a nonextraction protocol, maxillary grinders can be moved distally and thereby derive infinite and change over the Class II grinder relationship to a Class I. Then, the grinders are held in topographic point whereas the bicuspids, eyetooths, and incisors normally are retracted by conventional multibracket techniques Appliances to distalise grinders can be classified in several ways and one categorization can associate to if the contraption is a patient conformity ( extraoral grip or removable contraptions ) or a non-compliance distalization contraption ( intraoral fixed contraptions ) . Patient conformity contraptions Traditional patient compliant contraptions for molar distalization include extraoral grip, Cetlin removable home base, Wilson distalizing arches and intermaxillary rubber bands. For more than 100A old ages the most common process has been the headgear applied to upper grinders, and its public presentation has been dependable. Non-compliance contraptions Successful orthodontic treatmentA frequently relies to a great extent on patient co-operation in the erosion of headdress, intermaxillary rubber bands, or removable contraptions. Conformity with headdress is seldom optimum ( Cureto et al. , 1994 ) . Clinicians have concerns aboutA the safety of headgear to do oculus and facial tissue harm ( Samuels, 1996 ) .. As a consequence many clinicians prefer to utilize intraoral distalizing systems that cut down the conformity of the patient and are under the orthodontist ‘s control. These non compliant contraptions minimize the demand for such co-operation and effort to maximise the predictability of consequences Most of the intraoral distalizing systems consist of a force bring forthing unit and an anchorage unit ( normally consisting bicuspids or decidiuous grinders and an acrylic Nance button ) . Different types of active force constituents includes for illustration driving magnets, superelasic spiral springs and beta Ti metal springs. Such devices include the disgusting magnet, spiral springs on a uninterrupted arch wire, A superelastic nickel-titanium arch wires, A spiral springs on a sectional arch wire ( Jones gigue, A distal jet, A Keles skidder ) , and springs in beta Ti metal ( pendulum, A K-loop, A intraoral bodily molar distalizer ) . Distaljet CaranoA etA Al. ( 1996 ) describedA theA designA and useA ofA thisA applianceA . Bilateral tubesA ofA 0aˆ?036-inch internal diameterA areA attached toA anA acrylicA Nance button.A AA coilA and prison guard clampA are slid overA theA tube.A TheA wire fromA theA acrylic terminals inA aA bayonet bendA and insertsA intoA aA palatine sheath onA theA molar band.A TheA forceA acts throughA theA centreA ofA resistanceA ofA theA molarA and therefore is said to translateA theA tooth.A TheA Nance button isA alsoA attached toA aA premolar bandA viaA aA linking wire.A TheA contraption isA activated by slidingA theA clinch closer toA theA molarA and can be converted toA aA conventionalA Nance by severingA theA fond regard toA theA premolar bands.A Teeth during orthodontic intervention are exposed to forces and minutes, and these moving forces ever generate mutual forces of the same magnitude but in opposite way ( Newton ‘s 3rd jurisprudence ) . To forestall unwanted tooth motions and keep intervention success, these mutual forces must be diverted. Orthodontic anchorage, defined as the ability to defy these unwanted reactive tooth motions, can be provided by other dentitions, by extra-oral devices, by support from the muscular structure or from skeletal beginnings. ( Proffit,2000 ; Roberts et al,1994 ; Wehrbein et Al, 1999 ; Melsen et Al 2000 ) . The non-compliance intra-arch grinder distalizing methods chiefly rely on a Nance button to reenforce the anterior anchorage. A figure of surveies have shown that despite the effectivity of many of these contraptions in traveling posterior dentitions distally, the Nance button does non supply absolute anchorage both during and after molar distalization. As a consequence they all produce a certain sum of anterior anchorage loss-mesial motion of grounding dentitions and proclination of maxillary incisors. In add-on, they besides tend to bring forth some distal tipping of the maxillary grinders, instead than pure bodily motion. These restrictions introduce inefficiencies into the Class II rectification, specifically, round tripping of the incisors and posterior anchorage loss during the abjuration of the other maxillary dentitions. With these contraptions one time the grinders have been distalized, some patient conformity is frequently required during distalization of bicuspids and anterior dentitions by agencies of Class II rubber bands, Class II rubber bands on skiding gigues, etc. However, surveies have shown the Distal-Jet produces a better bodily molar motion. Surveies on the distal-jet have shown they overcomeA theA disadvantagesA ofA otherA contraptions for distalizing molarsA by reducingA the inclination forA theA dentition to tip. TheA writers claim thatA theA rateA ofA motion is comparable toA theA Jones Jig or magnets, A and isA achieved by bodily translation.A No clinical tests have been published on thisA contraption In orthodontias accomplishing absolute anchorage has been a really of import subject of involvement. Skeletal anchorage ( Young et Al, 2007 ) is a technique which uses some signifier of bony ground tackle to supply absolute anchorage ( ie no unwanted tooth motion ) . These do non necessitate patient conformity, supply more predictable and efficient intervention options. Skeletal anchorage can be derived from dental implants ( osseointegrated ) , surgically placed mini home bases ( on-plants ) , or with mini -screws ( AKA TADS ) . Molar distalizing contraptions have been combined with assorted osseo-integrted implants to accomplish osteal anchorage and get the better of the restrictions of the above tooth-supported contraptions. Their usage for orthodontic anchorage has been good documented in the literature but they have restrictions when used for this purpose eg, their big size, a period of healing is needed to let osteal integrating of the implant before a force could be applied. the careful implant location needed, and the possible trouble and surgical injury of remotion after intervention is completed ( Roberts et al, 1984 ; Roberts et al,1990 ; Turley et al,1988 ; Wehrbein et al,1993 ) . Mini prison guards ( aka impermanent anchorage devices ) are little titanium metal chromium steel steel surgical bone prison guard, runing from 6 to 12 millimetres in length and 1.2 to 2 millimetres in diameter. They are placed into either buccal or palatine bone. ( Mizrahi,2007 ) temporarily to heighten orthodontic anchorage. Harmonizing to Cope,2005 a impermanent anchorage device ( TAD ) is a device that is temA ­porarily fixed to cram for the intent of heightening orthA ­odontic anchorage either by back uping the dentition of the reacA ­tive unit or by rid ofing the demand for the reactive unit wholly, and which is later removed after usage. They can be located transosteally, subperiosteally, or enA ­dosteally ; and they can be fixed to cram either automatically ( cortically stabilized ) or biochemically ( osseointegrated ) . The footings such as miniscrews, miniscrew implants, mini implants, microscrews, and impermanent anchorage devices ( TADS ) have been used. There is no general understanding on the terminology ( Cornelis et al,2007 ; Mah J, 2005 ) . TADS were developed in response to the jobs outlined earlier with conventional implants.Their advantages, in add-on to size, include minimum anatomic restrictions, minor surgery, increased patient comfort, immediate burden, and lower costs ( Miyawaki et al, 2003 ; Costa et al,1998 ) . The first clinical study in the literature of the usage of TADs appeared in 1983 when Creekmore and Eklund used a vitallium bone screw to handle a patient with a deep contact overbite. The prison guard was inserted in the anterior rhinal spinal column to irrupt and root and rectify the upper incisors utilizing an elastic from the prison guard to the incisors. In 1997, Kanomi reported the use of mini prison guards for orthodontic anchorage. Since this instance study, there has been an detonation of extra studies of mini prison guards for orthodontic anchorage ( Lee et al,2001 ) . Examples of mini prison guards include the Aarhus, Spider screw, Dual Top, A Absoanchor A and IMTEC. Non-compliance distalizing devices can integrate miniscrews connected to the Nance button for reenforcing the anchorage and avoiding side-effects in the anterior part. Purposes Some surveies have been published refering the intervention result of the distal jet contraptions for distal motion of maxillary grinders. However, some publications are non recent and non may RCT ‘S. instance series, instance studies or method descriptions but merely a few prospective controlled surveies. So far there exists no randomised test comparison Because TADs are a comparatively new add-on to intervention and most of the published literature consists of instance studies and instance series, there is limited systematic reviews/RCT ‘S. The purposes of this article were to reexamine and critically analyze systematic reviews/RCT ‘s available for comparing distal jet and TADS as methods of distalizing maxillary first grinders in the intervention of category II malocclusions Aims Undertake a hunt of the published literature. 2. Synthesize the information from the relevant documents. 3. Critically appraise the documents selected for reappraisal. 4. Suggest clinical guidelines based on the grounds. Method A literature hunt will be perA ­formed by seeking the electronic databases ( 1990 onwards ) ; MEDLINE database ( Entrez PubMed ) , Web of Science and the Cochrane Library. Randomised clinical tests ( RCT ‘s ) and systematic reappraisals refering distalisation of maxillary grinders will be considered. Footings used in this literature hunt will include: category II maloclussion, distal maxillary molar motion, intra-oral contraptions, distal-jet contraption, mini-screw, impermanent anchorage device ( TAD ) , systematic reappraisals, randomised control tests. We used the footings †mini-implant, mini prison guards, TADS † in the article, because it is presently the most often used in the orthodontic literature. The undermentioned inclusion standards will be used to choose appropriate articles: articles on utilizations of mini prison guards and distal jet, category II maloclussions, mild crowding, none extraction instances, informations merely from human topics, linguistic communication in English, randomized conA ­trolled surveies ( RCTs ) and systematic reappraisals. Exclusion standards included articles on headdress, removeable contraptions, osseointegrated dental implants, onplants, palatine implants, miniplates ; implant stuffs reA ­search ; carnal surveies ; old orthodontic intervention, old instance studies and instance series ; technique presentations of mini-implant and microimplant ; in-vitro surveies ; reexamine articles and letters and articles in a linguistic communication other than English. The information collected in this survey will be grouped and analyzed in footings of sum of molar distalization, tipping and rotary motion. Besides the sum of anchorage loss of incisors ( mesial motion ) will be assessed. Timescale Literature hunt January 2011 Critical assessment Feb/March 2011 Data synthesis April 2011 Discussion May 2011 Submission of undertaking 1 September 2011 Ethical consideration No moralss commission blessing required – a Literature Review. Key Mentions Samuels, R. H.A A. ( 1996 ) A AA reviewA ofA orthodontic facebow injuriesA and safety equipment, A American JournalA ofA OrthodonticsA and Dentofacial Orthopedics, A 110, A 269-272 Cureton, S. L. , Regennitter, F. J.A and Yancey, T. M. ( 1993 ) A TheA roleA ofA theA headgear calender in headgear conformity, A American JournalA ofA OrthodonticsA and Dentofacial Orthopedics, A 104, A 387-394