Employee - Cal State LA - Instructional Web Server

Download Report

Transcript Employee - Cal State LA - Instructional Web Server

Management Information Systems
CIS 301
Spring 2006
Week 10 Lectures
Dr. David Gadish
© 2004-06, David Gadish, Ph.D.
1
Week 9 Review
 More student introductions
 Protecting People and Information – threats
and Safeguards (Chap 8)
 Building and e-Portfolio (ELM-I)
© 2004-06, David Gadish, Ph.D.
2
Week 10 Overview
 Implementing a Database with MSAccess
(ELM-J)
 Protecting People and Information - Threats
and Safeguards (Chap 9)
 Course Review / Discussion
© 2004-06, David Gadish, Ph.D.
3
Student Introductions…
 Your name
 What you do
 How computers are used in your
business/life
 What you want to do in life
 How can technology help?
© 2004-06, David Gadish, Ph.D.
4
Implementing a Database
with MSAccess
ELM - J
5
Overview
 Implementing The Structure Of Your Employee
Database
 Defining Relationships Within Your Employee
Database
 Entering Information Into Your Employee
Database
 Creating A Simple Query Using One Relation
 Creating An Advanced Query Using More Than
One Relation
 Generating A Report
© 2004-06, David Gadish, Ph.D.
6
Introduction
 The following slide has the correct database
structure from Extended Learning Module C.
 Revisit Module C if you need a refresher.
© 2004-06, David Gadish, Ph.D.
7
Introduction
© 2004-06, David Gadish, Ph.D.
8
Implementing The Structure Of
Your Employee Database

Data dictionary - contains the logical structure for the
information.

To create a database using Microsoft Access, perform the
following steps:
1.
2.
3.
4.
Start Microsoft Access.
Select Blank Database on the right side of the screen or select
File and New from the menu and then Blank Database on the
right side of the screen.
Select a folder for the database and enter a file name (we’ll use
Employee.mdb).
Click on Create.
© 2004-06, David Gadish, Ph.D.
9
Implementing The Structure Of
Your Employee Database
Create a blank
database by clicking
on Blank Database.
© 2004-06, David Gadish, Ph.D.
10
Implementing The Structure Of
Your Employee Database
Select a location and
provide a database
name.
© 2004-06, David Gadish, Ph.D.
11
Implementing The Structure Of
Your Employee Database
 To create a relation (table) using the Design view, make
sure the Tables tab is selected and then double-click on
Create table in Design view.
 Enter a name, data type, and description (the last is
optional) for each field in a given relation.
 Save that structure and repeat the process until you’ve
created the structure for each relation in your database.
© 2004-06, David Gadish, Ph.D.
12
Implementing The Structure Of
Your Employee Database
To define the structure of a
relation, first select the
Tables tab and then
double-click on Create
table in Design view.
© 2004-06, David Gadish, Ph.D.
13
Implementing The Structure Of
Your Employee Database
Enter field names and
data types here.
© 2004-06, David Gadish, Ph.D.
14
Implementing The Employee
Relation Structure
To identify a primary key,
place your cursor in the
appropriate row and click
on the key icon. The key
icon will then appear to
the left of the field name.
This is the field properties
for Employee ID, the
primary key. Notice that it
does not allow for
duplicates.
© 2004-06, David Gadish, Ph.D.
15
Implementing The Employee
Relation Structure
 We entered three fields for the Employee relation
– Employee ID, Name, and Department Num.
– Employee ID = Number
– Name = Text
– Department Num = Number
© 2004-06, David Gadish, Ph.D.
16
Implementing The Employee
Relation Structure
 We identified Employee ID as the primary
key by placing a key symbol next to its field
name.
 You’ll perform this process for each
primary key in each relation you create.
© 2004-06, David Gadish, Ph.D.
17
Implementing The Employee
Relation Structure
 To save the structure, click on the disk icon
(Save As), enter Employee as the table
name, and click on OK.
 You can then close the Table: Employee
