Test case prioritization and regression test selection

Test case prioritization and regression test selection 1. introduction The significance of software testing process and its affects on software quality cannot be taken too lightly. Software testing is a fundamental component of software quality assurance and represents a review of specification, design and coding. The greater visibility of software systems and the cost associated with software failure are motivating factors for planning, through testing. A number of rules that act as testing objectives are: * Testing is a process of executing a program with the aim of finding errors. * A good test case will have a good chance of finding an undiscovered error. * A successful test case uncovers a new error. Software maintenance is an activity, which includes enhancements, error corrections, optimization and deletion of obsolete capabilities. These modifications in the software may cause the software to work incorrectly and may affect the other parts of the software, as developers maintain a software system, they periodically regression test it, hoping to find errors caused by their changes. To do this, developers often create an initial test suite, and then reuse it for regression testing. Regression testing is an expensive maintenance process directed at validating modified software. Regression Test Selection techniques attempt to reduce the cost of regression testing by selecting tests from a programs existing test suite. The simplest regression testing method, retest all, it is one of the conventional methods for regression testing in which all the tests in the existing test suite are re-run. This method, however, is very expensive and may require an unacceptable amount of time to execute all tests in test suite. An alternative method, regression test selection, reruns only a subset of the initial test suite. In this technique instead of rerunning the whole test suite, we select a part of test suite to rerun if the cost of selecting a part of test suite is less than the cost of running the tests that regression test selection allows us to exclude. Of course, this approach is unsatisfactory as well test selection techniques can have significant costs, and can abandon tests that could disclose faults, possibly reducing fault detection effectiveness. [1] To reduce the time and cost during on testing process, another approach, Test Cases Prioritization in a testing procedure can be favorable for engineers and customers. In Test Case Prioritization techniques, test cases are executed in such a way, that maximum objective function like rate of fault detection can be achieved. In section 2 of this paper, we have described different types of Regression Test Selection techniques and we discussed various categories of these types point out by various authors then moving into the details of selective and prioritizing test cases for regression testing. In this section, we also describe several techniques for prioritizing test cases and we evaluate their ability to improve rate of fault detection, according to various authors. In the next section, we in particular describe the Regression Test Selection techniques and Test Case Prioritization problems. Subsequent sections present our analysis and conclusions 2. Regression testing During a software development life cycle, regression testing may start in development phase of system after the detection and correction of errors in a program. Many modifications may occur during the maintenance phase where the software system is corrected, updated and fine-tuned. There are three types of modifications, each arising from different types of maintenance. According to [2], corrective maintenance, commonly called fixes, involves correcting software failures, performance failures, and implementation failures in order to keep the system working properly. Adapting the system in response to changing data requirements or processing environments constitutes adaptive maintenance. Finally, perfective maintenance covers any enhancements to improve the system processing efficiency or maintainability. Based on of modification of specification authors identify two type of regression testing, Progressive regression testing involves a modified specification. In corrective regression testing, the specification does not change. Corrective regression testing Progressive regression testing * Specification is not changed * Involves minor modification to code (e.g., adding and deleting statements) * Usually done during development and corrective maintenance * Many test cases can be reused * Invoked at irregular intervals * Specification is changed * Involves major modification (e.g., adding and deleting modules) * Usually done during adaptive and perfective maintenance * Fewer test cases can be reused * Invoked at regular intervals Table 1: Differences between Corrective and Progressive Regression Testing According to [2], table 1 lists the major differences between corrective and progressive regression testing. Regression testing is defined [3] as the process of retesting the modified parts of the software and ensuring that no new errors have been introduced into previously tested code. There are various regression testing techniques as given by various researchers are: (I) Retest all, (II) Regression Test Selection and (III) Test Case Prioritization. Retest-All Technique reuses all tests existing in test suite. It is very expensive as compared to other techniques. In this report our main focus on Regression Test Selection and Test Case Prioritization. Let P be a procedure or program, let P be a modified version of P, and let T be a test suite for P. A typical regression test proceeds as follows: 1. Select T C T, a set of tests to execute on P. 2. Test P with T, establishing Ps correctness with respect to T. 3. If necessary, create T, a set of new functional or structural tests for P. 4. Test P with T, establishing Ps correctness with respect to T. 5. Create T, a new test suite and test history for P, from T, T, and T. Although each of these steps involves important problems, in this report we restrict our attention to step 1 which involves the Regression Test Selection problem. 2.1. REGRESSION TEST SELECTION Regression Test Selection technique is less expensive as compare to retest all technique. Regression Test Selection techniques reduce the cost of regression testing by selecting a subset of an existing test suite to use in retesting a modified program. A variety of regression test selection techniques have been describing in the research literature. Authors [1] describe several families of techniques; we consider five most common approaches often used in practice. 1) Minimization Techniques: These techniques attempt to select minimal sets of tests from T that yield coverage of modified or affected portions of P. One such technique requires that every program statement added to or modified for P be executed (if possible) by at least one test in T. 2) Safe Techniques: These techniques select, under certain conditions, every test in T that can expose one or more faults in P. One such technique selects every test in T that, when executed on P, exercised at least one statement that has been deleted from P, or at least one statement that is new in or modified for P. 3) Dataflow-Coverage-Based Techniques: These techniques select tests that exercise data interactions that have been affected by modifications. One such technique selects every test in T that, when executed on P, exercised at least one definition use pair that has been deleted from P, or at least one definition-use pair that has been modified for P. 4) Ad Hoc / Random Techniques: When time constraints prohibit the use of a retest-all approach, but no test selection tool is available, developers often select tests based on hunches, or loose associations of tests with functionality. One simple technique randomly selects a predetermined number of tests from T. 5) Retest-All Technique: This technique reuses all existing tests. To test P, the technique selects all tests in T. According to [3], Test Selection techniques are broadly classified into three categories. 1) Coverage techniques: These consider the test coverage criteria. These find coverable program parts that have been modified and select test cases that work on these parts. 2) Minimization techniques: These are similar to coverage techniques except that they select minimum set of test cases. 3) Safe techniques: These do not focus on criteria of coverage, in contrast they select all those test cases that produce different output with a modified program as compared to its original version. Regression test selection identifies the negative impact of modifications applied to software artifacts throughout their life cycle. In traditional approaches, code is modified directly, so code-based selective regression testing is used to identify negative impact of modifications. In model-centric approaches, modifications are first done to models, rather than to code. Consequently, the negative impact to software quality should be identified by means of selective model-based regression testing. To date, most automated model based testing approaches focus primarily on automating test generation, execution, and evaluation, while support for model-based regression test selection is limited [4]. Code-based regression test selection techniques assume specification immutability, while model-based techniques select abstract test cases based on models modifications. Thus, in model based Regression Test Selection techniques, the existing test suite can be classified into following three main types: 1) Reusable test cases: Reusable test cases are test cases from the original test suite that are not obsolete or re-testable. Hence, these test cases do not need to be re-executed. 2) Re-testable test cases: Test cases are re-testable if they are non-obsolete (model-based) test case and they traverse modified model elements. 3) Obsolete test cases: Test cases are obsolete if their input had been modified. Regression Test Selection techniques may create new test cases that test the program for areas which are not covered by the existing test cases. Model based Regression test suite selection that utilizes Unified Modeling Language (UML) based Use Case Activity Diagrams (UCAD). The activity diagrams are commonly employed as a graphical representation of the behavioral activities of a software system. It represents the functional behavior of a given use case. With behavior slicing we can built our activity diagram. This diagram gives us qualitative regression tests. Using behavior slicing each use case divided into a set of unit of behavior where each unit of behavior represents a user action.[5] An activity diagram has mostly six nodes: 1. Initial node 2. User Action node 3. System Processing node 4. System Output node 5. Condition node 6. Final node 2.3. TEST CASE PRIORITIZATION The main purpose of test case prioritization is to rank test cases execution order to detect fault as early as possible. There are two benefits brought by prioritization technique. First, it provides a way to find more bugs under resource constraint condition and thus improves the revealed earlier; engineers have more time to fix these bugs [6]. Zengkai Ma and Jianjun Zhao [6] propose a new prioritization index called testing-importance of module (TIM), which combines two prioritization factors: fault proneness and importance of module. The main advantages of this prioritization approach are twofold. First, the TIM value can be evaluated by analyzing program structure (e.g., call graph) alone and it also can be evaluated by incorporating program structure information and other available data (e.g., source code changes). Therefore, this approach can be applied to not only regression testing but also non-regression testing. Second, through analyzing program structure, we can build a mapping between fault severity and fault location. Those test cases covering important part of system will be assigned high priority and executed first. As a result, the severe faults are revealed earlier and the system becomes reliable at fast rate. The main contributions of authors [6] are: * They propose a new approach to evaluate the testing importance for modules in system by combining analysis of fault proneness and module importance. * They develop a test case prioritization technique, which can provide test cases priority result by handling multiple information (e.g., program structure information, source code changes) and can be applied to both new developed software testing and regression testing. * They implement Apros, a tool for test case prioritization based on the proposed technique, and perform an experimental study on their approach. The result suggests that Apros is a promising solution to improve the rate of severe faults detection. Authors consider a sample system, which consists of six modules: M1-M6 and there exist some call relationships between each module. A test suite includes six test cases T1-T6 that covers the M1-M6 respectively. Some modules are dependent on each other. They are finding fault proneness and fault severity by using TIM from this system. They conclude the prioritization result (T3, T6, T4, T2, T5, and T1) on the bases of analyzing structure of system. For calculating this result they had developed some formulas and equation. [6] They also did some experiment with two Java programs along JUnit test cases: xml-security and jtopas. They select three sequential versions of the two java programs and apply newly developed software testing and the regression testing. They perform some experiment for finding fault proneness and severe fault. They also introduce the importance of any module using weight fact. Authors [7] explore value-driven approach to prioritizing software system test with the objective of improving user-perceived software quality. Software testing is a strenuous and expensive process. Research has shown that at least 50% of the total software cost is comprised of testing activities.They conclude that, their approach of prioritization of test cases is work effectively with regression and non-regression testing by analyzing the program structure. They make a reach on prior TCP which have two goals: (1) to improve customer confidence on software quality in a cost effective way and (2) to improve the rate of detection of severe faults during system-level testing of new code and regression testing of existing code. They present a value-driven approach to system-level test case prioritization called the Prioritization of Requirements for Test (PORT). PORT based on following four factors. 1) Requirements volatility Is based on the number of times a requirement has been changed during the development cycle. 2) Customer priority Is a measure of the importance of a requirement to the customer? 3) Implementation complexity Is a subjective measure of how difficult the development team perceives the implementation of requirement to be. 4) Fault proneness Of requirements (FP) allows the development team to identify the requirements which have had customer-reported failures. They claim in research paper, Prioritization of Requirement Test (PORT) has great impact on finding severe fault at system level. They are emphasis on Customer priority in TCP for improve the fault detection. Today software industries are working on neutral manner. They set neutral value to all requirements use cases, test cases and defects. To improve the customer satisfactions in software engineering world they are presenting a value-driven approach for system level testing. In these days Regression Test Case Prioritization techniques use structural coverage criteria to select the test cases. They are leading their ideas from structure level to code level TCP for both new and Regression tests. This Paper has two main objectives: 1). Find severe faults earlier 2). Improve customer confidence on particular system. Researchers describe several techniques [8] for prioritizing test cases and they empirically evaluate their ability to improve rate of fault detectionà ¢Ãƒ ¢Ã¢â‚¬Å¡Ã‚ ¬a measure of how quickly faults are detected within the testing process. An improved rate of fault detection during regression testing can provide earlier feedback on a system under regression test and let developers begin debugging and correcting faults earlier than might otherwise is possible. Their results indicate that test case prioritization can significantly improve the rate of fault detection of test suites. Furthermore, their results highlight tradeoffs between various prioritization techniques. Test case prioritization can address a wide variety of objectives. In practice, and depending upon the choice of objective, the test case prioritization problem may be intractable: objectives, an efficient solution to the problem would provide an efficient solution to the knapsack problem [8]. Authors consider nine different test case prioritization techniques. T1: No prioritization One prioritization technique that authors consider is simply the application of no technique; this lets us consider untreated test suites. T2: Random prioritization Random prioritization in which authors randomly order the tests in a test suite. T3: Optimal prioritization An optimal ordering of test cases in a test suite for maximizing that suites rate of fault detection. In practice, of course, this is not a practical technique, as it requires knowledge of which test cases will expose which faults. T4: Total branch coverage prioritization We can determine, for any test case, the number of decisions (branches) in that program that were exercised by that test case. We can prioritize these test cases according to the total number of branches they cover simply by sorting them in order of total branch coverage achieved. T5: Additional branch coverage prioritization Total branch coverage prioritization schedules test cases in the order of total coverage achieved. However, having executed a test case and covered certain branches, more may be gained in subsequent test cases by covering branches that have not yet been covered. Additional branch coverage prioritization iteratively selects a test case that yields the greatest branch coverage. T6: Total fault-exposing-potential prioritization Statement- and branch-coverage-based prioritization consider only whether a statement or branch has been exercised by a test case. This consideration may mask a fact about test cases and faults: the ability of a fault to be exposed by a test case depends not only on whether the test case reaches (executes) a faulty statement, but also, on the probability that a fault in that statement will cause a failure for that test case. Although any practical determination of this probability must be an approximation, we wished to determine whether the use of such an approximation could yield a prioritization technique superior in terms of rate of fault detection than techniques based on simple code coverage. T7:Additional fault-exposing-potential (FEP) prioritization Analogous to the extensions made to total branch (or statement) coverage prioritization to additional branch (or statement) coverage prioritization, we extend total FEP prioritization to create additional fault-exposing-potential (FEP) prioritization. This lets us account for the fact that additional executions of a statement may be less valuable than initial executions. In additional FEP prioritization, after selecting a test case t, we lower the award values for all other test cases that exercise statements exercised by t. T8: Total statement coverage prioritization Total statement coverage prioritization is the same as total branch coverage prioritization, except that test coverage is measured in terms of program statements rather than decisions. T9: Additional statement coverage prioritization Additional statement coverage prioritization is the same as additional branch coverage prioritization, except that test coverage is measured in terms of program statements rather than decisions. With this technique too, we require a method for prioritizing the remaining test cases after complete coverage has been achieved, and in this work, we do this using total statement coverage prioritization. 2.3.1. Search Algorithms for Test Case Prioritization There are many search techniques for test case prioritization, which are being developed and unfolded by various researchers in the field. 1) Greedy algorithm: Works on the next best search philosophy. It [9] minimizes the estimated cost to reach a particular goal. Its advantage is that it is cheap in both execution time and implementation. The cost of this prioritization is O(mn) for program containing m statements and test suite containing n test cases. 2) Additional Greedy algorithm: This algorithm [9] uses the feedback from previous selections. It selects the maximum weight element from the part that is not already consumed by previously selected elements. Once the complete coverage is achieved, the remaining test cases are prioritized by reapplying the Additional Greedy algorithm. The cost of this prioritization is O(mn2) for program containing m statements and test suite containing n test cases. 3) Hill Climbing: It is one of the popular local search algorithms with two variations; steepest ascent and next best ascent. It is very easy and inexpensive to execute. However, this has cons of dividing O(n2) neighbors and is unlikely to scale. Steps of algorithm are explained in [9]. 4) Genetic Algorithms (GAs): Is a search technique [9] based on the Darwins theory of survival of the fit test? The population is a set of randomly generated individuals. Each individual is representing by variables/parameters called genes or chromosomes. The basic steps of Genetic Algorithm are (1) Encoding (2) Selection (3) Cross over (4) Mutation. 3. CONCLUSION In this paper we discussed about Regression test selection and Test Case Prioritization Selection. Regression testing is a style of testing that focuses on retesting after changes are made. In traditional regression testing, we reuse the same tests (the regression tests). In risk-oriented regression testing, we check the same module functionality as before, but we use different tests. Any test can be reused, and so any test can become a regression test. Regression testing naturally combines with all other test techniques. Therefore we use Test Case Prioritization technique inside Regression Testing. Test prioritization makes strengthen our regression testing for finding more severe fault in earlier stages. In this paper we discussed about different factor of prioritization. Customer priority has a great impact on PORT. Our view about both test case selection is, First version of test suite which developed by developer should have concrete test cases. Also at the same stage we should perform some prioritization. With earlier prioritization of test cases we can reduce our cost, time, effort and maximize customer satisfaction 4. References [1] Todd L. Graves, Mary Jean Harrold, Jung-Min Kim, Adam Porters, Gregg Rothermel, An Empirical Study of Regression Test Selection Techniques, Proceedings of the 1998 (20th) International Conference on Software Engineering, 19-25 April 1998 Page(s):188 197. [2] Leung, H.K.N., White, L., Insights into Regression Testing, Proceedings., Conference on Software Maintenance, 16-19 Oct. 1989 Page(s):60 69. [3] K.K.Aggarwal Yogesh Singh, Software Engineering Programs Documentation, Operating Procedures, New Age International Publishers, Revised Second Edition 2005. [4] Naslavsky L., Ziv H., Richardson D.J., A Model-Based Regression Test Selection Technique, ICSM 2009. IEEE International Conference on Software Maintenance, 20-26 Sept. 2009 Page(s):515 518. [5] Gorthi R.P., Pasala A., Chanduka K.K.P., Leong, B., Specification-Based Approach to Select Regression Test Suite to Validate [6] Changed Software, APSEC 08. 15th Asia-Pacific Software Engineering Conference, 3-5 Dec. 2008, Page(s):153 160 [7] Zengkai Ma, Jianjun Zhao, Test Case Prioritization based on Analysis of Program Structure, APSEC 08. 15th Asia-Pacific Software Engineering Conference, 3-5 Dec. 2008, Page(s):471 478 [8] Srikanth H., Williams L., Osborne J., System Test Case Prioritization of New and Regression Test Cases, 2005 International Symposium on Empirical Software Engineering, 17-18 Nov. 2005, Page(s):10 pp. [9] Rothermel G., Untch R.H., Chengyun Chu, Harrold M.J., Test Case Prioritization: An Empirical Study, (ICSM 99) Proceedings. IEEE International Conference on Software Maintenance, 30 Aug.-3 Sept. 1999, Page(s):179 188 [10] Zheng Li, Mark Harman, and Robert M. Hierons, Search algorithms for regression test case prioritization, IEEE Trans. On Software Engineering, vol 33, no.4, April 2007.

