William Shakespeare s Romeo And Juliet - 1341 Words

As Shakespeare composes this tragic love story â€Å"Violent delights have violent ends / And in their triumph die, like fire and power, / Which as they kiss consume† (2.6.9). In the play Romeo and Juliet an enchanted love leads to violent ends and consumes two people’s lives until their powerful death. When Romeo first lays eyes on the gorgeous Juliet it is love at first sight. Though their love is authentic and empowering, it is also entirely banned. William Shakespeare writes this masterpiece with much delight but also great sorrow. Romeo and Juliet is the most abiding love story of all time. Shakespeare uses many literary devices in his works. Throughout this story the character Juliet changes remarkably. Shakespeare provides evidence for†¦show more content†¦Come, what says Romeo?†(2.5). Juliet is completely obsessed with her love, so obsessed that her love overpowers her, in a dangerous and controlling way. This of course does happen near the end o f the play she takes a dangerous potion tricking her family into thinking that she is dead. This ables Juliet into hopefully running away to her love who has been banished from Verona. Though scarred she drinks the potion in hope of living happily ever after with Romeo: â€Å"Come, vial. What if this mixture do not work at all?... What if it be a poison which the friar / Subtilly hath minist’red to have me dead†¦ I fear it is†¦ There’s a fearful point! Shall I not then be stifled in the vault†¦ and there die strangled†(4.2) yet she still drinks the potion for love: â€Å"Romeo, I come! This do I drink to thee.†(4.2). Her love consumes her especially after Romeo’s death: â€Å" Yea, noise? Then I’ll be brief. O happy dagger! (Snatches Romeo’s dagger.) This is thy sheath; there rest, and let me die (she stabs herself and falls on Romeo’s body.)†(5.3). Just like that she ends her life because of her obsession over Romeo and their love. This is a huge change of her character, she goes from being just a child who â€Å"hath not seen the change of fourteen years†(1.2) to a woman who ends her life for love. This shows how much Juliet’s perspective on love and life has changed through foreshadowing. There are a lot of periphrasis in Shakespeare s play some which reveal a

My First Day Of School - 1577 Words

