INFORMAL INFORMATION SYSTEM

The formal information system is a power structure designed to achieve company goals. An
organization’s emphasis on control to ensure performance tends to restrict the communication flow
among employees, however. As a result, an informal information system develops. It is an employee
based system designed to meet personnel and vocational needs and to help solve, work related
problems.

COMPUTER BASED INFORMATION SYSTEM

A third class of information system relies on the computer for handling business applications. The
computer is now a required source of information. System analysis relies heavily on computers for
problem solving. This suggests that the analyst must be familiar with computer technology and have
experience in handling people in an organizational context.

INTERPERSONAL COMMUNICATIONAL SYSTEM

Interpersonal communication is the sending and receiving of information between two or more
people. Interpersonal communication in the workplace also involves this interaction in varying
relational situations, such as between co-workers and between superior and subordinates. Interpersonal
communication is a process of exchange.

The components of this process include sender, message, channel and receiver. The sender is the one

Some limitations of interviews and questionnaires in management information system are:

1. Response Bias: Respondents may not answer truthfully or may give socially desirable answers,
leading to inaccurate data.

2. Limited response options: Questionnaires may have limited response options, making it difficult
for respondents to express their true opinions or experiences.

3. Time Constraints: Interviews can be time-consuming and resource-intensive, especially when a

4. Reliance on self-report: Both interviews and questionnaires rely on self-reported data, which
may not always be accurate or reliable.
 5. Limited Flexibility: Questionnaires have limited flexibility, as they must be structured in a specific
way to be administered and analyzed effectively.

6. Difficulty in Capturing Complex Information: Both interviews and questionnaires can struggle to
capture complex or nuanced information effectively.

7. Lack of Confidentiality: Respondents may be hesitant to provide truthful answers if they believe
that their responses will not remain confidential.

A Prototype model is a type of software development process where a working model of a system is
created and tested early in the development process. The goal of a Prototype model is to create a basic
version of the system quickly to gather feedback and make modifications to improve the design.

he steps in system planning in 5 points are:

1. Define the Problem or Opportunity: Identify the problem or opportunity that the system is
meant to address. This step involves identifying the current limitations or inefficiencies of the
existing system and determining the desired outcome. This includes analyzing business
processes, conducting stakeholder interviews, and gathering data to better understand the
requirements of the new system.

2. Determine System Requirements: Determine the specific requirements for the system, including
functional, performance, and technical requirements. This step involves developing a list of
features, functionalities, and performance criteria that the new system must meet. It is
important to involve stakeholders in this process to ensure that all requirements are captured.

3. Develop a Conceptual Design: Develop a high-level design for the system, including an overview
of its components, functionality, and relationships. This step involves creating a visual
representation of the new system, including its structure, components, and interactions with
other systems. The conceptual design should also include an overview of the data flow and the
data architecture of the new system.

4. Implement the System: Install and configure the system, train users, and convert existing data
and processes to the new system. This step involves installing and setting up the new system,
conducting user training, and integrating the new system with existing systems and data. It is
important to have a detailed implementation plan and to thoroughly test the new system before
it is put into production.

5. Evaluate the System: Continuously monitor and evaluate the performance of the system, and
make any necessary modifications to improve it. This step involves regularly monitoring the
 system's performance, conducting user satisfaction surveys, and analyzing system data to
identify areas for improvement. Any issues or problems identified should be addressed through
updates and modifications to the system. This step is critical for maintaining the long-term
success of the system.

Data Flow Diagrams (DFDs)

• Data-flow diagrams provide a graphical representation of the system that aims to be accessible
to computer specialist and non-specialist users alike.

• The models enable software engineers, customers and users to work together effectively during
the analysis and specification of requirements.

• Although this means that our customers are required to understand the modeling techniques
and constructs, in data-flow modeling only a limited set of constructs are used, and the rules
applied are designed to be simple and easy to follow.

• These same rules and constructs apply to all data-flow diagrams (i.e., for each of the different
software process activities in which DFDs can be used).

Four basic elements are used to construct data-flow diagrams:

• processes

• data-flows

• data stores

• external entities
The rest of this section describes each of the four elements of DFDs, in terms of their purpose, how the
element is notated and the rules associated with how the element relates to others in a diagram.

Processes: Processes are the essential activities, carried out within the system boundary, that use
information. A process is represented in the model only where the information which provides the input
into the activity is manipulated or transformed in some way, so that the data-flowing out of the process
is changed compared to that which flowed in.

The main part of the box is used to describe the process itself, giving the processing performed on the
data it receives.

Data Flow: A data-flow represents a package of information flowing between two objects in the data-
flow diagram. Data-flows are used to model the flow of information into the system, out of the system,

and between elements within the system.

The directed line is labeled with the data-flow name, which briefly describes the information contained
in the flow. Data-flows between external entities are depicted by dashed, rather than unbroken, lines.

Data Store: A data store is a place where data is stored and retrieved within the system. A data store is
represented in the data-flow diagram by a long rectangle, containing two locations.

External entities: are entities outside of the system boundary which interact with the system, in that
they send information into the system or receive information from it .

During Structured Analysis, various tools and techniques are used for system development. They are −

• Data Flow Diagrams

• Data Dictionary

• Decision Trees

• Decision Tables

• Structured English
• Pseudocode

• Data Dictionary: A data dictionary is a structured repository of data elements in the system. It
stores the descriptions of all DFD data elements that is, details and definitions of data flows,
data stores, data stored in data stores, and the processes.

• Decision Tree: Decision trees are a method for defining complex relationships by describing
decisions and avoiding the problems in communication. A decision tree is a diagram that shows
alternative actions and conditions within horizontal tree framework. Thus, it depicts which
conditions to consider first, second, and so on.

• Decision Table: Decision tables are a method of describing the complex logical relationship in a
precise manner which is easily understandable. It is useful in situations where the resulting
actions depend on the occurrence of one or several combinations of independent condition. It is
a matrix containing row or columns for defining a problem and the actions.

• Structure English: Structure English is derived from structured programming language which
gives more understandable and precise description of process. It is based on procedural logic
that uses construction and imperative sentences designed to perform operation for action.

• Pseudocode: A pseudocode does not conform to any programming language and expresses logic
in plain English. It may specify the physical programming logic without actual coding during and
after the physical design. It is used in conjunction with structured programming. It replaces the
flowcharts of a program.