You are on page 1of 15

MANAGEMENT

INFORMATION
BYSYSTEM
GROUP – I
DEVELOPMENT OF
MANAGEMENT
INFORMATION SYSTEM
DEVELOPMENT OF long
range plans
Development of Long-range plans
Long term plans are necessary for
success of implementation MIS.
Originally computers are just used for
computing and accounting, not for
managing “information” as resource.
Computers now are used as tool for
information processing and storing large
database or knowledge base.
MIS should be flexible enough to deal
with the changing information needs of
business management.
• MIS should be conceived as an open system
continuously interacting with the business
environment with a built in mechanism to
provide the desired information as per the new
requirements of management.
• The plan of MIS should be consistent to the
business plan of organization.
• The business plan should be strategic, or
otherwise states the information needs.
• The plan of development of the MIS is linked
with the steps of the implementation in a
business development plan.
• The system of Information generation is so
planned that strategic information is provided
for the strategic planning, control information is
provided for short term planning and execution.

• Once the management needs are translated into


information needs, it is left to the designer to
evolve a plan of MIS development and
implementation.
Contents of MIS Plan
• MIS plan has to be linked to Business plan.
• Strategy for the plan achievement.
• Development Strategy.
• System Development Strategy.
• Resources for system development.
• Manpower composition.
• The architecture of MIS.
– (Inputs, outputs, linkages, subsystems, coupling and
decoupling etc.)
• The system Development schedule.
• Hardware and software plan.
Information System Development
• There are mainly two methods of application development:
» Experimental, prototyping approach.
» Life cycle approach
• Prototyping Approach
– Evolutionary design method “prototyping” can be used for development of
information system application.
– A prototyping methodology is initiated by a user who conceives of a
problem or an opportunity to be solved by an information system.
– Prototyping an application system basically a four step process:
• STEP 1: Identify the users basic information requirement.
• STEP 2: Develop an initial prototype system.
• STEP 3: Use the prototype system to refine the user’s requirements.
• STEP 4: Revise and enhance the prototype system.
– Advantages:
• Ability to try out ideas without incurring large costs.
• Lower overall development costs.
• Effective utilization of resources.
– Disadvantage:Frequent changes in design .
Prototype Application Development

Identify the basic information requirements


Basic needs, Scope of application, Estimated costs

Development of Initial Prototype

Initial Prototype

Use prototype and refine requirements

Operational Prototype Yes


Is user/ Designer Satisfied Enhanced
Prototype

No
Use prototype as
specifications for Working Prototype
application Development

Revise and enhance prototype

Use Prototype as
Application
Life Cycle Approach To Application System
Development
• Common method used.
• Well defined process by which an application is conceived,
developed and implemented.
• Phases in the system development cycle provide basis for
management and control.
• The information system development cycle for an application
contains three major stages:
» Definition Stage
» Development Stage
» Installation and Operation
Proposal Definition:

Definition Stage
Preparation of request for a proposed application
Feasibility Assessment:
Evaluation of feasibility & cost benefit of proposed application
Information requirements:
Determination of information needed

Conceptual Design:
User oriented design of application

Development Stage
Physical System Design:
Detailed design of flows and procedures in application processing
system & preparation of program specifications
Physical Database Design:
Design of internal schema for data in database or design of files

Program Development:
Coding and Testing of Computer programmes

Procedure Development:
Design of procedures & preparation of user instructions

Operation Stage
Installation and
Conversation:
Final System test and conversion

Operation and Maintenance:


Day to day operation, modification and maintenance
Post Audit:
Evaluation of development process, application system & results of use
Implementation of the Management
Information System
• Implementation is a management process.
• In the process of implementation, the system
designer acts as a change agent or a catalyst.
• User of the system has certain fear complex, when
cultural work change is occurring, which is to be
removed by the developer.
• Another fear is the role played by the person in the
organization and how it affects him.
• There are certain guidelines for the systems
designer for successful implementation of the
system. The system designer should;
1. Not question beyond a limit the information need of the user.
2. Not to forget that his role is to offer a service and not to demand
terms.
3. Remember that the system design is for the use of the user and
it is not the designer's prerogative to dictate the design features.
In short, the designer should respect the demands of the user.
4. Not to mix up technical needs with the information needs. He
should try to develop suitable design with appropriate
technology to meet the information needs. The designer should
not recommend modifications of the needs, unless technically
infeasible.
5. Impress upon the user the global nature of the system design
which is required to meet the current and prospective
information need.
6. Not to challenge the application of the information in decision
making.
7. Impress upon the user that the quality of information depends
on the quality of input.
8. Impress upon the user that you are one of the users in the
organization and that the information is a corporate resource and
he is expected to contribute to the development of the MIS.
9. Ensure that the user makes commitment to all the requirements
of the system design specifications. Ensure that he appreciates
that his commitments contribute largely to the quality of the
information and successful implementation of the system.
10. Ensure that the overall system effort has the management's
acceptance.
11. Enlist the user's participation from time to time, so that he is
emotionally involved in the process of development.
12. Realize that through serving the user, he is his best guide on the
complex path of development.
13. Not to expect perfect understanding and knowledge from the
user as he may be the user of a non-computerized system. Hence,
the designer should be prepared to change the system
specifications or even the design during the course of
development.
14. Impress upon the user that the change, which is easily possible
in manual system, is not as easy in the computer system as it calls
for changes in the programs at cost.
15. Impress upon the user that perfect information is non-existent,
his role therefore, still has an importance in the organization.
16. Ensure that the other organization problems are resolved first
before the MIS is taken for development.
17. Conduct a periodical user meetings on systems where you get
the opportunity to know the ongoing difficulties of the users.
18. Train the user in computer appreciation and systems analysis as
his perception of the computerized information system will fall
short of the designer's expectation.

You might also like