The History Of The Heavyweight Methodologies

The History Of The colossus MethodologiesINTRODUCTIONSoftw atomic number 18 has gravel an essential discussion section of adult male sprightliness both at professional and personal goal. The development of softw ar has become a chaotic business and is normally cited as the code and fix. In the initial days the softw be programs were written with bulge out much of cast, shape and without foresighted limit site. This however was fine for the blue clay of ruless. With the advancement of technology several(prenominal) changes were made and it became difficult to incorporate these changes and it was hard to fix the bugs. This was the result of un fourth dimensionly formulation. This has led the roots to another alternative, Methodology. This emphasized on the disciplined dish up of softw ar package development to make the whole packet development outgrowth smooth and predictable.Traditional rules were heavily dep removeent on documentation, invention, work plan and struc ture making it the way to call it the heavy system. However, this seemed increasingly lengthened and frustrating for few developers who were looking for rapid change. This has resulted in consultants preparing methodologies independently. These methods are cognise as immediate methods.Agile methodological analysis is getting extensive popularity in the industry. This is a mix of accepted and controversial practices. It is the features of the drifts such as scope, requirement, vision and size that determine the eliminate methodology that should be roled. Thought practicing professionals chill out tensenesse on the magnificence and physical exercise of heavy methods, the empirical studies are emphasizing on the Agile methods. heavyweight methodologies heavyweight methodologies are considered the conventional way of software development. These are based on step by step evolution approach. Several steps in this surgical operation include, define requirement, solution forma tion, exam and development. In this process it is also mandate to stimulate a document that has a set of requirement at the jump of the project. waterfall approach This emphasizes on structured approach. Each interpret in this process has a set of actions. These activities much be fulfilled before progressing to the next storey. Each arrange is named differently. The commencement ceremony phase determines what the system go out be, the second phase determines how the system will be developed. It is in the third submit that the actual coding and jut outing is started. The developed system is tried and true in the fourth stage. In the fifth and utmost stage appropriate training and documentation are provided. In terms of engineering, the term waterfall is used to denote a subsequent or sequential development.Waterfall nonplus Life CycleUnified Process (UP)Each natural process comprising instanceling is split up into workflows in the UP process. This process takes pla ce in an repetitive and incremental manner. In this method the whole process is separate into four phases. The below diagram depicts the stages of this processInception At the end of this process the feasibility of the project is driven. The scope of the design is set and a business plan is prepared.Elaboration In this phase, a basic design is made and a plan of structure or plait is made. A risk analysis is also done at this stage. The study(ip) risks determined should also be addressed.Construction In the construction phase the system of beta-version is prepared. A well developed system good enough for the introductory test should also be available in this stage.Transition This is the final stage. In this stage the system is commenced to the stakeholders and end users. The process is considered complete if the stakeholders fit out that the objectives mentioned in the inception phase are met.As part of UP there are approximately 50 work items that should be completed. Thi s cockeyed approach and heavy documentation add a lot of the complexness to the UP. Also, the roles in this process are predefined making it less flexible.Spiral ModelThis is another heavy model which merges both design and prototype stages essay to combine the benefits of top-down and bottom-up benefits. The four phases in the development model are as followsObjective setting- In this phase objectives of the project phase are identified.Risk assessment and limitations In this phase key risks are identified and analysed. Information about reducing these risks is also collected in this phase.Development and validation A suitable model is selected for the next phase. prep The project is reviewed and plans for the next round of spiral are made in this phase.Characteristics of Heavyweight methodologiesHeavyweight methodology is known for a long time. This is a very disciplined approach in the software development. Few characteristics of goliath methodologies are as followsPredicti ve approach This methodology plans most part of its software development for a longer time. A great emphasis is given to drawing foc utilize on the needs and measure to exercise these needs. Drawings determine how to phase the system and act as the basis for the construction process. This also predicts time table and budget for building or constructing the software. comprehensive Documentation Traditional software development considers the requirements documentation as a key element of documentation. It collects all the node and stake holder requirements before writing code.Process orientation The purpose of this method is to allocate or define a process of work that suits the one using it. A process may contain few processes just a managing director or a tester move perform. For every task in this method there is a procedure.Agile modellingAgile process concentrates on adding lightness to its processes provideing to high lumber of software and customer satisfaction. Few of t he industrious models are as followsExtreme Programming (XP) This has evaluated out of problems raised from traditional systems. This process is known for short cycles of development, incremental prep and uninterrupted feedback, parley leading to evolutionary designing. This methods life cycle is split into 6 phases i.e. Exploration, Planning, Iterations to release, Production, sustentation and Death.During the Exploration stage, the client creates story boards about his needs. This is followed by the planning phase in which the story boards are prioritised and a first release schedule is prepared. In the Iteration to Release stage it is the office of development team to create the whole system by forever testing and integrating the code. In the Production Phase additional testing and performance chinks are done. Developments and suggestions detected in this stage are document for later implementation. Based on this updated releases are made in Maintenance Phase. The final stage is the Death Phase is reached when customer has no more(prenominal) stories to be implemented and the final documentation is prepared.Scrum Scrum is a repetitive and incremental process of product development. Scrums main focus is on how members should work in order to generate flexibility in a continuously varying environment. At the end of each iteration it makes a set of potential features. In this method it is not compulsory to use any specific software development methods. Key practices in this method are Product Backlog, Sprints, Sprint Planning, meeting, Sprint Backlog and Daily Scrum. self-propelled System Development method This is a mixture, and extension for rapid natural covering development and iterative development practices. The basic notion behind this method is to give more importance to time and resources before the functionality of a system. In this method a high emphasis is given to quality. This method has atomic number 23 stages Feasibility Study A d ecision is made about usage of DSDM. This decision is based on project type, organization requirement and race. This stage has two outcomes, 1) feasibility report ii) A prototype plan business organisation Study A business study to understand the business expectation of the project. This forms the base for prototype.Functional Model Iteration This phase includes analysis, coding and prototypes. The yield of this stage is a prototype code and analysis models.Design and build iteration Main system is built in this stage. The prototypes are reviewed and developments are made based on user comments.Implementation This is the final stage where the project is handed over to the user. Appropriate training is also provided.Characteristics of agile methodologiesPeople oriented All the stakeholders. i.e. customers, developers, users and end users are very outstanding in this methodology.Adaptive This methodology is preferred by those who are absolved to change and are flexible.Balancing Flexibility and Planning Though planning is significant, a trial and error method is followed in this approach as it is hard to predict the right things in the initial stage of software development.Simplified process and small groups A simple process of concentrating on the present rather than the future is the motto of Agile process. It also maintains small teams and any communication is provided to the whole team.ComparisonTraditional heavy methodology for software development is prevailing successfully for a long time now. However, it has several disadvantages such as inflexibility and high time consume etc. Taking these drawbacks in to account a new system was developed which is Agile. Both the methodologies i.e. (agile and heavy weight) have their advantages and disadvantages. People usually use one of these methods based on the feasibility. A Summary of difference in agile and heavyweight is shown in the following table.There are important agentive roles influencing the de cision and selection methodology, which is suitable for different conditions. These factors can be divided into the size of the project, spate and riskProject sizeOne of the major limitations in this process is size of the project. The important elements in this process are budget, time span of the project and team organization. A huge project needs huge team and huge budget. This in turn requires break away co-ordination and mend communication. Heavy methodology provides this by a thorough planning, design and documentation. However, this is not possible in case of Agile process. According to Alistair A light process needs few spate in depraved to the heavy method where more people are required.A major limitation of agile methods is the size of the project. Main elements of the same are budget, succession of projects and organization of the project team. The large unit or a larger budget, you need the larger project. Thus, requires a compilation of more demands, requirements of more people and better coordination. Heavyweight support this methodology by providing planning, documentation and processes for better communication and coordination in large groups. Fewer people are infallible if the methodology used is lighter. However, more people will be call for if the heavier methodology (Alistair Cockburn, 2003). The larger group also has its impact on communication in the design and performance. The methodology is a matter of coordination and management of human communication. This implies that the level of methodology must be increased if the numbers of people increase. This makes it even more difficult to use agile methods with large groups. However, raft Schwaber (one of the developers of SCRUM) argues that large groups can be broken down into small teams using the dimensions of the scrums.Project duration is another factor in the choice of methodology. Heavyweight methodology needs a lot of extra time for output such as documentation, design docu mentation, writing, analysis etc. Therefore, it can be concluded that when time is short agile development methodologies would be the surpass option.People FactorThe Agile methodology gives very much importance to stakeholders i.e. it concentrates on peoples factor. This methodology makes sure that experienced people and skilled people are part of the process. Experts who are part of the team provide continuous feedback about the effects that the use may face in selecting the project. As part of this process the customer also gets a right to check progress and change the direction of development at any stage or iteration. This is one of the main features that make the agile process more attractive than the heavy process.Organizational culture is another important factor while choosing the methodology. If any organization is not open to change and is inflexible, An agile process cant be used there.Risk FactorAn important risk factor in the software development is how it responds to change. Agile methods can be used in case of applications that should be built promptly and dont have any quality hurdles. If the project is critical and requires several quality layers then the traditional system is appropriate. Improper definition may lead to several defects. Agile methodologies help in developing short term projects and give importance to customer reviews.ConclusionI would like to end it by saying that heavy methodology consisted of severe methods of comprehensive planning, design documentation.. Heavy thoughts that accompany them will be taken over by the agile movement not in the distant future. The need for Heavyweight approaches still prevails in large, long-lived projects that have specific earnest, reliability and security requirements. However, business needs to respond quickly to the environment in innovative, cost-efficient and efficient manner is increasing the need to use agile methods of software development.