Systems Development and Project ManagementInformation technology is an important element of a company's future success. For businesses to move restrictively into the future, they must continue to improve their information technology. The systems development process and its management are important aspects of strategically improving a company's existing IT system or improving it for the future. Systems development can be simply described as the process you follow to develop the product(s) that meet the needs of your organization. This type of development process is described as a waterfall process. There are several development processes, but the one most talked about is the waterfall process. The other type of development process is the iterative process. This type of process is mainly used by business developers for a client who is not sure what they want to develop for them. Each of the processes has a template that describes many of the tasks or activities that occur when you use either process. To name just a few models you own, the Waterfall model, the Spiral, the prototype and the Evolutionary model. To explain a model, an example would be the Cascade. The model is pretty much the same as the Waterfall process. This particular template shows the progress of your project. You start by receiving, processing and sending your inputs to the next activity as input and the process continues until you have your final product as output. Each process and module has advantages and disadvantages depending on the type of product or system you are developing. According to Travis Bakersville in his article “The Impact of Computer-Aided Technologies on Information Systems Development,” there are five types of systems development methodologies. . The types are structured approach, prototyping/iterative approach, rapid application development, object orientation and other types. Based on the above types, 76.5% of organizations use the structured approach. Among these different methodologies, a survey was carried out to see how companies acquired their methodology. According to Judy Wynekoop, 35% of organizations purchased their methodology and 65% developed their own in-house. There are many surveys and comments from various IT managers who believe that every project development should use a methodology. However, a consensus is that no particular methodology is appropriate for every project development process and each IS manager reports modifying methodologies depending on the project..