box.
© 2004-06, David Gadish, Ph.D.
18
Implementing The Job Relation
Structure
Job Number is the
primary key.
This is the field
properties for Job Name.
We have set Allow Zero
Length to No which
means that you must
enter something in this
field.
© 2004-06, David Gadish, Ph.D.
19
Implementing The Job Relation
Structure
 We created the Job relation by using the Design
view.
 We identified Job Number as the primary key by
placing the key icon beside its name in the field
name list.
© 2004-06, David Gadish, Ph.D.
20
Implementing The Job Relation
Structure
 Let’s take a look at the Field Properties for
Job Name.
 Since this is a text field, you have some new
Field Properties to consider.
– Allow Zero Length - if you leave this at Yes,
you’re essentially saying that anyone can enter a
new job but not specify a name (i.e., blank).
© 2004-06, David Gadish, Ph.D.
21
Implementing The Department
Relation Structure
This is the field properties
for Department Name.
Notice that we changed
the Field Size from the
default of 50 to 35.
Always make sure text
fields are large enough to
handle any entry but not
so large that you waste
space.
© 2004-06, David Gadish, Ph.D.
22
Implementing The Department
Relation Structure
 We created the Department relation using
the Design view.
– Department Num = Number
– Department Name = Text
 We also specified that Department Num is
the primary key by placing the key icon
beside its name in the field name list.
© 2004-06, David Gadish, Ph.D.
23
Implementing The Department
Relation Structure
 Let’s take a look at the Field Properties for
Department Name.
 Since this is a text field, the default size (Field
Size) is 50 characters, which we changed to 35.
 The field size for a text field can range from 0 to
255.
© 2004-06, David Gadish, Ph.D.
24
Implementing The Job
Assignment Relation Structure
The Job Assignment
relation is a composite (or
intersection) relation,
meaning that it will have
two fields (Employee ID
and Job Number) making
up the primary key. To
identify more than one
filed as the primary key,
highlight the appropriate
fields and click on the key
icon.
© 2004-06, David Gadish, Ph.D.
25
Implementing The Job
Assignment Relation Structure
 We entered all the field names
– Employee ID = Number
– Job Number = Number
– Hours = Number
 This particular relation is different from
the rest because it has a composite
primary key.
© 2004-06, David Gadish, Ph.D.
26
Implementing The Job
Assignment Relation Structure
 Composite primary key - consists of the primary key fields
from the two intersecting relations.
 We created the Job Assignment relation to eliminate the
many-to-many relationship that existed between the
Employee and Job relations.
 The Job Assignment relation has a primary key composed
of two fields – the primary key Employee ID that
originated in the Employee relation and the primary key
Job Number that originated in the Job relation.
© 2004-06, David Gadish, Ph.D.
27
Defining Relationships Within
Your Employee Database

We have one final structural task to take care of
– that of defining how all the relations relate to
each other.

Foreign key - a primary key of one file
(relation) that appears in another file (relation).
© 2004-06, David Gadish, Ph.D.
28
Defining Relationships Within
Your Employee Database
To define relationships in a
database, you must first
click on the Relationships
button.
When you first start this
process, the Relationships
palette will be blank. As
you highlight each relation
and click on the Add button
in the Show Table box,
the relations will appear on
the palette.
© 2004-06, David Gadish, Ph.D.
29
Defining Relationships Within
Your Employee Database
 To create these relationships, you click on the
Relationships button in the button bar.
 To identify the relationships, you must make each relation
appear on the palette.
 To do this, simply highlight each relation name and click
on Add, which is what we did.
 We then clicked on the Close button to make the Show
Table box disappear.
© 2004-06, David Gadish, Ph.D.
30
Defining Relationships Within
Your Employee Database
Drag and drop primary keys
onto foreign keys. This will
create a one-to-many
relationship. The “many” is
denoted by the infinity
symbol.
Enforce referential integrity
by clicking here.
© 2004-06, David Gadish, Ph.D.
31
Defining Relationships Within
Your Employee Database
 Click on and drag each primary key and drop it