How Significant a Role Do Multinational Corporations (Mncs) Play in Today’s Uk Economy in Terms of Their Impact on Employment Relations (Er) and Labour Conditions?

How significant a role do multinational corporations (MNCs) play in today’s UK economy in terms of their impact on employment relations (ER) and labour conditions? This is the question the paper attempts to evaluate through drawing on academic literature and empirical evidence from the 2004 Wers survey. The first section profiles MNCs in the UK, currently dominated by US and German firms. Following this, there is a brief analysis of employment relations in the UK. The third section reviews literature from leading commentators on the subject, highlighting contrasting views and evidence of foreign IR and ER practices. The fourth section looks at key factors that influence the way labour is managed within MNCs subsidiaries. The country of origin effect, the home country effect, the global dominance effect and a global interaction effect as identified by Edwards and Ferner. This is important to assess to what extent MNCs use these factors in the management of labour. Finally, a conclusion will be drawn and a consideration whether MNCs have diffused home country employment relations practices to their UK foreign subsidiaries and if they have affected labour conditions for the UK workforce. Introduction Foreign direct investment (FDI) as a percentage of GDP (Ferner Industrial) in the UK is the highest of any developed country in the world. Since the deregulation of the labour market in the 1980’s the UK has seen a rise in foreign owned companies. According to the WERS 2004 survey, 19 per cent of private sector workplaces with 10 or more employees had some degree of foreign ownership, an increase of 4 per cent on the 1998 survey. Similarly, a rise from 8 per cent to12 per cent of companies were predominantly foreign owned and controlled. For what reason do MNCs choose to set up subsidiaries in the UK? Could it be to take advantage of the nature of the 1 open and deregulated national business system and transfer home country ER practices? Margaret Thatcher and the conservative government came to power in 1979 and in favour of capital markets rather than labour markets; legislations were put in place to weaken the power of unions. The national business system has changed dramatically resulting in an institutionally weak British system. These factors have altered the employment relationship, weakening the statutory and long established support for collective representation. A small proportion of the UK workforce is now covered by collective bargaining (McDonalds) in the employment relationship, although remains the principal form of pay setting (Primarily in the public sector). Union membership has decreased from 13. 2 million members at its peak in 1979 to 6. 7 million in 2005 and union density1 has declined from 32 per cent in 1995 to 29 per cent in 2005. Commentators suggest that MNCs are an important source of innovative work practices, such as a specialist HRM functions. Moreover, that they are able to transfer business models from parent companies, the ‘country of origin effect’ to UK subsidiaries with relative ease. This has been described as a ‘forward diffusion’ of practices. However, evidence suggests that some MNCs, dependant on their country of origin, will adhere to the host country practices even though they conflict with the parent companies policies and practices. This will be explored in more detail further into the paper. The following section of the paper will profile MNCs in the UK. Profile of MNCs MNCs are not homogeneous but are now heterogeneous and are spread across sectors, although are dominant in the fast food and manufacturing industries in the UK. At the 1 The unionised workforce expressed as a percentage of potential membership 2 turn of the century there were 18000 foreign subsidiaries (Contemporary Employment Relations) operating in Britain, with 5000 of these employing more than 1000 employees. They stem from the US, Europe and Asia. The US is dominant with 25 per cent of total FDI to the UK followed by Germany (Bach) with 21 per cent. Foreign subsidiaries employ 18 per cent (Warwick) of the workforce in the production sector in the UK and the incidence of foreign-ownership of UK workplaces has risen since 1998 (Wers 2004) by approximately a quarter. They tend to have commonality it its products and services across its subsidiaries with 52 per cent (Warwick) having an international product. It could be argued that for these reasons they have significant economic and political power and the potential to significantly impact UK employment relations and labour conditions. Employment Relations and Labour conditions in the UK Throughout the 1980’s the Thatcher government and the neo-liberal labour movement stripped unions of their power, collapsing the traditional IR pluralist system under the previous labour governments. Historically unions played a powerful role in the UK economy, with the emphasis on centralised collective bargaining over the employment relationship. Union recognition and membership has since been on the decline. Although, sectorial shifts from manufacturing industries were unionization was predominant to an increase in the services sector is a possible conclusion. Moreover, the increase in small enterprises were unions find it hard to organise is another possible answer. It is evident that unionisation in the UK has lost its appeal and there is a marked shift towards alternative means by firms to regulate the employment relationship. The emphasis is shifting away from the pluralist view to the unitarist view on the role of the individual. Successive Labour government under Tony Blair 3 supported the regulative reforms of the conservative government, although amended the union recognition procedure. This stipulates that unions must be recognised in a workplace if there is a majority consensus of employees. The UK is now under EU directives, most recently the information and consultative directive (ICE) which came into force in 2005. This stipulates that companies with more than 1000 employees must establish a works council. This gives the workers rights to information and consultation on company decisions. Employees are also protected by many employment legislations in areas such as discrimination, unfair dismissal, minimum wage and working time regulations, directives from both the EU and the UK. With the general trend away from union involvement and collective agreements there has been a rise in union substitution strategies in the form of HRM policies in domestic firms. ER in Foreign Subsidiaries The following section reviews business systems of different countries that have foreign subsidiaries in the UK and their stance towards trade unions and practices and policies on employment relations. The US is similar to the UK with respect to the national business system. The framework for union representation in the US is weak and the support for collective bargaining is declining. Throughout the 1990’s unionization rates have declined rapidly from 30 to14 percent (Policies) in US firms leading to widespread non-unionism and anti-unionism. Do US firms then transfer this stance to their subsidaireis? One argument is that many US MNCs, especially in the services sector, with low paid, low skilled workers will use strong union avoidance strategies, the ‘low road’ approach to industrial relations. McDonalds is a key example of this with union membership (MCDonalds) bordering at zero. UK 4 unions find it impossible to organise in the company. According to Royle, a possible reason is the strength of the corporate culture disseminated by management. The chief executive of McDonalds stated that ‘unions do not bring much to the equation of the company’s philosophy of service and employee motivation’. To many US MNCs unions are seen as conflicting with their corporate strategy, the philosophy geared towards shareholder value. This gives them the competitive edge in terms of financial markets in the ever increasing globalising world. However, this has only been observed in certain sectors and it is argued that strong anti-unionism is only existent in few MNCs. If it is existent then exploitative HR policies are commonplace (Policies) which is a ‘Bleak house’ model. Non-union US MNCs use innovative union substitution polices, introducing incentives such as favourable pay and conditions to gain commitment from employees. US firms are characterised by centralised decision making and formalised procedures stemming from the HQ. There is a high degree of employee participation involving direct communication and individualised HR function and pay is predominantly performance related. In contrast to the US and UK, Germany has a strong institutional framework to protect the rights of workers. Collective bargaining in firms is under the force of the law (Royle) and 80 to 90 per cent of the workforce is covered by collective agreements. Conversely to the US, German MNCs tend to adapt to their host country environment, not recognising unions in their subsidiaries, which is divergent to their home country practices. 5 Influences on Labour Management According to Ferner and Edwards there are key influences that affect the way labour is managed in MNCs. Firstly, the ‘country of origin’ effect as mentioned earlier. This is when the MNC exerts its parent company’s management style to their foreign subsidiaries. This contends that MNCs transfer ER practices to subsidiaries in order to converge the firm’s practices and policies across international boundaries. This comes under the convergence theory, were globalisation is pressurising companies to standardize ‘best practice’ policies across its international operations. According to Bach, the pace of convergence is increasing with growth of international trade and integrated financial systems, resulting in the erosion of distinctive national differences in the field of ER and industrial relations. This theory is argued by Traxler, who states that national differences remain intact and national variances will always occur due to differing cultural approaches. This is important as it determines the way employees are managed. Autonomy is not left to the subsidiary and policy making is in the hands of the parent company. This is evident in the report by Warwick that identified 61 per cent of MNCs having a worldwide philosophy on the management of employees. With a loosely regulated framework in the UK it is possible for MNCs do ‘forward diffuse’ certain practices and are able to circumvent the national business system if it is in their interests. The characteristics of a flexible workforce and the ease of dismissal in the UK is an example. This is taking advantage of the host country’s business system. Whether this is a positive or negative impact is dependant on the parent company’s country of origin, the culture of management and the sector of operations and of course their strategic objectives. The extent to which they are able to impact on UK ER through the country of origin effect is questionable. US MNCs 6 are the most likely to diffuse home country practices such as union avoidance and antunionism, as evidence suggests. It is argued that US MNCs will challenge traditional pluralist industrial relations. Although, it is evident that union recognition has been declining in the UK over the last twenty years so to suggest that US MNCs are at the forefront of this change is unsound. Companies are finding alternative methods of managing the employment relationship without the need for intermediaries (unions). A further example of forward diffusion is that of Japanese work practices transferred in the 1980’s. Renowned for the innovative work practice of lean production which was successfully transferred to their UK subsidiaries in the manufacturing industry. The ‘host country effect’ is when the MNC is influenced by the country of operation. Certain factors attribute to the extent to which subsidiaries adopt host countries practices. The regulatory framework of the UK is weak compared to its European counterparts so; therefore, open to MNCs devising policies to suit their strategies and the environment. The global dominance effect is associated with how dominant the MNC is and its country of origin in the global economy. It may either enable or constrain (Edwards, Ferner) MNCs to implement ER practices to foreign operations. This has an effect alongside the home country effect. The US is dominant in the global economy thus its practices of ER are seen as influential and innovative, as did the Japanese form of work organisation. There is evidence to suggest that European countries will adopt such characteristics of this liberal model in order to compete effectively in the ever increasing competitive global economy. The US has brought specialised HRM practices, such as recruitment and training and implemented them across foreign sites. 7 The global integration effect is when the MNC is globally integrated on their policies thus becomes one powerful global company. The best practice to standardise all operations in order to meet their oibjectives. Conclusion It is apparent that MNCs have the economic and political power to impact UK employment relations and labour conditions. Foreign direct investment is crucial in ensuring a progressive economy and creating employment. Margaret Thatcher favoured capital thus deregulated the labour market to encourage FDI. The institutional framework of the UK is now weak and open to the transfer of MNCs IR policies. There is evidence that foreign companies will take on union avoidance strategies but there are few that openly challenge the UK IR system. A possible reason to adhere to the national system could be to ‘keep the peace’ with employees and to maintain good community relations within the areas they operate. The UK environment is such that models of unionism, non-unionism and the ‘Bleak house’ exist in MNCs in the UK and that a cross fertilization of these strategies are forming. There is little impact on the UK framework for IR as it is already evolving from collectivism since the 1980’s towards individualism. Although, there is an increase in the services sector were MNCs are dominant and non-unionism is the preferred strategy. The global dominance effect is a crucial factor on the impact of employment relations in the UK. This is closely related to the country of origin effect and global integration effect. The US at present is the most dominant. The main emphasis is now geared towards the shareholder and a short-termist view is the leading strategy. This is impacting on the labour force as MNCs will use their power to dismiss employees if 8 the strategy is focused on shareholders returns. ER is fairly regulated in the UK, workers are protected by legislation, although MNCs do have the power to circumvent some areas. However, there is evidence that they have been influential in terms of HRM in the UK. There impact can be seen in other foreign subsidiaries and indigenous MNCs in creating specialised HR. The main issue is the speed of globalisation and firms will want to compete in countries that have a weak institutional framework, as capital is favoured compared to labour. It will be difficult for countries to keep their national identities with regard to their IR and ER framework. 9 References Alpin, C, Kersley, B (2006) Inside the Workplace: Findings from the 2004 Workplace Employment Relations Survey, Routledge Chapter 2, 11. Clark, I and Almond, P (2004) ‘Dynamism and embeddedness: towards a lower road? British subsidiaries of American multinationals. Industrial Relations Journal (IRJ), 35:6. Edwards, T. , Ferner, F, Bach, S (2002) ‘The renewed ‘American Challenge’: a review of employment practice in US multinationals’. Industrial Relations Journal, Vol. 33 No. 2, pp. 94-108. Edwards, T and Ferner, A (2005) ‘Managing Human Resources in Multinational Companies’. Managing Human Resources: Personnel Management in Transition (4th Edn), Oxford: Blackwell, Chapter 3. Ferner, A (2003) ‘Foreign Multunationals and Industrial Relations in Britain’, in Edwards, P (2003) Industrial Relations Theory and Practice (2nd Edn), Oxford: Blackwell, Chapter 4. Ferner, A et al (2005) ‘Policies on Union Representaion in US Multinationals in the UK: Between Micro-Politics and Macro-Institutions’, British Journal of Industrial Relations, 43:4. Lee, E (1997) ‘Globalisation and Labour Standards: a review of the issues’, International Labour Review, 136:2. Michael Muller-Camen, Phil Almond, Patrick Gunnigle, Javier Quintanilla, Anne Tempel (2001) Between Home and Host Country: Multinationals and Employment Relations in Europe Industrial RelIations Journal 32 (5) , 435–448 doi:10. 1111/1468-2338. 00210 Royle, T (1999) ‘The reluctant bargainers? McDonalds, unions and pay determination in Germany and the UK’. IRJ, 30:2. Tuselmann, H. , McDonald, F. , Heise, A. (2002). ‘Globalisation, nationality of ownership and employee relations – German multinationals in the UK’. Personnel Review, Vol. 31 No. 1, pp. 27-43. Williams, S and Adam-Smith, D (2006) Contemporary Employment Relations: A Critical Introduction, Oxford, Oxford University Press, pp 61-82. http://www. berr. gov. uk/files/file11423. pdf http://www2. warwick. ac. uk/fac/soc/wbs/projects/mncemployment/conference_papers/ voice_in_mncs. pdf http://www. certoffice. org/annualReport/index. cfm? pageID=annual 10 11

