DEVELOPMENT OF MANAGEMENT INFORMATION SYSTEM

The Development process of a MIS is based on its various models . Systems development: The activities that go into producing an information system solution to an organizational problem or opportunity Systems analysis: The analysis of a problem that the organization will try to solve with an information system Feasibility study: As part of the systems analysis process, the way to determine whether the solution is achievable, given the organizations resources and constraints

Some Models of MIS are as below:

1.SPIRAL MODEL :
What is the Spiral Model?

The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. The spiral model was defined by Barry Boehm in his article A Spiral Model of Software Development and Enhancement from 1985. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration matters. As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with the client (who may be internal) reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.

2. WATERFALL MODEL :

The waterfall model is a sequential development process, in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance. The first formal description of the waterfall model is often cited to be an article published by Winston W. Royce[3] in 1970 although Royce did not use the term "waterfall" in this article. Basic principles of the waterfall model are:[1]

Project is divided into sequential phases, with some overlap and splashback acceptable between phases. Emphasis is on planning, time schedules, target dates, budgets and implementation of an entire system at one time. Tight control is maintained over the life of the project through the use of extensive written documentation, as well as through formal reviews and approval/signoff by the user and information technology management occurring at the end of most phases before beginning the next phase.