Laboratory Techniques and Measurements Lab 1 (Labpaq) free essay sample

Throughout lab one we were introduced to many different forms of measurement, whether its using a ruler too measure length, a digital scale to measure weight, and also many different sized and shaped flasks to measure different volumes. Another key measurement of this lab was to teach the student about density and how to measure it. Density tells us that it is defined as the mass per unit measure, in which as we know is most oven referred to as volume and is also used to describe how heavy something is. We were also required to calculate many different measurements do to the number of moles that one substance might have due to the amount of material/solution we are currently working with. Along with all the measurements and how to use them correctly that Lab 1 teaches us, it also presents to use how to record our data correctly using Significant Figures. We will write a custom essay sample on Laboratory Techniques and Measurements Lab 1 (Labpaq) or any similar topic specifically for you Do Not WasteYour Time HIRE WRITER Only 13.90 / page Significant figures are the number of digits that we may use including or excluding the zeros that we may be given with any number or solution. There are many different rules in determining the proper number of significant figure in an answer. For example; â€Å"All zeros to the right of the decimal place and to the right of a non zero digit are consider significant†. So we were given the number 45. 000, we know from the rule above that this figure has 5 significant figures because the zeros following he unit are behind the decimal place and are considered significant. My Hypothesis for this lab was simple, can I or can I not make the proper measurements using the provided materials and measuring devices included for this lab. Along with making the appropriate measurements, will I be able to use the rules I was taught and record my data with the correct significant figures? This lab is all about measurements and recording them properly. The lab first introduces to use the measurement of centimeters, millimeters, and meters to measure different household objects in our everyday life. We were given the task to use the provided ruler and measure a CD, key, spoon, and a fork in centimeters and then convert our findings to give us the appropriate units of millimeters and meters for each object required in the exercise. Data Table 1: Length measurements. | Object| Length (cm)| Length (mm)| Length (m)| CD or DVD| 12cm| 120mm| . .12m| Key| 5. 5cm| 55mm| 0. 055m| Spoon| 15cm | 150mm| . 15m| Fork| 18cm| 180mm| . 18m| Lab 1 also teaches us the importance of molecular weight of a substance and how to use that to find the amount of moles of that substance in a solution. For example; in exercise 3 we were asked to weigh 8 grams of sugar and then calculate how many moles of sugar it really was. Using the molecular weight of sugar (C = 12. 01 grams/mol, H = 1. 008 grams/mole, O = 15. 00 grams/mole). We were then able to use this molecular mass of the sugar that we then had to use to calculate and determine the molarity of the sugar solution that we were working on for exercise three. Data Table 8: Initial Concentration. | Chemical| Mass(g)| Molecular Weight (g)| Moles in Volumetric Flask| Total Volume (L)| Molarity(mol/L)| Sugar(C12H22O11)| 8. g8. | 28. 018g| 0. 29 | . 0025L| 116 mol/L| My analyses of this lab is like so. The lab presented itself with great learning options for teaching us how to use and proper measure the different units of the Si system, but as easy as they are to learn there are many of possible solutions for error. Since this was the first lab the many of the students have probably done in a couple years, I see plenty of room for h uman error do to the lack of training or experience with most of the lab equipment required to compete this lab to the full. Not only is there room for human error but there are also the possibilities of error with the lab equipment whether it is the student’s fault or just default equipment. For example, if the digital scale, required for most of the lab, is not tarred right, your numbers from your experiment are going to be way off. One wrong calculation or measurement could ruin a whole exercise if not whole entire lab itself. In my conclusion for this lab was pretty accurate to my hypothesis. I was able to make most of the appropriate measurements with little to no error at all. I had trouble with the density at first seeing I have never used the method for calculating density. After a few tries I was able to succeed in calculating all the appropriate calculation required for this lab as well as using the appropriate significant figures for all my answers in my lab right up. Measurements are all around us in our daily life. We use some sort of measurement on a daily bases whether we know it or not. Without measurement or the SI units we would have no since of idea of how much something may way or weather or not the water was going to fit into a single are or space (density). The unit of measure is used so much throughout the world everyday that without it, the world would have no since of weight, mass, height, width, or any other unit from the Si family. We use this form of description for almost everything living and non-living in our world today.

