Project Life Cycle Model

Project management is referred to as the putting up of knowledge, skills, and other techniques in to accomplish a project efficiently and effectively {Heagney 2011}. Computing project management can be described as the art and science where skillful integration of software technologies, economics and human relations are implemented in the specific context of a software project {Stellman et al 2005}. Furthermore, software projects are highly human-intensive effort that extends a very long period with basic implications on the work and performance of many different classes of individuals. As a lot software projects succeeds, some failed massively. During the recent years, software failures has always been a norm to IT industries and due to

It is one of the most well-known version of the systems development life cycle model for software engineering industries. This model has a linear and sequential development technique. The steps of the life cycle are defined in a very common terms, they are adaptable and their application will vary among different institutions. There are many software development methodologies described and designed which are being implemented during development process of software, the approaches are also specified as software development process models {Royce 1970}. The approach of waterfall model has greatly aided in the difficulty faced previously during so many software projects and it has become the foundation for most software projects acquisition in many industries {Boehm 1988}. Waterfall model is a technique used in software development projects which is considered as the classical approach in software project's lifecycle. It is described as a sequential design process used in software development, in which the success is witnessed as flowing substantially downwards (like a waterfall) through the phases of system and software requirements, Initiation, Analysis, Design, Coding, Testing, Implementation and Maintenance. This method of approach involves limited involvement of clients, requirements are mostly fixed, it requires no or little of feedback. But there is a high probability of problems arising if the requirement are changing or are constantly changing {Royce 1970}. The idea behind the waterfall technique is that it gives room for the directorial control. Deadline schedules for each phase of project's success is made and a product then proceeds through the process of developing under the created schedule. According to an article written by {Boehm 1988}, it is stated that in 1970 the waterfall model provided a very broad enhancement to other project methodologies. These