onto its respective foreign key counterpart.
 Once you drop the primary key onto its respective
foreign key counterpart, you’ll see the Edit
Relationships box.
 In that box, you need to click on Enforce
Referential Integrity and then Create.
© 2004-06, David Gadish, Ph.D.
32
Entering Information Into Your
Employee Database
 To enter information, you simply highlight
the desired relation and click on Open.
© 2004-06, David Gadish, Ph.D.
33
Entering Information Into Your
Employee Database
To enter information,
highlight the appropriate
relation and click on Open.
© 2004-06, David Gadish, Ph.D.
34
Entering Information Into Your
Employee Database
When you begin entering
information, your database
will look very much like a
spreadsheet with rows and
columns.
© 2004-06, David Gadish, Ph.D.
35
Entering Information Into Your
Employee Database
After you enter all the
information, click on the
Disk icon to save it.
© 2004-06, David Gadish, Ph.D.
36
Creating a Simple Query Using
One Relation
 Query-by-example (QBE) tool - helps you
graphically design the answer to a question.
 Suppose, for example, that we wanted to
see a list of all employees by Employee ID
and by Name.
© 2004-06, David Gadish, Ph.D.
37
Creating a Simple Query Using
One Relation
To create a query, select
the Queries tab and
double-click on Create
query in Design view.
© 2004-06, David Gadish, Ph.D.
38
Creating a Simple Query Using
One Relation
Then, select the
appropriate relations by
highlighting each of them
individually and clicking on
the Add button.
This is the QBE grid.
© 2004-06, David Gadish, Ph.D.
39
Creating a Simple Query Using
One Relation
Since all the query
information we need is in
the Employee relation, it’s
the only relation we added.
© 2004-06, David Gadish, Ph.D.
40
Creating a Simple Query Using
One Relation
Next, we dragged and
dropped Employee ID and
Name from the Employee
relation into the QBE grid.
© 2004-06, David Gadish, Ph.D.
41
Creating a Simple Query Using
One Relation
After clicking on the
exclamation point icon
(Run), Access provided us
with this result of our query.
© 2004-06, David Gadish, Ph.D.
42
Creating a Simple Query Using
One Relation
 Let’s assume that we wanted to see all
employees by ID and name who are in the
Residential department (Department Num
is 43).
 We often refer to this as a conditional
query because it only returns results based
on some condition.
© 2004-06, David Gadish, Ph.D.
43
Creating a Simple Query Using
One Relation
To create a condition
query, we added
Department Num from the
Employee relation and
specified “=43” in the
Criteria field.
© 2004-06, David Gadish, Ph.D.
44
Creating a Simple Query Using
One Relation
The result of this query
shows only employees in
department 43.
© 2004-06, David Gadish, Ph.D.
45
Creating An Advanced Query Using
More Than One Relation

Suppose we wanted a list of all employees by ID,
name, and the department in which they work.
However, instead of Department Num as the
identifier for the department, we would like to see
Department Name.

That query will require the use of two relations
because Employee ID and Name are in the
Employee relation and Department Name is in the
Department relation.
© 2004-06, David Gadish, Ph.D.
46
Creating An Advanced Query
Using More Than One Relation
To show employees by ID,
name, and department
name, we added both the
Employee and Department
relations to the query.
© 2004-06, David Gadish, Ph.D.
47
Creating An Advanced Query Using
More Than One Relation
We then dragged and
dropped Employee ID and
Name from the Employee
relation and Department
Name from the Department
relation into the QBE grid.
© 2004-06, David Gadish, Ph.D.
48
Creating An Advanced Query Using
More Than One Relation
The result of that query
show employee information
including Department
Name, not Department
Num.
© 2004-06, David Gadish, Ph.D.
49
Creating An Advanced Query Using
More Than One Relation
 As a final query example, let’s consider that
we would like to see all The IDs and names
of employees who work in the Residential
Department (Department Num is 43) who
work more than four (4) hours in Sales (Job
Number is 23) and how many hours they
work in Sales.
© 2004-06, David Gadish, Ph.D.
50
Creating An Advanced Query Using
More Than One Relation
 To perform this query, we still only need
