Abstract In the course of the most recent decade (or two) the pendulum of designer mind has swung strongly in the direction of agile methodology of software development as against the traditional methodology of software development. This paper is being written as Course Project Part 1 researching the evolution of Agile software development paradigms while taking a look at traditional methodologies as a predecessor as they relate to iteration length or project management. In Part 2, the study is on the future of Agile Software Engineering in the next 5 years. Introduction A software development process or life cycle is a structure forced on the development of a software product. There are a few models for such processes, each portraying ways …show more content…
No matter how software development is performed or what approach is taken the essential task involved is, problem-solving. The way developers solve problems is generally the same no matter what the problem is or the approach taken. Problem-solving involves four essential activities: Requirements – gathering and documenting details about the problem; Analysis – understanding the problem in enough detail to ensure a correct solution; Design – finding and specifying an optimal solution to the problem; and Implementation – implementing the solution in whatever form it takes. Every developer goes through the requirements, analysis, design, and implementation cycle, be it over an extended period, a week, a day, an hour or minutes, and whether or not they document the results, discuss them with others on a whiteboard, or just consider them informally within their head. Others apply project management techniques to writing software. Without project management, software projects can easily be delivered late or over budget. With large numbers of software projects not meeting their expectations in terms of functionality, cost, or delivery schedule, effective project management is proving …show more content…
For the purpose of this course project, I will consider the first two. Traditional Project Management Traditional waterfall. The Waterfall SDLC involves sequentially completing each phase in full and then moving on to the next phase. It was never meant to be a practically useful approach to software development. The idea that requirements can be totally completed, and then analysis totally completed, and then design totally completed and then implementation totally completed, is practically impossible. The best-known and oldest process is the waterfall model, where developers follow these steps in order. They state requirements, analyze them, design a solution approach, architect a software framework for that solution, develop code, test, deploy, and maintain. After each step is finished, the process proceeds to the next step. Traditional project management is mainly used on projects where activities are completed in a sequence and there are rarely any