INFORMATION SYSTEMS DEVELOPMENT

Information Systems Development



Information Systems Development

Task # 1: Range of software Development Methodologies

Rapid Prototyping Methodology

This methodology generates a program that executes some important or possibly typical functions for the end product. A throwaway prototyping approach is mostly used if the objective is the testing of the execution method, acceptability of end user or language. If these tools are totally feasible, the prototype might become the source of the development of the final product. However, it is only a vehicle to enter a totally secure operational specifications. The new feature of this methodology is that it makes use of various prototypes. After gathering requirements, a prototype application is developed and presented to the end users. The feedback from the end users offers a loop for improving the application.

In our considered case the advantage of this prototype methodology will be that delivery time will be greatly reduced as this methodology skips many of the stages that are common in other methodologies in favor of lower cost and fast development of software (Purcell, 2007, pp 3). But on the other hand, it will not be perfect to be considered for our desired information system development as this methodology will be too fast that complete testing will not be done.

Incremental Methodology

The incremental methodology is the modification of the prototype methodology. This methodology is intended for delivering functional quality system at each stage of development, but it doe not complete the operational specifications (Jayaswal & Patton, 2006, pp 14). In case where we have to develop a large scale information system then it will not be flexible as it will not be able to respond to complex requirement changes as the development will progress. But its advantage in this concern will be that developers and analysts will be able to tackle minor complexity issues. Both developers and end users will be able to learn from the development process of the information system but this would generate a risk for the end users as learning will exceed the development and productivity, project will become research based project that will exceed budget and time and the project management team will not be able to deliver the desired information system on time.

Waterfall Methodology

The Waterfall Methodology is the oldest and most popular software development methodology. The distinctive characteristic of the Waterfall methodology is its step-by-step phases from analysis of requirements to maintenance. The main weakness of the Waterfall methodology in our case of the development of the large scale information system is that after gathering requirements for project in the initial phase, there will be not any proper way to bring changes to the project if requirements will change or more information will become available to the project management team. During the long development phases, the requirements might vary at any developmental stage.

The waterfall methodology is not an appropriate approach to be adopted when the requirements are not properly understood or known by the project development team. The reason of not selecting this methodology in the development ...