two relations, this time Employee and Job
Assignment.
1.
2.
3.
4.
5.
Employee ID from Employee
Name from Employee
Department Num from Employee
Job Number from Job Assignment
Hours from Job Assignment
© 2004-06, David Gadish, Ph.D.
51
Creating An Advanced Query Using
More Than One Relation
To show employees in
department 43 who are
assigned to job 23 for more
than 4 hours, we added
both the Employee and Job
Assignment relations to this
query.
© 2004-06, David Gadish, Ph.D.
52
Creating An Advanced Query Using
More Than One Relation
We then dragged and
dropped the necessary
information into the QBE
grid and specified the
appropriate information in
the Criteria fields.
© 2004-06, David Gadish, Ph.D.
53
Creating An Advanced Query Using
More Than One Relation
The result shows only two
employees.
© 2004-06, David Gadish, Ph.D.
54
Generating A Report
 To create this report, follow these steps:
1. Select the Reports tab.
2. Double click on Create report by using wizard.
3. Under Tables/Queries, select Table: Employee.
4. Under Available Fields, select Employee ID and click
on the greater than sign (>) to the right and select Name
and click on the greater than sign (>) to the right.
5. Under Tables/Queries, select Table: Department.
6. Under Available Fields, select Department Name and
click on the greater than sign (>) to the right.
© 2004-06, David Gadish, Ph.D.
55
Generating A Report
7.
8.
9.
10.
11.
12.
13.
Click on Next>.
Click on Next>. (Allows you to choose ordering of information
presentation.)
Click on Next>. (Allows you to specify grouping of
information.)
Click on Next>. (Allows you to specify sorting of information.)
Click on Next>. (Allows you to select layout and page
orientation).
Click on Next>. (Allows you to choose from among predefined
reports styles).
Enter “Employee Report” (without the quote marks) for the title
and click on Finish.
© 2004-06, David Gadish, Ph.D.
56
Generating A Report
To create a report,
select the Reports tab
and double-click on
Create report by
using wizard.
© 2004-06, David Gadish, Ph.D.
57
Generating A Report
Once you select a
table (relation), you
will see the list of
fields in it. You add
fields to a report by
highlighting them and
then clicking on the
greater than sign (>)
button.
© 2004-06, David Gadish, Ph.D.
58
Generating A Report
For our report, we
included Employee ID
and Name from the
Employee relation.
© 2004-06, David Gadish, Ph.D.
59
Generating A Report
We then selected the
Department relation to
add more information
to the report.
© 2004-06, David Gadish, Ph.D.
60
Generating A Report
From the Department
relation we chose to
add Department Name
to the report.
© 2004-06, David Gadish, Ph.D.
61
Generating A Report
After accepting several
default report options, we
chose Employee Report
as the name of the
report.
© 2004-06, David Gadish, Ph.D.
62
Generating A Report
The report shows all
employees by ID, name,
and department name.
© 2004-06, David Gadish, Ph.D.
63
Emerging Trends and
Technologies - Business, People,
and Technology tomorrow
Chapter 9
64
Introduction
 Technology is changing everyday.
 How new technologies will change the
things that you do, both from a personal
and organizational perspective?
© 2004-06, David Gadish, Ph.D.
65
Introduction
© 2004-06, David Gadish, Ph.D.
66
The Need For Information Filtering
Push, Not Pull Technologies
 In a pull technology environment you request and
find what information you want.
 Push technology – an environment in which
businesses and organizations come to you with
information, services, and product offerings based
on your profile.
© 2004-06, David Gadish, Ph.D.
67
The Need For Information Filtering
Push, Not Pull Technologies
© 2004-06, David Gadish, Ph.D.
68
The Need For Information Filtering
Information Supplier Convergence
 Information suppliers include businesses that provide you
with magazines, newspapers, Internet access, telephone
service, cable TV, books, and the like.
 If you receive your newspaper from the same company
that supplies your Internet access you are experiencing
supplier convergence.
 You’ll notice a greater ability to filter information when
you start to enjoy the convergence of information
suppliers. Is that a good thing???
© 2004-06, David Gadish, Ph.D.
69
The Movement Toward
Intellectual Computing
Automatic Speech Understanding
 Automatic speech recognition has come a
long way in the past several years, but it
still has a long way to go.
 If we someday create intelligent software,
then speech recognition will become speech
understanding.
© 2004-06, David Gadish, Ph.D.
70
The Movement Toward
Intellectual Computing
People Will Still Make The Decisions
 Regardless of how intelligent a
computer system may become, it will
never completely replace people in all
aspects of decision making.
© 2004-06, David Gadish, Ph.D.
71
The Changing Of Physiological
Interaction
 Biometrics - the use of your physical
characteristics – such as your fingerprint,
the blood vessels in the retina of your
eye, the sound of your voice, or perhaps
even your breath – to provide
identification.
© 2004-06, David Gadish, Ph.D.
72
The Changing Of Physiological
Interaction
Automatic Speech Recognition
 Automatic speech recognition (ASR) – a system
that not only captures spoken words but also
distinguishes word groupings to form sentences.
 An ASR system follows three steps.
1. Feature analysis - the system captures your words as
you speak into a microphone, eliminates any
background noise, and converts the digital signals of
your speech into phonemes (syllables).
© 2004-06, David Gadish, Ph.D.
73
The Changing Of Physiological
Interaction
Automatic Speech Recognition
2. Pattern classification - the system matches your
spoken phonemes to a phoneme sequence stored
in an acoustic model database.
3. Language processing - the system attempts to
make sense of what you’re saying by comparing
the word phonemes generated in step 2 with a
language model database.
© 2004-06, David Gadish, Ph.D.
74
The Changing Of Physiological
Interaction
Virtual Reality
 Virtual reality – a three-dimensional
computer simulation in which you
actively and physically participate.
– Glove – an input device that captures and
records the shape and movement of your
hand and fingers and the strength of your
hand and finger movements.
© 2004-06, David Gadish, Ph.D.
75
The Changing Of Physiological
Interaction
Virtual Reality
– Headset – a combined input and output device
that (1) captures and records the movement of
your head and (2) contains a screen that covers
your entire field of vision and displays various
views of an environment based on your
movements.
– Walker – an input device that captures and
records the movement of your feet as you walk
or turn in different directions.
© 2004-06, David Gadish, Ph.D.
76
The Changing Of Physiological
Interaction
Cave Automatic Virtual Environment
 CAVE (cave automatic virtual environment) - a
special 3-D virtual reality room that can display
images of other people and objects located in
other CAVEs all over the world.
 Holographic devices – devices that create,
capture, and/or display images in true threedimensional form.
© 2004-06, David Gadish, Ph.D.
77
The Changing Of Physiological
Interaction
Cave Automatic Virtual Environment
© 2004-06, David Gadish, Ph.D.
78
Increasing Portability and
Mobility
 Portability refers to how easy it is for you
to carry around your technology.
 Mobility encompasses what you have the
ability to do with your technology while
carrying it around.
© 2004-06, David Gadish, Ph.D.
79
Increasing Portability and Mobility
Free Internet Phone Calls
© 2004-06, David Gadish, Ph.D.
80
Increasing Portability and
Mobility
Micro-Payments and Financial
Cybermediaries
 Micro-payments - techniques to facilitate
the exchange of small amounts of money
for an Internet transaction.
 Financial cybermediaries - Internet-based
companies that make it easy for one person
to pay another person over the Internet.
© 2004-06, David Gadish, Ph.D.
81
Increasing Portability and
Mobility
Wearable Computers
 Wearable computer - a fully-equipped computer
that you wear as a piece of clothing or attached
to a piece of clothing similar to way you would
carry your cell phone on your belt.
© 2004-06, David Gadish, Ph.D.
82
Increasing Portability and
Mobility
Wearable Computers
© 2004-06, David Gadish, Ph.D.
83
Increasing Portability and
Mobility
Implant Chips
 Implant chip - a technology-enabled
microchip implanted into the human
body. Implant chips server two
functions:
1. Contains memory which stores important
information about you.
2. Many of these chips are GPS-enabled.
© 2004-06, David Gadish, Ph.D.
84
Increasing Portability and
Mobility
Implant Chips
 Global positioning system (GPS) - a
collection of 24 earth-orbiting satellites that
continuously transmit radio signals to
determine your current longitude, latitude,
speed, and direction of movement.
© 2004-06, David Gadish, Ph.D.
85
The Digital Frontier
 Digital economy – marked by the electronic movement of
all types of information, not limited to numbers, words,
graphs, and photos but including physiological information
such as voice recognition and synthesization, biometrics
(your retina scan and breath for example), and 3-D
holograms.
 Last-mile bottleneck problem - occurs when information is
traveling on the Internet over a very fast line for a certain
distance and then comes near your home where it must
travel over a slower line.
© 2004-06, David Gadish, Ph.D.
86
The Digital Frontier
Digital Cash
 Digital cash (also called electronic cash or e-
cash) - an electronic representation of cash.
© 2004-06, David Gadish, Ph.D.
87
The Rebirth of E-Commerce
Broadening of E-Government
There are four primary focuses in the e-government arena.
1. Government-to-Government (G2G) – performing
electronic commerce activities within a single nation’s
government focusing on vertical integration and
horizontal integration.
2. Government-to-Business (G2B) – the electronic
commerce activities performed between a government
and its business partners for such purposes as
purchasing direct and indirect materials, soliciting bids
for work, and accepting bids for work.
© 2004-06, David Gadish, Ph.D.
88
The Rebirth of E-Commerce
Broadening of E-Government
3. Government-to-Consumer (G2C) – the
electronic commerce activities performed
between a government and its citizens or
consumers including paying taxes, registering
vehicles, and providing information and services.
4. International Government-to-Government
(IG2G) – the electronic commerce activities
performed between two or more governments
including providing foreign aid.
© 2004-06, David Gadish, Ph.D.
89
The Rebirth of E-Commerce
Broadening of E-Government
© 2004-06, David Gadish, Ph.D.
90
The Rebirth of E-Commerce
Explosion of C2C E-Commerce
 Of all the types of private-sector ecommerce activities – B2B, B2C, C2C, and
C2B – the least amount of revenue dollars
right now is in the C2C (consumer-toconsumer) space.
 Expected to change dramatically in the next
several years.
© 2004-06, David Gadish, Ph.D.
91
The Most Important
Considerations
The Necessity of Technology
 Technology is a necessity today.
 It’s hard to imagine a world without
technology.
 Just as we need electricity to function on an
everyday basis, we need technology as well.
© 2004-06, David Gadish, Ph.D.
92
The Most Important
Considerations
Closing the Great Digital Divide
 The power of technology needs to be
realized on a worldwide scale.
 We cannot afford to have any technology-
challenged nation or culture (within reason).
© 2004-06, David Gadish, Ph.D.
93
The Most Important
Considerations
Technology for the Betterment of People and
Society
 As you approach the development and use
of technological innovations (or even
standard technologies), think in terms of
the betterment of people and society in
general.
© 2004-06, David Gadish, Ph.D.
94
The Most Important
Considerations
Exchanging Privacy for Convenience
 You need to consider how much of your
personal privacy you’re giving up in
exchange for convenience.
 Everyday you’re giving up just a little more
privacy in exchange for a little more
convenience.
© 2004-06, David Gadish, Ph.D.
95
The Most Important
Considerations
Ethics, Ethics, Ethics
 Ethics guide your behavior that affects
other people.
 You can be very ethical and very
successful.
© 2004-06, David Gadish, Ph.D.
96
Questions?
© 2004-06, David Gadish, Ph.D.
97
Next Week’s Agenda
 Final Exam
© 2004-06, David Gadish, Ph.D.
98