How to Write a Research Paper in MLA style

How to Write a Research Paper in MLA style When writing, it is of paramount importance that one formats their paper using one of the accepted styles available. One of the commonly used formatting styles when writing research papers is MLA. This style refers to a writing method recommended by the Modern Language Association. This style is mostly used in humanities, more particularly in language related papers such as literature, as well as manuscripts. Other humanities, such as history, may require a different writing style. When using the MLA style, one should use the standard, white 8.5 x 11-inch paper. The text should be double-spaced, and typed using a legible font. The recommended font is Times New Roman with a 12 pt size. One should leave a single space after a full stop or any other punctuation mark. The margins of your document should all be set at 1 inch. For well presented and organized work, the first line of each paragraph should be indented one half-inch from the left margin. In MLA, it is recommended that one uses the Tab key to indent, instead of pressing the space key five times. A key feature of MLA is that one uses parenthetical citations to acknowledge work borrowed from another person. When making the citations, one is supposed to use present tense for quoted material, as well as for personal comments. The past tense is used when reporting a historical event or when making a direct quote. The works used are then listed on a page at the end of the paper. Research papers written using MLA do not have a separate cover page, unless the given instructions state otherwise. The header is placed at the upper right-hand of your paper, along with your surname. The header should also be in Times New Roman font, at 12 pt font size and double spaced. However, this too may vary depending on the instructions given. After the header, at the upper left-hand corner of your document, write the student’s name, tutor’s name, course and the date. The title then follows in Title case. It should be in bold and centered. Notably, it is essential to always write work that is free from plagiarism. Due to this, one should always make references to the owner of the work used through in-text citations and by listing the work on the page. There are a number of websites that provide guides on how to write in MLA format, one being the Purdue Online Writing Lab. Please refer to one of these for further details on how to make in-text citations and list sources used on the page. All in all, if you need assistance with writing an MLA style research paper visit our custom writing service and our writers will write a custom paper in MLA format starting at $10/page.

Logic According to Husserl Essay Example | Topics and Well Written Essays - 1000 words

Logic According to Husserl - Essay Example It helped us to predict the existence of certain things which were unknown to us earlier. Husserl defined logic in a different manner. He has attached various dimensions to logic in order to analyze it comprehensively. According to Husserl â€Å"Logic is the science of science† (Husserl p.8). This paper analyses the arguments of Husserl with respect to logic and transcendental logic along with his criticisms against formal logic. â€Å"Logic, as Husserl sees it, is concerned in the first place with meanings (propositions, concepts) and with associated meaning-instantiating acts. Most importantly, it is concerned with that sort of deductively closed collection of meanings which constitutes a scientific theory†(Corazzon). In other words, Husserl pointed out that logic helps us to deduce certain scientific theories which were unknown to us earlier. He has pointed out that science has no existence without logic. All scientific theories were evolved out of logical thinking. For example, we assume that electrons revolve around certain nucleus in which protons and neutrons are located. This scientific theory is formulated based on logic rather than experimental conclusions. The stability of an atom can be explained only with the help of such an atom model described above. In other words, logic helped us to device a new scientific theory. ... For example, until recent times, science educated us that no object can move faster than light. However, some of the recent scientific discoveries are pointing towards the existence of a particle which is capable of moving much rapidly than light. Many of the basic scientific theories such as Einstein’s relativity theory may undergo modifications because of the new discovery. In other words, logic and science need not provide us correct explanations always. â€Å"The central position of the theory of judgement in the total problematic of formal logic is due to material as well as historic grounds†(Husserl and Landgrebe, p. 12). For example, we predict the arrival of different seasons based on historic facts. Historically, December is the coldest month at many parts of the world. So, people always expect December to be the coldest month in coming years also. Formal logic forces us to think in that manner. However, because of global warming problems, climate changes are t aking place everywhere in the world. Unexpected rains and droughts are taking place everywhere now. Under such circumstances, it is quite possible that the coming months of December may not be as cold as it before. In other words, formal logic may not provide us true information always. â€Å"Formal logic does not inquire into the differences in the mode of pre-givenness of objects. It enquires only into the conditions of self-evident judging†(Husserl and Landgrebe, p. 21). It should be noted that formal logic is the self-interpretation of reasons and therefore it is highly subjective. No two individuals are alike either physically or intellectually. Because of the differences in intelligence, different people formulate reasons differently. For

