Unit 02 - People & Organizations
Unit 02 - People & Organizations
Unit 02 - People & Organizations
INFORMATION SYSTEM
Unit 2
People
Characteristics of People
Organization
Information System Personnel
System Models
System Development Life Cycle
Arslan Umar
PEOPLE
3
People
• People are the most important part of any organization
and thus of any MIS. An MIS often succeeds or fails on
the basis of people involved
• Physiological Factors
• Ergonomics
• Workers Skills and Abilities
• User Interfaces
• Memory Processes
• Learning
• Psychological Factors
6
Physiological Factors
• MIS jobs are physically demanding, e.g. a person used to
work on input of data can suffer from eyestrain,
headaches, neck and back problems due to long sitting
against display terminals
Ergonomics
• The field that studies computer workspaces and their
effects on users is known as ergonomics
User Interfaces
• Many of the interfaces for workers who enter Transaction
Processing Data are typically designed for the lowest
capability workers
Memory Processes
Memory
Receptors
(Eye, Ear, Short Term
Nose) Memory (Brain)
Processor
Environment (Brain)
Effectors Long Term
(Physical, Memory (Brain)
Spoken,
Written)
External Memory
(Notes and
Reference
Materials)
12
Learning
• Acquisition of knowledge or skills through study,
experience, or being taught.
• How people learn is an important consideration when
building or upgrading computer systems
Psychological Factors
A large number of psychological factors
contribute to the success or failure of an
Information Systems:
• Perception (2 different people see same thing in different ways)
• Attitudes (Expression of feelings about people, objects, events etc.)
• Risk Taking Tendencies (Risk Seeker, Risk Avoider)
• Willingness to Change
ORGANIZATION
15
Organization
• Relatively long term, output producing entity that consists
of more people, has one or more goals and conducts
itself to achieve these goals
• Delicately balanced
• Conflict resolution
17
• Division of labor
• Hierarchy
• Politics
• Culture
18
• Public / Private
• Centralized / deCentralized
19
• Organization characteristics
• Product line
• Expansion strategies and system integration
• Merger or acquisition
• Size
• Organizational structure
• Function
• Product/service
• Customer
• Geography
20
• Culture
• Norms
• Status
• Roles
• Participation
• Leadership
INFORMATION SYSTEM PERSONNEL
22
23
Information System
Specialists:
IT Infrastructure: CIO
Hardware Managers
Software System Analysts
Networks Programmers
Network Specialists
Database Administrator
Clerical
24
25
CIO
Data Processing
Director
System Environment
• All system functions within some sort of environment. The
environment is the collection of elements. The elements
surround the system and often interact with it
Environment
System
Boundary
29
Types of Models
• Mathematical Models
• Physical Models
• Graphical Models
32
Mathematical Models
•A Mathematical Model is used to express
relationship, in mathematical terms
33
Physical Models
•A Physical Model is usually a three-dimensional
representation that can be held or touched
Graphical Models
• Graphical Models generally use symbols as icons,
boxes and lines to represent real world elements and
the relationship between them, for example, Data
Flow Diagrams, Entity Relationship
Diagrams, Flow Charts etc
GRAPHICAL MODELS
36
• An arrow
• An open-ended rectangle
37
An ENTITY is a person,
group, department, or any
system that either receives
or originated data
Levels of DFD
• …..
40
• An arrow
41
An ENTITY is a person,
Entity group, department, or any
Name system that either receives
or originated data
Passenger
Reservation
Airline
43
An ENTITY is a person,
Entity group, department, or any
Name system that either receives
or originated data
ERD
• Graphical representation of database design is called
Entity Relationship Diagram
45
Flow Charts
2 - Determining
Information
1 - Identifying Problems, Requirements
Opportunities and
Objectives
3 - Analyzing System
Needs
7 - Implementing and
Evaluating the System
4 - Designing the
Recommended System
6 - Testing and
Maintaining the System 5 - Developing and
Documenting Software
50
• The first phase requires that the analyst look at what is occurring in
the business, together with the organization people, the analyst
pinpoint the problems
• Identifying objectives
• First the analyst must discover what the business is trying to do, then
the analyst will be able to see if some aspects of information systems
applications can help the business reach its objectives
51
• People
• Users
• Analysts
• Systems Managers coordinating the project
52
• Activities
• Output
• Feasibility report
• People :
• Analysts
• Users
• Activities
• Output
• Analyst understands
• how the business functions
• have complete information on the
• people
• goals
• data
• procedures involved
58
• People
• System Analysts
• Activities
• Output
• System Analyst prepares a system proposal that summarizes what
have been found, provides analysis and makes recommendations.
If one of the recommendations are acceptable to the management,
the analyst proceeds along with the course
60
• People
• System Analysts
• People :
• Analysts
• Programmers
• Users
63
• Activities
• Output
• Analyst
69
FINAL PROJECT TASKS – UNIT 2
Using MS Word
Start Project Documentation; Introduction, Details of Visits to Organization
& Interviews Conducted, Details of Exiting Business Processes
&
On paper
Design DFDs; Context, Zero, One and next level DFDs of organization
Design Flow Charts of Selected Business Processes
Design Entity Relationship Diagram of Organization
Design Output Screens – Forms