The Growth of Anti-Communist Belief In the 20th century Essay

The Growth of Anti-Communist Belief In the 20th century - Essay Example The ideas of communism later grew rapidly spreading the political and social structures in countries all over the eastern bloc and causing an intense rivalry between the east and countries in the Western bloc that were mainly capitalist. During the cold war, the feelings against anticommunism began spreading in the eastern countries thereby resulting in the disintegration of the Union of Soviet Socialist Republics. The cold war created an enabling environment for the spread of propaganda about other countries and economic regimes. The cold war period preceded the Second World War, a period in which countries in the different economic blocs never shared any business transaction and they each lived in fear of the operations of each bloc. Each region therefore feared that the other was progressively becoming stronger and accruing military assets thereby gaining military power. This culminated into fear which no bloc could break by opening war against the other. However, the fear and sus picion that the East had against the economy of the West slowly began countering the effect of communism in the East resulting in the abolition of the economic regime. The West led by the United States of America and countries in Europe had the capitalist economic structure. Capitalism enabled rapid economic growth since it permitted private enterprises thereby enabling the government to collect taxes from the population thereby gaining more revenue. The ideas of capitalism promised rapid economic growth through private investment. The western countries therefore looked economically stronger than the Eastern bloc did since they had enough money to purchase any military artillery they would require. This was unlike the situation in the Eastern bloc where the countries communally owned the economy and therefore the military assets. The regime looked weak and threatened the growth of the entire Asian continent and their affiliates. The precarious times of the cold war therefore created an enabling environment for the spread of propaganda and hate messages among each region. The East progressively became suspicious of the activities of the western bloc, which had active economic activity. The fear and propaganda led to fighting among the different regions in the eastern bloc resulting in the split within the socialist world. The West feared that the growth of the communist ideologies in the East would eventually affect their economies since they targeted foreign markets after the war. The cold war therefore created an enabling environment for the spread of propaganda which the west appropriately created and used their advanced telecommunication mechanisms to spread to east and other neutral countries. The infiltration of the propaganda resulted in fear, which compelled the socialist countries to split their political ideologies a feature in the history of communism that resulted in the creation of left wing anticommunism. The creation of the left wing anti-communi sm preceded the split of the communist parties from the previously predominant socialist second international to create three different political ideologies including the democratic socialist, the third international and the social democrats2. Communism had an elaborate political system referred to as the socialist. The regimes had

Stand up meeting in agile software development Dissertation

Stand up meeting in agile software development - Dissertation Example However, from the development of software methodologies, some classical or pioneering methods evolved. These are now known as the traditional approaches to the development of software. The traditional approach to software development involves the â€Å"definition of requirements which leads to the architecture or design of the development process and implementation† (Dean and Gravel, 2009 p12). This is a basic model that was steeped in convenience and the ability to complete things according to a standard pace. The Committee on Certifiable Dependable Software Systems criticized the traditional approaches to software development for lacking the basis for strong and rigorous analysis (2011). This is because these methods were very basic and depended on the software developer’s testing and validation without the inclusion of other external parties. Another criticism put forward against the traditional approach to software development is that it assumes that this approach i s based on a set of rigidly defined assumptions that will be used as the guideline throughout the process (Kathleen, 2007). This method usually lacks the flexibility that can help in the adjustment of the processes in the course of the software development (Kathleen, 2007). Thus, if the assumption of a given process is not appropriate, the project is prone to failures as it proceeds. A textbook example of the traditional software development approach is the waterfall model which contains rigid steps and levels that the software developer goes through in the completion of a software development process (Segal, 2010). The inherent issues in these systems have led to the creation of more dynamic and flexible approaches to software development like the Agile Software Development methodology. The literature review will critique these approaches and methods and evaluate them in relation to relevant issues and matters that are define each of them. This will set the parameters for the discu ssions on stand meetings and scrum meetings in dynamic approaches to software development. 2.1 Waterfall Approach The Waterfall Approach to the development of software follows a sequential process where activities follow each other downwards, like a waterfall; hence the name. The sequence applied in this methodology involves the analysis of requirements, design, coding, validation (testing), installation, and maintenance (Royce, 1970). Projects that follow the Waterfall Approach are normally segmented according to the different phases, although some of these phases might overlap during the process. The Waterfall Approach maintains tight resource control, and operations remain limited to the provisions as identified in the requirement analysis. The major setback to this method remains the assumption of having all essential problems and requirements identified at the beginning. This is a challenge because at the onset, there are many opportunities and threats that might not be clear t o the software developers. Unpredictable problems encountered during the project lifetime result in project failure. The method contains numerous activities which must be undertaken through a series of activities identified at the beginning of project. Figure 1: The Waterfall Approach (Source: Snyder, 2002) Figure 1 shows the fundamental stages and phases of the Waterfall Approach to software development. It depicts the sequential phases that a software develope