Red and White Mulberry Information and Identification

Red mulberry or Morus rubra is native and widespread in the eastern U.S. It is a rapid-growing tree of valleys, flood plains, and moist, low hillsides. This species attains its largest size in the Ohio River Valley and reaches its highest elevation (600 meters or 2,000 feet) in the southern Appalachian foothills. The wood is of little commercial importance. The trees value is derived from its abundant fruits, which are eaten by people, birds, and small mammals. The white mulberry, Morus alba, is native to China and has several differences including size, foliage, and color of fruit. Fast Facts: Red Mulberry Scientific name: Morus rubraPronunciation: MOE-russ RUBE-ruhFamily: MoraceaeUSDA hardiness zones: 3a through 9Origin: Native to North AmericaUses: Bonsai; shade tree; specimen; no proven urban toleranceAvailability: Somewhat available, may have to go out of the region to find the tree Native Range Red mulberry extends from Massachusetts and southern Vermont west through the southern half of New York to extreme southern Ontario, southern Michigan, central Wisconsin and southeastern Minnesota; south to Iowa, southeastern Nebraska, central Kansas, western Oklahoma and central Texas; and east to southern Florida. It is also found in Bermuda. Description Size: 60 feet tall; 50 foot spreadBranches: Dense branches that droop as the tree grows, and will require pruning for clearance; should be trained to a single leader.Leaf: Alternate, simple, broadly ovate to roughly orbicular, pointed, 3 to 5 inches long, serrate margin, even base, rough and fuzzy undersidesTrunk and Bark: Showy trunk; Gray colors with flattened and scaly ridges.Flower and Buds: Small and inconspicuous flowers with off-center buds; usually dioecious but can be monoecious (both male and female flowers on different branches); male and female flowers are stalked axillary pendulous catkins and appear in April and MayFruit: Reddish black and resembling blackberries; reach full development from June to August; composed of many small drupelets developed from separate female flowers ripening togetherBreakage: Susceptible to breakage either at the crotch due to poor collar formation, or the wood itself is weak and tends to break. Special Uses Red mulberry is noted for its large, sweet fruits. A favored food of most birds and a number of small mammals including opossum, raccoon, fox squirrels, and gray squirrels the fruits also are used in jellies, jams, pies, and drinks. Red mulberry is used locally for fence posts because the heartwood is relatively durable. Other uses of the wood include farm implements, cooperage, furniture, interior finish, and caskets. In landscape use. the species is considered invasive and fruits cause a mess on walks and driveways. For this reason, only fruitless cultivars are recommended. Differentiating White Mulberry When compared to red mulberry, the white mulberry has several key differences:Size: Smaller, at 40 feet tall and 40 foot spreadBranches: Less dense with fewer branchesLeaf: Brighter green, smoother, and more rounded with uneven basesTrunk and Bark: Brown with thick and braiding ridgesFlower and Buds: Centered budsFruit: Less sweet, smaller, and lighter in color, with creamy brownish white berries that start as green, purple, or even black; only females bear fruit Red and White Mulberry Hybrids Red mulberry hybridizes frequently with white mulberry, which has become naturalized and somewhat more common than its native sister throughout parts of the Eastern United States.