Understanding the Concepts Essay Example | Topics and Well Written Essays - 250 words

Understanding the Concepts - Essay Example These include the profit ratios like the Gross Profit & Net Profit Margins, Earnings per share, and Return on Assets, the liquidity ratio like the Current Ratio, and Quick Ratio, the activity ratios like the Average Collection Period, and the Inventory Turnover Ratio, and leverage ratios like the Debt Ratio, and Equity Ratio (Vickers, 2005, p.117). However, in larger corporations, besides the above mentioned ratios, certain other ratios like Accounts Receivable Turnover, Fixed Asset Turnover, Total Asset Turnover, Price-to-earnings Ratio, and Price-to-book value, to name among others (Lee, Lee & Lee, 2009, p.33). These ratios provide with further detailed analysis of a company which a small business might not require unless it is grown big. The above study has reflected on the fact that financial ratios are highly significant for every organization. However, depending on the size of the organization, the need for the different financial ratios to be determined might

The Glass Menagerie' by Tennessee Williams Essay

The Glass Menagerie' by Tennessee Williams - Essay Example Jim O'Connor, the gentleman caller, bears the same name as the young man who called on Rose Williams, before her descent into insanity. The action takes place in a small apartment in a poor district of the city, crowded outside and in, surrounded by many dark alleys and fire escapes, exploring the illusory lives of the three main characters as they attempt to achieve their dreams, only for it all to end in failure and disappointment. It has been interpreted variously as a psychological drama portraying a dysfunctional family, the tragedy of a fragile psyche (Laura) edging into madness, and a socio-political statement, "his personal testament to the Great Depression" (p.20, Hale, 1998). It is all of these as becomes apparent as the action moves from the past to the present as Tom's recollection are recalled and Character Analysis - Tom Wingfield: Tom is a poet, working in a boring low paid job in a shoe factory, the main economic support for his mother and sister. Despite his position as the main provider, an adult male, he is denied that status, simply by how his mother perceives things should be, rather than what they are, and by her demands on him to be that provider until another appears (a husband for Laura). He is complex, shy and intelligent, his creativity dismissed and ridiculed by his mother. He seeks escape through the illusions of the movies, but recognizes the reality of the times in which he seeks his dreams: Tom: "Hollywood characters are supposed to have all the adventures for everybody in America, while everybody in America sits in a darkened room and watches them have them! Yes, until there's a war. That's when adventure becomes available to the masses!....Then the people in the dark room come out of the dark room to have some adventure themselves-...." (Williams, 1936, Scene Six, p. 282) Some connection to socialist values appear when Tom paid his dues to the Union of Merchant Seamen, rather than the electric bill - thus highlighting a belief in the unions and socialism, as opposed to capitalism. His relationship with his mother is volatile, as she is the nagging presence preventing his escape and fulfillment. He loves his shy, fragile sister and the most telling example Williams's lyrical language and symbolism which elicit poignant imagery and the emotion of guilt can be found as he reflects on his escape. Tom: " I didn't go to the moon, I went much further - for time is the longest distance between two places...Perhaps I am walking along a street at night, in some strange

Project failure in the software industry