It’s the first day of school for me and my first class of 1st graders. In walks a little girl, she is wearing a beautiful blue head scarf. Her name is Berra. While talking to her parents before her first day of school, I know she is from Istanbul, Turkey. She moved to the United States when her father received a job as an architect. It was important for me to know this will be her first year in school. Children in Turkey begin to receive a free education when they 6 years old. This differs from the U.S. because children can begin school at age 5. The Turkish tradition and culture is one with great influence from the surrounding countries. It is located in Western Asia between Europe. Istanbul is located between the Black Sea and the Sea of Marmara. Istanbul is the largest city in Turkey with a square footage of 2,063 miles. The city holds the country’s economic, cultural and historical heart. Not every woman or girl wears a head scarf but it is up to them and their religion whether they choose to wear it or not. It is important for me to know the most I can about my students culture and her way of life so I can help set straight any common misconception my young students may have. I also want to give every one of my students the best education possible. I can only teach my children if I know who they are. I need to know what is important to each of my students and what interests them. This means doing my research on where my student is from and discoveringShow MoreRelatedMy First Day At School837 Words   |  4 Pageshard push on my side. Slowly I opened my eyes. I just see the sun’s rays creep through my windows and flash me right in my eyes. Slowly I got used to the light. I finally got up and could open my eyes fully. I hear my mom yell get up it’s your first day of school. I Got up took a shower, got dressed, ate my breakfast, and I was out the door on my way to school. I live in Ohio where it usually rains a lot and today it was a very sunny beautiful day. I got to school. It was my first day of middle schoolRead MoreMy First Day Of School838 Words   |  4 PagesIt was sunny Monday morning, soon to be my first day of school. I remember having a mild anxiety. I found myself swept away by fear as I approach the main entrance. The thought of leaving my home to acquire education seemed like nonsense for my 4 years old self. Since it was my first day of school my parents had to stay with me to make me comfortable. Being nervous, I passed through the main entrance. I saw a couple of kids playing with their small trucks in the playground and others were runningRead MoreMy First Day Of School Essay1024 Words   |  5 PagesIn elementary school, I had two best-loved teachers. My kindergarten teacher, Dr. Barron had the kindest heart. My first day of school, I scarcely remember her greeting each student with a friendly smile. That first day we learned her class song. â€Å"Dr. Barron’s bunnies come to school every day, school every d ay, school every day†. Throughout the remaining years in elementary school, I would visit her class for a friendly conversation. My second favorite teacher in elementary school was Mrs. JacobsonRead MoreMy First Day Of School Essay966 Words   |  4 PagesThe first day of school is nerve-wracking for most people, for me, the first day was especially terrifying. The first day of a college class is probably more crazy than all others. My mom and younger sister, Michaela, were busy taking pictures as I attempted to run out of the door. After being homeschooled for the last six years, I knew it would be a much different experience. I had been in my room alone doing school; I was content with where I was. The morning of the first day of class, I was soRead MoreMy First Day Of School1607 Words   |  7 PagesWhen I woke up this morning, I was very nervous my first day of school, usually, I get taught at home so I don’t understand much, going to this public school is going t o put a new perspective in my life. When I open my little wooden door with my tinny bunnys hands, I walked to the bus in the background, I heard my mom and dad and little sister saying, â€Å"good luck on your first day.† I just gave a little wave back and blew a kiss. When I looked around I felt alone, the birds chirping with suchRead MoreMy First Day Of School1682 Words   |  7 Pagesyour day off with a two mile walk in the heat. Finally, you get to the small, one room schoolhouse, and it has no air conditioning. Everyone around you is so much taller than you, meaning they are probably a lot older than you as well. The teacher looks at you and tells you to take a seat, but all you want to do is turn around and be anywhere else but there. Seems a little scary, right? Well this is how my grandma’s first day of school went. This is nothing like a typical first day of school for kidsRead MoreMy First Day Of School Essay1544 Words   |  7 PagesWe met during our second last year of high school. Back then, I had transferred to Richmond High from my old school, Churchill, to study in the IB program they offered. I was quite looking forward to it, actually. I felt that the past years of my life had been wasted on social life and boys who just disappointed me at the end. Moving to a new school was a way to break free, to start anew and focus on something different for a change. Studies. That’s right, I was going to focus on studies. PlusRead MoreMy First Day At School774 Words   |  4 Pages My time at Life School was very eventful, and I will remember them for the rest of my life. My first day at life school was very eventful though i made a name for myself. I started at Life School Lancaster in the third grade, and i came about a month after school started because i transferred from a different school. I got into trouble and they gave me a tally which is just something to show you did something they didnt like. At first i thought i was getting kicked out, but through time i learnedRead MoreMy First Day At School733 Words   |  3 Pagesbecause it was my first day of school. First I went to take a shower; I thought, â€Å"What I would do in school today, who will be my teachers. Then I walked to the bus stop people looked at me like Im not from this planet. I sat on a tree trunk waiting for the bus. The bus arrived after 15 minutes, I aboard the bus. The driver was a woman she was wearing a black shirt and brown pants. She told me â€Å" Do you have the paper that sh ows that you have permission to go to school in a school bus† I stared atRead MoreMy First Day Of School1280 Words   |  6 PagesHigh school first day drama My first day of highschool changed my identity through new environments new teachers new friends and new standards. On the first day of school I woke up to my blaring alarm â€Å"beep beep beep beep†. After I hit the snooze button it was 6:00 and realized the summer was over and new school had started. I had not worried much about this day but today was different. I had the stomach bug I felt as though I was going to throw up. The sun was just waking up throwing vibrant colors

Approach to Software Architecture Description Using UML Free Essays

