Characteristics Of Heavyweight Methodologies Information Technology Essay

Characteristics Of Heavyweight Methodologies Information Technology Essay Software is part of modern society for over 50 years. Software development began as a chaotic business and is often cited as the code and fix. The software program was written without much of the plan and design of the system. Also, it was set with many short term decisions. That’s fine for small systems, but as systems grow it turned out as increasingly difficult to add new features and bugs were harder to fix. This style of development was used for many years until this was replaced by an alternative: Methodology. This imposed a disciplined process for software development in order to make software development more predictable and efficient. Traditional methods are based on the work plan and begin to extract a complete set of documentation requirements, the architectural and high level of project development and control. Because of these serious aspects of this method has become known as heavy. Some practitioners realized this software development process frustrating. As a result, several consultants have independently developed methodologies and practices to adopt and respond to inevitable changes they have experienced. These methods and practices are based on multiple components, a technique that was introduced in 1975 and which became known as an agile methodology. Agile methodology is gaining popularity in the industry, although they compromise a mix of accepted and controversial software engineering practices. Software industry is likely to prove that the specific features of the project, such as the purpose, scope, requirements, resources, architecture and size will determine the methodology that fits those best. Dynamic and heavy or perhaps a hybrid of the two. In the past few years, anecdotal evidence and success of practicing professionals suggests that effective methods are effective and suitable for a variety of situations and environments. However, empirical studies are urgently needed to assess the effectiveness and possible use of agile software development methods. Heavyweight methodologies Heavyweight methodologies are considered the traditional way of software development. These methods are based on the following series of steps such as defining requirements, solution building, testing and deployment. Heavyweight methodology requires defining and documenting a stable set of requirements at the beginning of the project. Waterfall approach emphasizes a structured progression between certain phases. Each stage consists of a term set of activities and tasks that must be met before the next stage can begin. The phases are always named in different ways, but the basic idea is that in the first phase tries to capture what the system will do, its system and software, in the second phase determines how it will be designed. The third stage is where developers start writing the code; the fourth step is testing the system and final phase focuses on tasks such as training and documentation. However, in engineering practice, the term waterfall is used as the generic name for all subsequent methods of software engineering. Waterfall Model Life Cycle Unified Process All  activities,  including  modeling, is  divided into  workflows  in the  Unified Process  (UP) and takes place  in an  iterative  and  incremental manner. In this process the process is divided into four phases. The below diagram depicts the stages of this process: