Professional Documents
Culture Documents
Unit 2
People Characteristics of People Organization Information System Personnel System Models System Development Life Cycle
Zeshan Ahmer
PEOPLE
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
A number of human characteristics can have an impact
PEOPLE CHARACTERISTICS
Ergonomics
Workers Skills and Abilities User Interfaces Memory Processes Learning Psychological Factors
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
Workers physical workspace can also poorly designed or
Ergonomics
The field that studies computer workspaces and their
attempts to overcome the problems associated with poorly designed computer workspaces that causes unnecessary physical and mental stress
that many on the job behaviors are affected by the skills and abilities that worker posses
An employees capability to perform job tasks determines
User Interfaces
Many of the interfaces for workers who enter Transaction
Processing Data are typically designed for the lowest capability workers
At McDonalds or KFC, the terminals have special
keyboards to facilitate fast and accurate data entry, e.g. if a customer buys a burger, the clerk have to only press the key that has a picture of the item the customer ordered, the key with picture of burger
10
Memory Processes
People differ in both their ability to memorize and in
speed which they recall the facts that are saved to memory
Short Term Memory Long Term Memory External Memory
11
Processor (Brain)
Long Term Memory (Brain)
12
Learning
How people learn is an important consideration when
13
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
A formal collection of people and other resources
established to accomplish a set of goals General Motors, National Wildlife Foundation, Shaukat Khanam, Nestle, Interwood
16
Delicately balanced
Conflict resolution
17
18
20
21
IT Infrastructure:
Hardware Software Networks
CIO Managers System Analysts Programmers Network Specialists Database Administrator Clerical
22
23
CIO
Telecommunications
Data Administration
Manager of programming
Staff
SYSTEM MODELS
25
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
Systems are normally delimited by a BOUNDARY, which
separates them from environment. Anything within the boundary is the part of the system and anything outside is the part of the environment
26
Environment
System
Boundary
27
system elements. The Arrows indicate the relationship among these elements
areas, such as marketing, finance, research, development etc. Each of the functional areas can be viewed as the subsystems of the larger organizational system
28
For Example, a drawing of human skeleton is a graphical model of the bone structures of human
29
Types of Models
Mathematical Models
Physical Models
Graphical Models
30
Mathematical Models
A
to
express
31
Physical Models
A
32
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
34
35
An ENTITY is a person, group, department, or any system that either receives or originated data A DATA FLOW shows that information is being passed from or to a process A DATA STORE shows the Interaction with a database
36
37
Levels of DFD
Context Level DFD Zero Level DFD
38
three symbols:
A rectangle with rounded corners A square with two shaded edges An arrow
39
Entity Name
An ENTITY is a person, group, department, or any system that either receives or originated data
Information Passed
40
Passenger
Travel Confirmation
Travel Agent
Travel Confirmation
Chosen Flight
Ticketing Information
Passenger Reservation
Airline
41
Entity Name
Information Passed
D1 Table1
42
ERD
Graphical representation of database design is called
43
Flow Charts
A chart that shows the sequence of actions to be held in a
45
of systems
Analysts disagree on how many phases there are exactly
46
Problems,
Opportunities
and
Objectives Determining Information Requirements Analyzing System Needs Designing the Recommended System Developing and Documenting Software Testing and Maintaining the System Implementing and Evaluating the System
47
4 - Designing the Recommended System 6 - Testing and Maintaining the System 5 - Developing and Documenting Software
48
and objectives
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
49
People
Users Analysts
50
Activities
Interviewing user management Summarizing the knowledge obtained Estimating the scope of project Documenting the results
51
Output
Feasibility report containing a problem definition and objectives summary
52
are sampling and investigating hard data, interviewing, questionnaires, observing decision makers behavior and office environment
In
this phase, analyst tries to understand information user needs to perform their jobs
what
53
People :
Analysts Users Typically operation managers and workers
54
55
56
Activities
Special tools and techniques help the analysts make
requirements definitions
One such tool is the use of data flow diagram to chart
57
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
58
to accomplish the logical design of the information system. The analyst design the accurate data entry processes
59
60
Users
61
Activities
Analyst work with programmers to develop software that
is needed
Tools used are structure charts, flow charts and pseudo
code
The
analyst use one or more of the tools to communicate with programmer what needs to be programmed
62
63
Output
Analyst
64
tested. It is much less costly to catch problems before the system is signed over to users
Some of testing is done by programmers alone and some
65
MIS
Final Project
Visit Organization Chosen for Group Project Meeting with Contact Person in Presence of All Group Members Ask Questions to Understand Business Processes Completely
67
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