MIS DEVELOPMENT

DEVELOPMENT METHODS
LIFE

CYCLE METHOD

PROTOTYPING

METHOD

SYSTEM DEVELOPMENT LIFE CYCLE

SDLC is a mechanism to ensure that information systems are developed to meet the established requirements.
SDLC makes the software development process more efficient and predictable.

SDLC is also known as Waterfall model or Linear Sequential Model because of coherent description of steps taken in the development of information sysyems. SDLC can be developed in a systematic manner and can be reviewed for significant modification.

Stages in SDLC:
System Requirement System Analysis System Design Coding Testing Acceptance

Problem Definition:

On receiving a request from the user for system development an investigation is conducted to state the problem to be solved

System Analysis
Consists of specifications of the present system, description of how the present system works and what it does.

System Design
Consists of the specifications about what the proposed system will do and how it will work. Specifications of the proposed system

System Construction
Consists of Programs Documentation and User Manuals

System Testing and Evaluation

Consists of Testing Verification and Validation of System

Advantages of SDLC:
Clear project objectives Stable project requirements Progress of system is measurable Designed for user and manager

Disadvantages
Time consuming Little scope for iteration Difficulty in responding to changes

Approaches to MIS Development

Top down approach Bottom up approach Integrated approach

Top down approach

The top level defines the business objectives and other parameters. A model of information flow is designed. The information system so developed is viewed as a total system which is fully integrated rather than as a collection of loosely coordinated sub-systems.

The advantage of this system is that top level management becomes eager in the development of this approach. The disadvantage is that, the lower level may not be in the stage to adapt the new MIS. As a consequent, they may not be fully co-operative and participative in the system development and implementation process.

Bottom up approach
Here, the development of MIS starts right from the root level. Data/information requirement and flows are identified. Steps are taken to ensure data-flow and data-integration between the sub systems.

The advantage of this approach is that, it is more realistic, more practical and less theoretical. The disadvantage of this approach is that, it may take more time to interpret the data/information flow and data-integration part.

Integrated Approach

The Integrated approach is a combination of Top-down and Bottom-up approaches, where all levels of managers influences the design of the system.
Top management identifies the structure and design.

This presented to the lower level management for making observations and for suggesting alterative views and modifications. The revised design is drawn and evaluated by the top level and sent down again in a modified form for further consideration, if required.

This is an iterative process, which is continued until a final design is achieved, that satisfies the requirements at all levels of the organisation. Then this design is transformed into operation and implemented into reality.

PROTOTYPING METHOD

PROTOTYPE
Prototypes are instruments used with in the software development process and different kinds of prototypes are employed to achieve different goals. A system that captures the essential features of the later system is most appropriate definition for a prototype.

Prototyping Model

The Prototyping Model is a systems development method (SDM) in which a prototype is built, tested, and then reworked as necessary until an acceptable prototype is finally achieved from which the complete system or product can be developed.

Steps involved in prototyping model:

Requirement Analysis Prototype Design Prototype building User evaluation Refine prototype System implementation

Requirement Analysis

At this stage, the developer tries to understand the content and nature of the customers initial requirements.

During this analysis, the developer should determine the functionality to be represented in the prototype.

Prototype Design

At this stage, the developer should choose a suitable implementation approach to develop the prototype.
Also, a design should be derived for the prototype based on the analysis of initial requirements and choice of implementation approach.

Features of prototype design are

Rapidity and Ease of modification.

Prototype building

This stage involves the actual coding of the prototype.

Consists of three tasks User interface construction Implementing the functional behaviour Developing the data model

User Evaluation

After the prototype construction it is presented to the customer for review. Comments and suggestions are collected from the customer.

Prototype Refinement

Information collected from the customer is processed and the prototype is refined. The developer revises the prototype to make it more effective and efficient.

System implementation

Once the prototype is refined it eventually produces a working system which can be considered for the fully functional system.

Overview of Prototyping model

When using the Prototyping Model, the developer builds a simplified version of the proposed system and presents it to the customer for consideration as part of the development process. The customer in turn provides feedback to the developer, who goes back to refine the system requirements to incorporate the additional information. Often, the prototype code is thrown away and entirely new programs are developed once requirements are identified.

Advantages
Reduced time and costs Improve the quality of requirements and specifications provided to developers Improved and increased user involvement

Disadvantages
Insufficient analysis Needs rapid development Expense of implementing a prototype

Differences between Life cycle and Prototyping

Lifecycle Method
Testing and training done after implementation of the system

Prototyping
Testing and training are done before implementation of the system.

Scope of the design and the It is prototyping based so application is fully determined with Experimentation is necessary. clarity and experimentation is not necessary. Closed system with little or no uncertainty about the information needs. Open system with a high degree of uncertainty about the information needs.

Information Systems

Types of Information systems

Decision Support system Expert System Knowledge work system Group Decision Support System