Fate in Kurt Vonnegut’s Novel, Slaughterhouse-Five Essay

â€Å"Fate is a misconception, its only a cover-up for the fact you dont have control over your own life.† –Anonymous. In Kurt Vonnegut’s novel, Slaughterhouse-five, an optometrist named Billy Pilgrim becomes unstuck in time uncontrollably and constantly travels between his past, present, and future. Since Pilgrim is unable to control his time warps, he is forced to re-live agonizing moments such as watching his wartime friend Edgar Derby executed for stealing or going through the Dresden bombing repeatedly. However, he is also able to visit pleasant moments like speaking as president in front of the Lions club or his honeymoon with his wife, Valencia. Vonnegut’s use of repetition and vision of war, time and death are crucial to Pilgrim as he†¦show more content†¦They could always visit him or her with the use of time travel when he or she was alive. Because the phrase was very often repeated, it somewhat served as a tally to show how frequently d eath occurs and just how inevitable it is. Billy knew the exact date of his death and how it would happen, but he could not alter it and was no longer afraid of dying, so it had no effect on him because â€Å"there is no why[,]† it just â€Å"simply is† (77; ch4). He learned this from the Tralfamadorians. Through Billy Pilgrim, Vonnegut protests his own feelings about war. Towards the beginning of the novel, Vonnegut visits his old wartime buddy, Bernard V. O’Hare and meets his wife, Mary. She is strangely already mad at Vonnegut because she assumed that he would write a war novel that will glorify the way men fight in wars when they actually send terrified babies off to war, not men. Mary also believed that war movies and books encouraged the chances of war. However, she was not directly angry at Vonnegut; she was angered by the thought of war and how babies are killing other babies on the battlefield. The main event in the novel was the fire-bombing on Dresden during World War II, which both Vonnegut and Pilgrim took part of. Billy Pilgrim was constantly traveling back in time to WWII already knowing this tragedy was going to take place. But again, he went on with life because he knew he could not stop the bombing fromShow MoreRelatedStyle Analysis of Kurt Vonnegut on Slaughterhouse Five1623 Words   |  7 Pagesexample, for instance, is Kurt Vonnegut who may have been stimulated by the war, thus writing Slaughterhouse Ââ€" Five. Though one may categorize this piece as science fiction or even auto - biographical, it can also be interpreted as an anti Ââ€" war piece. Because Vonnegut is classified as a post modernist, one can take into account all the details, such as the similarities between the main character and Vonnegut, the Tralfamadorians, and the style and themes of the novel, and interpret this pieceRead MoreEssay on Anti-War Sentiments in Cats Cradle and Slaughterhouse Five1173 Words   |  5 PagesOn the surface, Kurt Vo nneguts Cats Cradle and Slaughterhouse Five are vastly dissimilar works of literature, each with its own creative style and plot. However, when the texts are examined with a discerning eye one can notice multiple thematic undercurrents such as war fate,time and suffering hidden in plain sight. Overwhelmingly common in Cats Cradle and Slaughterhouse Five are strong anti-war sentiments which show all the ways war is deleterious towards the human condition.(Marvin) VonnegutRead MoreAnalysis Of Kurt Vonnegut s Slaughterhouse Five 1634 Words   |  7 PagesKurt Vonnegut once said, â€Å"So it goes† to describe the unavoidableness of fate. This aspect of seeing terrible things and being able to continue on would become a main theme in his novels. Vonnegut, as an author, received his essential voice by writing about his own experiences, using what would become his signature pessimistic yet humanist view. Vonnegut is described by Lindsay Clark as, â€Å"Worse than a pessimist†¦ he is an eternal optimist doomed to disappointment† (Clark, â€Å"Viewing Four Vonnegut NovelsRead MoreSatire in Slaughterhouse Five Essay862 Words   |  4 PagesIn Slaughterhouse Five, Vonnegut uses satire in the topics of war, aliens, fate and the reasons for life itself. In Slaughterhouse Five by Kurt Vonnegut, the author uses many literary devices to bring across his point including black humor, irony, wit and sarcasm. He mainly uses satire throughout the book. Satire is a literary device found in works of literature that uses irony and humor to mock social convention, another work of art, or anything its author thinks ridiculous to make a point. VonnegutRead MoreKurt Vonnegut s Slaughterhouse Five 1901 Words   |  8 PagesKurt Vonnegut developed his view of America through a history of personal loss and trauma that was largely endured at the same time by his characters. As a child, Kurt Vonnegut lived in Indianapolis, Indiana, which he would use in many of his later novels. His father was a prominent architect, while his mother came from the family of a wealthy brewer. After the depression hit, his father lost his business and gave up, his mother became addicted to alcohol and prescription drugs. In his teen yearsRead MoreSlaughterhouse Five By Kurt Vonnegut979 Words   |  4 PagesSlaughterhouse-five Kurt Vonnegut combines satire, imagery and an anecdotal style to talk about complex issues such as science, religion, sex, socialism, pacifism and tradition. He used his writing to convey messages and warnings to society about these issues. Slaughterhouse-five is one of his most well known novels. In this novel Vonnegut uses fiction to portray shadowy truths about human nature. Billy pilgrim is the main focus of Slaughterhouse-five; through him and other characters Vonnegut portraysRead MoreA Conversation With Real Life Director Harrison Starr1693 Words   |  7 Pagesalways be wars, that they were as easy to stop as glaciers†(3). In this quote, Vonnegut’s compares war with the glaciers. There has always been war just like there have always been glaciers. But there will not always be glaciers since they will all eventually melt and when they do, we will suffer. We are unable to live without glaciers, and we are unable to live without war either. No matter how great his anti-war novels are, Vonnegut doesn’t expect them to change society since he already knows thatRead More Kurt Vonnegut’s Slaughterhouse-Five Essays3848 Words   |  16 PagesKurt Vonnegut’s Slaughterhouse-Five Great artists have the ability to step back from society and see the absurd circus that their world has become. Such satirists use their creative work to reveal the comic elements of an absurd world and incite a change in society; examples include Stanley Kubrick’s film, Dr. Strangelove, and Joseph Heller’s novel, Catch-22. Both works rose above their more serious counterparts to capture the critical voice of a generation dissatisfied with a nation ofRead MoreDeterminism in Slaughterhouse-Five by Billy Pilgrim Essay1460 Words   |  6 Pagescontradicts the belief in free will of the majority of humans in today’s society. Slaughterhouse-Five follows the life of Billy Pilgrim, a young man who has become â€Å"unstuck† in time. The novel traces Billy’s experiences during the bombing of Dresden in World War II, an encounter with extraterrestrials, called Tralfamadorians, and throughout his domestic life as a father, husband, and optometrist. In pa rticular, Kurt Vonnegut explores the bombing of Dresden and the effects thereof on Billy PilgrimRead MoreKurt Vonneguts Slaughterhouse-Five Essay1311 Words   |  6 PagesI. Author- Kurt Vonnegut’s background had an endless influence upon his writing. In his early years, Vonnegut was a private in the 106th infantry division in World War II. He and five scouts were caught behind enemy lines, and then captured. They were held POWs and were beaten on various occasions. In 1945, they witnessed the fire-bombing of Dresden, Germany. Kept during this time in a slaughterhouse, this is part of the inspiration for Slaughterhouse-five. After being released from the Slaughterhouse