Project failure in the software industry Introduction: Project failure is a common thing heard in the Software Industry in recent years. It has been observed that almost 50% of the projects in the Industry fail due to many various reasons. Research shows that Project failure is not due to one particular reason but many reasons contributing to it. The Standish Group [1995], found in their survey that of all the projects only 1/6 of the projects were completed on time and within the specified budget. They also found that 1/3 of the projects were cancelled and more than  ½ of them were considered challenged. In these cancelled and challenged projects about 189% were over budget, 222% were behind schedule and only 61% of the requirements were met. Factors contributing to project success are to complete it on time, should be under budget and should meet the requirements completely, but generally these dont meet the expectations which results in project failures. The most common reasons for project failures are lack of user involvement, unre alistic time scale, poorly defined requirements, poor testing, miscommunication and difference of opinion between team members, etc. Since now most of the companies use software for various operations, it is a must for every company to avoid project failures. A huge amount of money is spent on making software, therefore it is important to analyze and understand the reasons behind the various reasons behind project failures. The graph below shows various reasons for failure and the percentage to which each factor contributes. The above graph and the percentage of failures show that it is normal for a software project to fail due to various reasons. But the point is what we can do to avoid it. For that we need to understand the various reasons for failure and the steps to avoid them. Reasons for Project Failures: Vague Requirements: Requirement gathering is the first step of any project development life cycle. Any project starts with the understanding and analyzing the requirements of the customer. Often the requirements are not clearly specified and the manager assumes the requirements as per his/her understanding and asks the developers to start developing the product which results in not meeting the exact requirements of the stakeholder. Many times the customer, himself/herself is not aware of what they want as keep changing the requirements on regular time intervals which results in delay of product delivery, increased cost and inefficient product. Many times due to time constraint the developers start the project assuming requirements and start developing it, thinking that the requirements will be fulfilled once we start developing which may result in incomplete project and increase in cost or even delay in completion of project. Hence it is very important to understand the requirements of the customer and make a proper software requirement document and then start the project development. Consequences: The result of vague requirements is severe. This will cause an increase in cost, inefficient product and a lot of rework. The developers will have to spend a lot of time and put in extra hours of work to make the necessary changes as the product developed is not as expected. Suggestion: To avoid this situation of vague requirements which may lead to project failure, I suggest that the project manager should meet the customer to get the exact requirements of the project. The Manager should make sure that all the requirements are properly documented so that the developers know the exact requirements which will help them to know what the goals to achieve are. The Manager should also regularly meet the developers and make sure that all the requirements are clear as they come and everyone has understood the requirements document. The requirement analyses and developing a project development life cycle should be given enough time before the actual development starts. Unrealistic Time Scale: Poor schedule estimation is another reasons for project failure. Many project managers understand the need to deliver the projects fast due to which they set unrealistic schedule to make sure the project is produced quickly without knowing the amount of work that needs to be done. Due to which they make superficial design and start coding to make the product as quickly as possible thinking that sooner the coding starts, faster the product is finished. Many times the managers are also pressurized by the stakeholders regarding the project deadlines. The Project Managers many times dont even work together with the stakeholders in defining a realistic schedule and decide on a proper deadline for the completion of the project. But this is the most common mistake made by the project managers. As a result of this unrealistic time scale the final product is either faulty or does not meet the user requirements or delay in delivery of project resulting in increase of the product development co st. Consequences: The result of unrealistic time scale is increase in cost and time to deliver. Since the schedule is unrealistic the manager will make a working model and ask the programmers to start coding quickly, which will result in low quality of work by the coders as they are under great pressure and the final product delivered will not meet the expectations of the stakeholder. This will cause the project to fail and cause waste of resources and money put in the project. Suggestion: Since unrealistic time scale being a common mistake made by the project manager, it can lead to heavy losses. This mistake should be taken care of by making a proper project plan and setting realistic deadlines. This plan and deadlines should be decided based on the amount of work to be done and the size of the team working on the project so as to avoid unnecessary pressure on the team. This will give enough time to work on each and every module properly and fulfill all the requirements properly rather than just complete the project within the given time. More importantly the stakeholders should be provided all the required data and estimated time of completion. They should also be updated at regular intervals to make sure that the work in on the estimated time. Poor Communication: Poor Communication is the third reason for project failure. Due to poor communication between the managers and developers, the developers are not aware of the work to be done by them, which may result in delay. As this important information is not shared between team members, the progress of the project is also not known. Trying to avoid communication between team members to avoid conflicting views between them may result in project failure. Sometimes the programmers are not allowed to give their opinion about the improvement of the project which is also a reason for project failure. This kind of poor communication between the manager and the team members hinders the progress of the project. This kind of poor communication should be avoided and the manager should take the necessary steps to overcome this problem for the success of the project. Consequences: The impact of this reason for project failure is very severe. It will affect the cost of development, affect the schedule and functionality. If the communication is poor it may lead to inefficient product development. Suggestion: Communication is very important between the team members, the management and the stakeholders for the project success. Since poor communication can lead to severe losses to a project I would suggest that manager should regularly communicate with the team regarding the project progress. This will help the manager to keep a track on the ongoing progress and also make sure that the team has understood all the requirements properly and avoid conflicting views between the members. And all the members will know their role in the project thus avoiding unnecessary work. Communication with the stakeholder will also help the stakeholder to know about the progress of the project and to know if the project is going as per the requirements. Scope Creep: Scope Creep gives the overall view of the final system to be delivered. Scope creep happens due to increase in the scope of the project during development. Often it is seen that the manager or the customer wants to add more functionality to the system while it is being developed. Like if a student record system is developed for the subjects taken and scores of the students by semester. But then the customer wants to add personal details and fees structure for each course. This will increase the scope of the system as the new functionality is required to be added along with the old requirements. This will affect the schedule of the project. Many times it happens that the customer might change the requirement at regular intervals or might require change as they are not comfortable with the existing system resulting in scope creep. Consequence: The consequence of this is very severe. As the requirements of the system change it will increase the cost of development and even affect the project schedule. Suggestion: Scope creep should be avoided as it may lead to major project failure or unnecessary delay in the project deliverable. This can be avoided by getting all the requirements from the user at the start of the project and even the priority in which the requirements need to be fulfilled. The cost and the time of delivery should be documented as per the present requirements. So any change will affect the cost and time should be told to the customer and everything should be documented. Inappropriate Staffing: Inappropriate staffing is another reason for project failure. The manager needs to find the right people for the job. Many times there are programmers who lack the required experience in the technology and are not qualified enough for that job. It also happens that the managers hired or allocated to a project dont have enough experience in handling such a huge task or dont have enough technical knowledge. These programmers and managers are hired simply to keep the cost of development low. So it is very important to get the right set of people to work on the project, who are experienced enough and can work well in a team for project to be successful. Many times it may happen that a member of the team or a high level manager might leave the job, which may affect the project schedule. Many times it happens that resources are not allocated properly while shows inefficiency in work, thus delaying the project schedule. This problem has been a major problem with all the companies. Consequences: This will have an impact on the project schedule as every time new resources are allocated, it will consume time to understand and complete task. Suggestion: To overcome the problem of inappropriate staffing the management must hire the right set of people for the required task who are efficient enough for the job. They must have a well balanced team and people who work well as a team and appreciate each other to achieve the bigger goal of successful project completion. Lack of User Involvement: User involvement is very important for any project to succeed. If the user is not involved in the project development by continuously communicating with the project manager, it may result in a project failure. Many times it happens that the user doesnt know how to use the system as the user is not much involved in the working of the system. The developers get the requirements from the user but the users are not actively participating in the design phase, requirement analysis phase, testing phase or the users are changing the requirements which may lead to delay in the project schedule and might not meet all the user requirements. Many times it is seen that the user will specify the requirements and then wait for the final product. Due to this the users sometimes dont get the expected functionality or they might not be familiar with the system which may result in a lot of time wasted in learning the system. Consequence: The consequence of this is medium effect. There can be a lot of change in the functionality as the user is not aware of the system working till the end. It may also increase the cost of the project and schedule as the user will take a lot of time to get familiar with the system. Suggestion: To overcome this problem of lack of user involvement, the user should actively participate in all the phases of project development. The user should be eager to learn the system before it is put live and hence should be trained to use the system. This will help the user to get familiar with the system and will also be able to test the system for all the features that are expected of the system. Poor Planning: Planning is the most important part of any project. If the project is well planned it will be completed on time and within schedule, resulting in success with all the requirements full filled. Project plan defines the objectives of the project and the goals to be achieved. The project plan contains the amount of resources required, the cost of development and the deliverable schedule. It helps in knowing what is to be done and what resources are required in which area of the project. Sometimes it is seen that the manager doesnt have much time to make a project plan due to time constrain from the senior management due to which implementation starts before the project plan is completed. This will hinder the project schedule as the flow of project development will not be clear. Many times it happens that project activities are dependent upon the previous activities completion but in case of poor planning this will get affected. This will result in the increase in the project development cost and increase the deliverable schedule. Consequences: The effect of poor planning is very severe. It will have an impact on the project development cost, incomplete requirements and will also affect the schedule. Suggestion: To avoid the problem of poor planning, the management should make sure that the project is well planned with all the resources, phases of development, cost estimation and the schedule of delivery before the implementation starts. Then at regular intervals it should be check if everything is going as planned, so that any kind of problem can be taken care of right away before its too late. Poor Testing: Poor testing plays an important role in project being a failure. Developers do test the project after the coding is done but it is the duty of the user to do an acceptance test to know if the system meets the requirements. But sometimes this testing fails as the requirements are poor enough to be tested. The user is unaware of the importance of this testing. It also happens that the user is not trained enough to test the system resulting in a poor test. Many times it is seen that the development phase takes so long that there is no time for testing, due to which it is avoided. So the user should be encouraged to do the acceptance testing so that the user is comfortable with the developed system. Consequences: The result of poor testing is that not very heavy. If the testing fails, then the development team will have to do a lot of rework on the failed areas. This will increase the cost and delay in project deliverable time. Suggestion: To make sure that testing is done properly the project should be well designed and planned. If the project is to be delivered in modules, then every module should be tested which is very useful as all the functionality is checked at the end of each module. This help in avoiding the entire system test at the end of the project, since most of the modules are tested as they were completed. Then the user should be trained to use the system so that they can do a proper test of the system. This can help in overcoming the problem of poor testing. View Point: The analyses shown above are based on my research about various reasons for project failure and their consequences. From my research on the above I analyzed and suggested that all of the above reasons are important and should be taken in to consideration during the life of project development as they have equal effect on success of a project or its failure. I think that most projects fail due to vague requirements, poor planning and inappropriate staffing. Making sure that all the requirements are properly gathered is the first step in any project development process. If the requirements are not properly gathered then it may lead to problems down the line during development. I have observed that many times due to time constraint or not clear requirements the development phase is started considering that once a working model is ready then all the left out requirements can be handled but this is the biggest mistake made as it will require a lot of rework and increase the cost of development. Many times vague requirements force the developers to make a functionality that is actually not required thus wasting of time and resources results in a lot of rework. Poor planning is also a factor for project failures. Due to vague requirements the planning done is also poor resulting in project failure. Planning phase comes after requirements gathering phase. In this phase all the details about the project development, the resources required, the cost of development, the time schedule of deliverable project parts or whole are decided. This phase takes a good amount of time as the whole project development is planned in this phase, so if the planning is poor, it may lead the project down the hill instead of up. So during the planning phase all the aspects of development should be taken into consideration by the developers and managers. Another problem which is faced by most of the companies is of inappropriate staffing. A project team should have the right combination of people. People, who are experienced, can work well in a team. Generally managers try to cut the cost of development by hiring people who are less experienced with the kind of project to be developed and even inexperience in using the technology being used. This will affect the project schedule. Many times it happens that a manager or team member leaves the project due to work pressure as they are kept to do parts in many projects. Due to this the project is delayed and a lot of time is lost in training the new member. So managers should chose the right people for the team and also the members should be dedicated to a particular project. Many times I have seen that there are dependencies between teams during a project development. Like now a days there is outsourcing where in the design and testing is done by one team and the coding is sent to another team. So whenever there is a change in the functionality or the design the coding team seating elsewhere are given the changes resulting in a lot of rework which relatively affects the project schedule. Many times there is miscommunication between the teams working in different modules so changes in one module is not conveyed to the other resulting in errors during the testing phase. So there should be proper communication between teams and regular updates should be given to all the teams working on the project to avoid any error at later stage of the project. And other than these all the other factors should be taken into consideration by the management for a successful project. Lessons Learnt: From my research on project failures I learnt that project management is the most important aspect for any projects success. From research on this topic I learnt that over the years this problem has haunted the software industry but still the management has not learnt from the previous mistakes. All the reasons shown above are very critical and can lead to project failure if not handled with care. Manager must also focus on the team development for any project as it the overall team effort that makes the project successful and not an individual. Conclusion: The research gives an insight into various reasons of software project failure. These reasons have been experienced by every manager in the industry and so now companies have started focusing on proper management of the projects. References: http://www.coleyconsulting.co.uk/failure.htm http://ezinearticles.com/?Causes-Of-Software-Project-Failureid=453814 http://www.ibm.com/developerworks/rational/library/feb06/marasco/ http://www.docstoc.com/docs/24462435/Why-Projects-Fail-Graph http://www.projectsmart.co.uk/why-software-projects-fail.html http://www.projectperfect.com.au/info_it_projects_fail.php http://ezinearticles.com/?Causes-Of-Software-Project-Failureid=453814 http://74.125.155.132/search?q=cache:rpsupt-SPl0J:www.tier1performance.com/content/features/mets_files/MajorCausesofSoftwareProjectFailures.pdf+reasons+for+software+project+failurecd=3hl=enct=clnkgl=us http://www.computerworld.com/s/article/71209/Why_Projects_Fail http://knapton.blogspot.com/2007/05/why-do-software-projects-fail.html http://www.adaptivepartners.com/projfailb.htm http://portal.acm.org.libaccess.sjlibrary.org/citation.cfm?id=1370099.1370100coll=portaldl=ACMCFID=12421101CFTOKEN=86551462