string(186) " then a section describing the stakeholders, then a section describing the elements and relations that can be used to describe views in this viewpoint, and finally an example of a view\." The 3+1 Approach to Software Architecture Description Using ML Revision 2. 2 Henries B ¦Arab Christensen, Anion Sorry, and Klaus Marcus Hansen Department of Computer Science, University of Argus Beograd 34, 8200 rush N, Denmark May 2011 Abstract This document presents a practical way of describing software architectures using the Unified Modeling Language. The approach is based on a â€Å"3+1† structure in which three viewpoints on the described system are used – module, component connector, and allocation – are used to describe a solution for a set of architectural requirements. We will write a custom essay sample on Approach to Software Architecture Description Using UML or any similar topic only for you Order Now Introduction Software architecture represents an appropriate level of abstraction for many system development activities [Bass et al. , 2003]. Consequently and correspondingly, appropriate software architectural descriptions may support, e. G. , stakeholder communication, iterative and incremental architectural design, or evaluation of architectures [Bass et al. , 2003], [Clement et al. , Bibb], [Clement et al. , AAA]. This document represents a practical basis for architectural description and in doing so, we follow the IEEE recommended practice for architectural description of software-intensive systems [Software Engineering Standards Committee, 2000]. Central to this recommended practice is the concept of a viewpoint through which the software architecture of a system is described (see Figure 1). A concrete architectural description consists of a set of views corresponding to a chosen set of viewpoints. This document recommends the use of three viewpoints (in accordance with the recommendations of [Clement et al. AAA]): A Module viewpoint concerned with how functionality of the system maps to static development units, a Component Connector viewpoint concerned with the runtime mapping of nationality to components of the architecture, and an Allocation viewpoint concerned with how software entities are mapped to environmental entities In addition to the views on the architecture, we recommend col lecting architecturally significant requirements (see Section 2) in the architecture documentation. This corresponds to the mission of a system as described in [Software Engineering Standards Committee, 2000]. The views corresponding to these viewpoints are described using the Unified Modeling Language standard (ML; [OMG, 2003]). This reports provides examples of doing so. The ML has certain shortcomings in describing software architectures effectively , but is used here to strike a balance between precision/expressiveness and understandability of architectural descriptions. Figure 1 : Ontology of architectural descriptions 1. Structure The rest of this document is structured in two main sections: One introducing the â€Å"Architectural Requirements† section of the documentation (Section 2, page 3), and one introducing the â€Å"Architectural Description† section of the documentation (Section 2, page 3). These sections are introduced in general and a specific example of applying them to the documentation of a system is provided. The examples are created to describe a point-of-sale system (Next POS) for, e. G. , a supermarket point-of-sales. The example is inspired by the case study of Alarms [Alarms, 2002]. The system supports the recording of sales and handling of payments for a generic store; it includes hardware components as a bar code scanner, a display, a register, a terminal in the inventory hall, etc. More details of the functionality of the system can be found in Section 2. 1 This is in particular connected to the central Component Connector viewpoint [Clement et al. , AAA] 2 Architectural Requirements Two types of descriptions of architecturally significant requirements are appropriate: scenario-based and quality attribute-based requirements. The architecturally significant scenarios (or use cases) contain a subset of the overall scenarios providing the functional requirements for the system. These can possibly be augmented with requirements on performance, availability, reliability etc. Related to the scenarios. Moreover, â€Å"non-functional† scenarios, e. G. , describing modifiability of the system may be useful as a supplements . All requirements cannot be described as scenarios of system functionality, and we propose supplementing the scenarios with a set of the most critical quality attributes that the system should fulfill. Since quality attributes (such as modifiability and performance) are often in conflict, this needs to be a subset of all architectural quality attributes. The goal of describing architectural requirements is to enable the construction of a set of â€Å"test cases† against which deterrent architectural designs may be compared and/or evaluated. 2. 1 Example In the Next POS case, a scenario is a specific path through a use case. An example of such a scenario is: Process Sale: A customer arrives at a checkout with items to purchase. The cashier uses the POS system to record each purchased item. The system presents a running total and line-item details. The customer enters payment information, which the system validates and records. The system updates inventory. The customer receives a receipt from the system and then leaves with the items. Critical architectural attributes for the Next POS system area : Availability. The system shall be highly available since the costiveness of sales depends on its availability Ђ Portability. The system shall be portable too range of deterrent platforms to support a product line of POS systems Usability. The system shall be usable by clerks with a minimum of training and with a high degree of e science 3 Architectural Description It is beneficial, when documenting software architecture, to apply deterrent viewpoints to the system. Otherwise the description of the system will be incomprehensible. 2 Architecturally significant scenarios are the basis of many architectural evaluation approaches [Clement et al. , Bibb] 3 Note that this choice of quality attributes excludes, e. G. Performance, scalability, security, safety, reliability, intolerability, and testability. Taken this into account, it is first important with a viewpoint which describes the functionality of the system in terms of how functionality is mapped into implementation. Secondly, it is important to describe how the functionality of the system maps to components and interaction among components. And thirdly, it is important to see how software components map onto the environment, in particular hardware structures. These three viewpoints are the module, component connector, and allocation viewpoints respectively in concordance with [Clement et l. AAA]. The viewpoints used in the architectural description section are defined as proposed in [Software Engineering Standards Committee, 2000]: for each, we first have a section describing the concerns of this viewpoint, then a section describing the stakeholders, then a section describing the elements and relations that can be used to describe views in this viewpoint, and finally an example of a view. You read "Approach to Software Archi tecture Description Using UML" in category "Papers" 3. 1 3. 1. 1 Module Viewpoint Concerns This architectural viewpoint is concerned with how the functionality is mapped to the units of implementation. It visualizes the static view of the systems architecture by wowing the elements that comprise the system and their relationships. 3. 1. 2 Stakeholder Roles This viewpoint is important to architects and developers working on or with the system. 3. 1 . 3 Elements and Relations The elements are units of implementation including: Class: A class describing the properties of the objects that exist at runtime. Package: A logical division of classes in the system. This can refer to packages as we find them in Java or Just give a logical division between the classes of the system. Interface: A classification of the interface of the element that realizes it. It can refer to the interfaces found in e. G. Java or Just a description of an interface that a class can conform to. The relations describe constraints on the runtime relationships between elements: Association: Shows that there is a hard or weak aggregation relationship between the elements and can be used between classes. Generalization: Shows that there is a generalization relation between the elements and can be used between two classes or two interfaces. Realization: Shows that one element realizes the other and can be used from a class to the interface it implements. Dependency: Shows that there is a dependency between the elements and can be used between all the elements. 3. 1 . 4 Examples The module view of the POS system can be described using the class diagrams of JIMS, which can contain all the above mentioned elements and relations. It is possible to describe the system top-down by starting wit h the most top-level diagram. In figure 2 the overall packages of the system are shown. Figure 3 and figure 4 show further decomposition of the Domain Model package and the Payments package in the Domain Model package. Figure 2: Package overview diagram for the POS system Dependencies among packages are also shown; these dependencies arise because of relationship among classes in deterrent packages. As an example, consider the association between figure 4 there is an association from classes in Payments to the Customer class of the Sales package. This relationship gives rise to a dependency from the Payments to Sales package as shown in figure 3. Figure 3: Decomposition of the Domain Model package of the POS system Typically, class diagrams such as figure 4 will suppress detail and also omit elements for clarity, since a major purpose of architectural description is come annunciation. In figure 4, e. G. , details of methods and attributes of classes have been suppressed and certain classes have been omitted. Figure 4: Decomposition of the Payments package of the POS system 3. 2 3. 2. 1 Component and Connectors (CC) Viewpoint This viewpoint is concerned with the run-time functionality of the system?I. . What does the system do? This functionality lies as the heart of purpose of the system under development, thus this viewpoint is of course a very central viewpoint, and architectural design often starts from tit . In this viewpoint, software systems are received as consisting of components which are blackball units of functionality and connectors which are first-class representations of communication paths between components. C omponents embody functional behavior while control and communication aspects are defined by the connectors. Paraphrasing this, you can say that components define what parts of the system is responsible for doing while connectors define how components exchange control and data. It is important to describe properties of both components and connectors in the documentation. This is done using a combination of textual descriptions (listing susceptibilities for example) with diagrams showing protocols, state transitions, threading and concurrency issues as seems relevant to the architecture at hand. 4 Hoverflies et al. Hoverflies et al. , 1999] defines a process where this viewpoint is the first to be considered and other viewpoints are derived and elaborated from it. 6 Figure 5: CC overview of the POS system 3. 2. 2 This viewpoint is important to architects, developers, and may also serve to give an impression of the overall system runtime behavior to customers and end users. 3. 2. 3 The CC viewpoint has one element type and one relation type: Component: A national unit that has a well-defined behavioral responsibility. Connector: A communication relation between components that defines how control and data is exchanged. Both are first class citizens of this viewpoint and both may contain behavior. This is obvious for components, but connectors may exhibit behavior as well. Examples of connectors with behavior are those that provide buffering of data between a data producer and consumer, data convention, adoption of protocols, remote procedure calls, networking, etc. A connector defines one or more protocols. A protocol defines both incoming and outgoing operations and mandates the ordering of them. Thus a connector’s protocol is radically deterrent from a class’ interface that only tells what operations its instances provide (not uses) and does not describe any sequencing of method calls. 3. 2. 4 The POS system has four major functional parts as shown in the CC view in figure 5. Components are represented by ML active objects, connectors by links with association names and possibly role names. Active objects are typically processes or threads in the operating system or programming language, and links the communication paths between them. The diagram cannot stand alone, as component names and connector names are only indicative of the functional responsibilities associated with each. We 7 therefore provide an description of component functionality in terms of responsibilities: Barded Scanner. Responsible for 1) Control and communication with bar code scanner hardware and 2) notification providing ID of scanned bar code for items passing the scanner. Sales. Responsible for 1) keeping track of items scanned; their price and quantity; running total of scanned items and 2) initiation and end of sales handling. Ђ Presentation. Responsible for 1) displaying item names, quantity, subtotals and grand total on a terminal 2) printing item, quantity, subtotals and grand total on paper receipt 3) handle key board input for defining quantities when only one of a set of items are scanned. Inventory. Responsible for 1) keeping track of items in store 2) mapping between bar code ID’s and item name and unit price. Likewise, the connectors’ protocols needs to be described in more detail. The level of detail needed depends on the architecture at hand. For some connectors, it may be us cent with a short textual description (for instance if it is a straightforward application of the observer pattern; or if it is a direct memory read); others may best be explained by ML interaction diagrams; and still others may have a very large set of potential interactions (like a SQL connector) of which only a few may be worthwhile to describe in more detail. The POS example names three connectors: MFC. A standard MFC patterns is the protocol for this connector that connects the Sales component serving the role of model and Presentation serving as controller and view. Ђ JDBC. This connector handles standard SQL queries over the JDBC protocol. BPCS. This connector defines a protocol for connecting with a barded scanner. Data and control is exchanged using ASCII strings in a coded format containing control words and data elements. Sequence diagrams can be used to describe connector protocols. Depending on the system, it may be relevant to docum ent connector protocols individually (a sequence diagram for each protocol) and/or to provide the â€Å"big picture† showing interaction over a set of connectors. Typical use cases as well as critical failure scenarios may be considered for description. In our point of sales example, an overall sequence diagram (diagram 6 seems most elevate, as the individual connectors have rather simple protocols. The scenario shown in the diagram is the event of a single item being scanned and registered. Further detail can be provided, like a sequence diagram showing observer registration and steady state operation for the MFC connector; perhaps table layout or SQL statements for the JDBC; or command language for the BPCS connector. However, most likely this information does not provide architectural insight (they do not eject architectural qualities) and their details should be found in more detailed documentation instead. 8 Figure 6: POS â€Å"item scanned† scenario 3. 3 3. 3. 1 Allocation Viewpoint This architectural viewpoint is concerned with how the software elements of the system – in particular the CC viewpoint elements and relations – are mapped to platform elements in the environment of the system. We are interested in what the software elements require (e. G. , processing power, memory availability, network bandwidth) and what the hardware elements provide. 3. 3. 2 This viewpoint is important to a number of stakeholders: Maintainers needing to deploy and maintain the system, to users/customers who need to know how nationality is mapped to hardware, to developers who need to implement the system, and to architects. 3. 3. 3 The deployment viewpoint has two primary element types: Software elements: These may be, e. . , executables or link libraries containing components from the CC views. Environmental elements: Nodes of computing hardware Furthermore, there are three main relation types: Allocated-to relations: Shows to which environmental elements software elements are allocated at runtime. These relations may be either static or dynamic (e. G. , if components move between environmental elements). Dependencies among software elements Protocol links among environmental elements showing a communication protocol used between nodes. 3. 3. 4 Figure 7 shows the deployment of the Next POS system using a ML deployment diagram. The deployment is a typical 3-tier deployment in which presentation is run on a client, domain code is run on a JEEZ application server, and data is stored on a database server. Figure 7: Deployment view of the Next POS system The following elements are of interest Environmental elements (shown as ML nodes) – The Barded Scanner is the device used for inputting sold items into the system. It s read via an ROARS connection to the POS Terminals – The Terminal is the main point of interaction for the users of the Next POS system – The Application Server is a machine dedicated for serving all Terminals on an application level – A Database Server provides secondary storage Software elements (Shown as ML components) – The POS executable component runs the client part of the Next POS system including presentation and handling of external devices (biz. The Barded Scanner). It communicates with the Application Server via RMI over IIOP – Jobs is an open source application server which is used for running the domain- elated functionality of the system. It uses the Database Server via JDBC 10 – Myself is an open source SQL database which handles defenestrated functionality (storage, transactions, concurrency control) of the system. 3. 4 Overview The three viewpoints and their associated elements and relations are summarized below. Module c Deployment Elements Class Component Executable Interface Computing node Package Relations Association Connector Allocated-to Generalization Dependency Realization Protocol link +1 view: Architectural requirements The mapping to ML is straight forward for the module and deployment viewpoint UT less so for the C viewpoint. For the C viewpoint, components are show by ML Active Objects (that represent run-time entities with their own thread of execution, typically threads and processes), while connectors are shown by ML links (that represent control- and data flow using some protocol). 2 How to cite Approach to Software Architecture Description Using UML, Papers

Construction Projects Selection and Risk †Free Samples to Students

Question: Discuss about the Construction Projects Selection and Risk. Answer: Introduction Risk management is essential for the project of construction because the main aim behind making waste management is to prevent of losses caused by exposure to risk. Risk management in the project of construction is designed to plan, control and monitor those requirements which are needed to protect exposure to risk. It is a research proposal which will describe the role of risk management in the project of construction. In order to understand the research, various sources will be used to analyze the topic. Literature review will reflect the entire structure of risk management to prevent exposure to risk. The importance of risk assessment will be described. The main objective of this research is to search out the importance of the risk assessment in the project of construction. Risk assessment is required to prevent the risk exposure. Secondary sources are being taken together the relevant information regarding the research title. The research program will reflect the importance of risk assessment in the project construction. Risk identification and risk analysis will be discussed under the program of research. The major scope of research proposal is to make better understanding about the kind of risk in construction. The projects of Constructions are exposed to risk at the time of their coming into existence. It is important for the risk management to measure and cost of the measure must be recognized and comfortable measures must be searched in order to avoid errors in the potential. There are various kind of construction project with the course of planning, development and realization. The importance of risk management in construction projects is vital. In the phase of planning possible risk for the successive achievement of the project can be raised and decreased by their integration into the planning. There is potential analysis of a construction project refers to what extent project risk affect the circumstances of risk of the business (Zhao, Hwang and Low, 2013). It is required for the risk potential to be predictable without depth knowledge of the individual raised at as little expense as possible. Risk management includes the integration of common Principles of risk policy and the organiz ational integration. With the help of risk management, transparency enhances, various issues can be avoided from the outside by applying the proactive action, and the construction project might be made for unavoidable issues (McNeil, Frey and Embrechts, 2015). The processes of risk management include many steps, which will be described in this literature review. The certain steps of risk process are identifying risk, risk analysis, assessing risk, controlling risk, monitoring risk and managing the goals. It is important for the risk management that risk to be identified because the risks that are not recognized also cannot be assessed. The risk identification can be distinguished into quality risk, personal risk, cost risk, deadline risk, strategic decision risk and external risk. It is important for the organization to analyze the type of risk in the construction project (Marcelino-Sdaba, Prez-Ezcurdia, Lazcano and Villanueva, 2014). The main objective of analyzing risk is to define the situation of Risk in the form of completely and precisely. The recognized risks are investigated with the term probability of the occurrence and the effect on the project the evaluation of Risk is brought by the project manager in the term of controlling the project. It is important for the risk team analysis to determine and evaluate as per the kind and poi nts for risk are worked out. The third step of risk management is assessing the risk. The risk assessment includes the qualitative assessment as well as quantitative measurement of the risk of individual involving the interrelationship of their influences (Hwang, Zhao and to, 2014). The result of risk assessment would be helpful for the company to analyze the position of rest in the existing construction project. Risk assessment is considered as a constitutional requirement for the health and safety risk under the management of Health and safety at work regulation. In case of no objective data is present, risk should be quantifiable. With the help of qualitative estimation, risk can be assessed subjectively as per the probability of their occurrence and the amount of damage or loss. Controlling risk has the effective influencing of the risk decided in the context of risk analysis. The measurement of handling with risk maybe various between cause related and effect related measures. The measure of cost related should be avoided or decrease risk, in the context of effect related measures serve to decrease or safeguard against the damage. The effectiveness of risk control is maintained when the operative control over the risk management is done on continuous manner (Osipova and Eriksson, 2013). The aim of risk management is not to eliminate waste entirely from the construction project. Monitoring risk facilitates guarantee that the position of the risk of the construction project conveys to the situation of endeavored for. The integral part of the body is internal control system. The constant monitoring of the previous indicators And the repeated risk verification are brought by the person who is responsible for every case, no afterward than the respective mileston e deadlines. The response construction is wider at the earliest stages of the initiating project with the option of procurement route. There are several routes of procurement that construction project utilize each with different balance of risk either towards the customer or the contractor. For instance the design of client-led and create the weight of the risk on the customer and the stage of design where is contractor Finance creating the weight of Risk on the contractor by the phases of design and construction. There are majorly three kinds of risks in the project of construction that is client risk, contractor risk and health and safety risk (Manuj and Mentzer, 2008). Client risk is related to the quality and cost time. The consideration of the risk management for the customer may involve feasibility risk, design risk, funding risk and commercial risk. Feasibility risk involved the decision to move further backed up by a business case of robust. The preferred solution is presented after consi dering options. Design risk refers to a decision the level of control to put design and therefore the risk is described in the context of design. Funding risk is making ensure about the availability of the fund to pay the contractor. It reduces the risk of insolvency of contractor as well. The risk of commercial is on the profits and income if contractor is unable to deliver the project on time with quality (Taylan, Bafail, Abdulaal and Kabli, 2014). The biggest risk for contractor is the stage of tender when commitments in the context of price and time scale. Accuracy in the bill is must in the construction project. Due to lack of quantity in the bill and inaccuracy in the bill can be the reason of fewer margins (Rothengatter, 2017). The contractor should define the entire detail about what he want related to the construction project because subcontractors might not stand by their commitment and work might be more costly in comparison of estimated if a choice of the method of construction is not suitable for the existing construction project. It has been analyzed that on average 2 to 3 people die every week on construction site. Most of them are avoided by constructor (Desai and Kashiyani, 2015). To decrease the risk of die while performing the task of construction project, health and safety regulation support to them directly or indirectly. The health and safety risk is handled by the legislation regarding construction involvin g the design and management regulation 1994 and the construction regulation 1996. The importance of Health and safety plan in the construction project is vital and it is important to have the effective communication within the entire team throughout the project. The guidance are reflected by the approved code of practice (HSE 2001) that is concerned about the elements of the health and safety plan and describe the responsibility of those person who are responsible and have duties under the regulation. Apart from those risks, risk of Fire is higher in construction projects. Fire risk is always available on the site of construction. It is necessary to have the certain firefighting equipment in the place of construction project. Training program about preventing risk should be addressed to the existing labor (Froot, Scharfstein and Stein, 2013). The principal contractor must develop the plan of fire prevention on construction sites. Research questions and hypothesis Research questions have been created for this research topic which is defined below: What is risk management in the construction project? Why risk assessment is necessary to protect the exposure to risk? What are the steps or process of risk management to control the risk in the construction project? Risk management is able to prevent the revelation to risk and their process is helpful for risk management team. Lack of controlling over the risk can take the lives of many. It can influence the image of the construction project and organization as well in adverse manner. Research Design and Methodology There are various kinds of design and methodologies available which gives support to accumulate the data effectively. Different kinds of methods and techniques have been observed while executing of the research. The used methods and techniques are listed below: There might be various kinds of techniques and methods which could support to research to gather the information. Qualitative data has been considered to collect the data and information regarding this topic. It will be facilitates to assemble the information on the quality basis. Qualitative and quantitative both approaches have been measured to gather the information. The approach of qualitative helps to understand the aspects and opinion about the gathered data. The support of primary and secondary sources has been taken to gather thee quality research material and information regarding the topic. Data collection is done with aim to collect the information for the executing of research. The relevant information is being collected by suing the primary and secondary data sources. A combination of the resources would b advantageous for the research to make effective understanding about the topic of research. Primary sources are fresh because it is directly fetched by respondent and includes questionnaire and interviews (Musa, Abanda, Oti, Tah and Boton, 2016). The term of reliability is heavier of the secondary sources in the comparison of primary. Secondary sources are able to increase the authenticity and reliability of the material of research. Sampling size and techniques The gathered information is huge so it is the challenge to evaluate the entire data within time limit. It is the main reason and to cope up with this issue, random sampling technique has been chosen. It would be helpful to give opportunity to an individual of the population of being involved in the sample. The major feature of this technique is its delegation of the population (Neuman and Robson, 2014). The research program should be completed within time frame because it is vital for the relevancy. The research should be conducted appropriately and it is necessary for attaining the aim and objectives. A systematic approach has been opted for the execution of the research. It facilitates to accomplish the data and activity within a sequence manner (Sadgrove, 2016). The outcome of the research program will come in a sequence way which is applicable for the research. Target market defines the place where relevant information regarding research topic has to be gathered. The primary as well as secondary sources have been taken in use to gather the information related to the topic. A primary source contributes in the term of questionnaire which will be represented to the risk management and secondary data has been collected from the reliability journals and published material after 2009. Research program has been executed by keeping in mind about the ethical consideration. There are certain rules and regulations have been followed by researcher and permission is not there to reveal information regarding the research topic. Data protection act is there for those who will breach the rules and policies (Grace, Leverty, Phillips and Shimpi, 2015). Research limitations There are certain limit has found during researching the program, the limitations are described below: The time limit is not sufficient for this research and due to lack of time; random sampling technique has been chosen which will be helpful to determine the various aspects related to risk management in construction project. The range of resources is limited which is being in the issue of limitation to execute the research. The limitation of getting access over the data is also the reason of unfavourable collision on the execution of the research. Schedule of time Serial number Activities Starting date Duration Attainment date Description 1 Decision about research topic 1 October, 2017 2 2 October, 2017 Selection of the topic will be done. 2 Making plan for the research 3 October, 2017 3 5 October, 2017 Plans will be made. 3 Implementation of the plan 6 October, 2017 4 9 October, 2017 Plans will be implemented. 4 Data collection 10 October, 2017 4 13 October, 2017 The methods will be selected. 5 Analyzing collected data 14 October, 2017 5 18 October, 2017 Data regarding topic will be analyzed. 6 Interpretation of the outcomes 19 October, 2017 3 21 October, 2017 Results will be drawn from the analyzed information. 7 Drawing conclusion ad recommendations 22 October, 2017 2 23 October, 2017 The conclusion and recommendation will be made. Conclusion Thus, it can be summarized by from the above discussion that risk management is necessary for the construction project. It is vital for the risk management to assess the risk. The process of risk management has been discussed in this report. The management of risk has been installed progressively in the project provides the opportunity to attain the clear understanding of the aim and objective of the services and viability of the project. It has been recommended that the process of risk should be done in the proper manner. Construction project is risky and the risk management team should be active and follow all rules regarding health and safety. Training program should be conducted in the construction project so that labor can get security and know about how to protect. References Aminbakhsh, S., Gunduz, M. and Sonmez, R., 2013, Safety risk assessment using analytic hierarchy process (AHP) during planning and budgeting of construction projects,Journal of safety research,46, pp.99-105. Desai, A. and Kashiyani, B., 2015, Role of insurance as a risk management tool in construction projects,International Journal of advanced Research in Engineering Science and Management,2(3/3). Froot, K.A., Scharfstein, D.S. and Stein, J.C., 2013, Risk management: Coordinating corporate investment and financing policies.the Journal of Finance,48(5), pp.1629-1658. Grace, M.F., Leverty, J.T., Phillips, R.D. and Shimpi, P., 2015, The value of investing in enterprise risk management.Journal of Risk and Insurance,82(2), pp.289-316. Hwang, B.G. and Ng, W.J., 2013, Project management knowledge and skills for green construction: Overcoming challenges.International Journal of Project Management,31(2), pp.272-284. Hwang, B.G., Zhao, X. and Toh, L.P., 2014, Risk management in small construction projects in Singapore: status, barriers and impact.International Journal of Project Management,32(1), pp.116-124. Manuj, I. and Mentzer, J.T., 2008, Global supply chain risk management strategies.International Journal of Physical Distribution Logistics Management,38(3), pp.192-223. Marcelino-Sdaba, S., Prez-Ezcurdia, A., Lazcano, A.M.E. and Villanueva, P., 2014, Project risk management methodology for small firms,International Journal of Project Management,32(2), pp.327-340. McNeil, A.J., Frey, R. and Embrechts, P., 2015,Quantitative risk management: Concepts, techniques and tools, Princeton university press. Musa, A.M., Abanda, F.H., Oti, A.H., Tah, J.H.M. and Boton, C., 2016, The Potential of 4D modelling software systems for risk management in construction projects. Neuman, W.L. and Robson, K., 2013,Basics of social research, Pearson Canada. Osipova, E. and Eriksson, P.E., 2013, Balancing control and flexibility in joint risk management: Lessons learned from two construction projects,International Journal of Project Management,31(3), pp.391-399. Rothengatter, W., 2017, Risk Management for Megaprojects,The Governance of Infrastructure, p.81. Sadgrove, K., 2016,The complete guide to business risk management. Routledge. Taylan, O., Bafail, A.O., Abdulaal, R.M. and Kabli, M.R., 2014, Construction projects selection and risk assessment by fuzzy AHP and fuzzy TOPSIS methodologies.Applied Soft Computing,17, pp.105-116. Walker, A., 2015,Project management in construction. John Wiley Sons. United States. Zhao, X., Hwang, B.G. and Low, S.P., 2013, Critical success factors for enterprise risk management in Chinese construction companies,Construction Management and Economics,31(12), pp.1199-1214.