lord of the rings :: essays research papers

The Fellowship of the Rings   Ã‚  Ã‚  Ã‚  Ã‚  I read The Fellowship of the Rings for my book report. It is the first book to the Lord of the Rings, written by J.R.R. Tolkien. The settings in this book changed many times from the hills of the Shire where the hobbits live, to the deep darkness of the mines of Moria. The book takes place in a place called Middle Earth, which is described by Tolkien as a mysterious place full of good and evil. The way Tolkien described each place is amazing and it is as if u were looking at a picture and copping it down into your head. The Shire, a peaceful place, full of little people, known as hobbits. The hobbits are friendly folk who don’t pay attention to the outside world. They live in little holes dug in the sides of hills. The hobbits have large gardens of, pipe weed, corn, and their favorite, potatoes. The hobbits are used to their everyday life, and are very content with the lack of adventure. Most do not travel farther then Bree. Bree is a small town mixed with big and little people, (men and hobbits) who live together through the hard time that trouble the old town. The Forest of Lothorien is where the elves live in peace, hidden for the evil not far off. The forest is very magical and full of beautiful trees. The trees were described to have silver bark and rich golden leaves. These were the homes of the elves that had built platforms in the center of the trees, like tree houses. In Lothorien the weather is always as if it were a warm spring day even in the dead of winter. Lothorien is unaffected by time, as if the days just repeat them selves but the people go on with their lives. The lady of the land, Galadriel, has another magical ring that the dark lord is seeking. The magic ring kept the forest protected and healthy along with everyone that lived there. Darkness, silence, emptiness describes the Mines of Moria. The mines cut through the Misty Mountains, and connect the fields of Rohan to the forest of Lothorien. The mines were abandon by the dwarfs in a war with the orcs, who worked for a wizard who wanted the same ring that the dark lord wanted. The are many passages that were crafted bye the dwarves to mines and lookouts but only one way out.