Documente Academic
Documente Profesional
Documente Cultură
2008.09.02 - SLIDE 1
IS 257 - Fall 2008
Lecture Outline
Review
Database Life Cycle
Information Systems Planning
Information Systems Architecture
Information Engineering
Database Design
Dive Shop DB in Access
2008.09.02 - SLIDE 2
IS 257 - Fall 2008
Lecture Outline
Review
Database Life Cycle
Information Systems Planning
Information Systems Architecture
Information Engineering
Database Design
Dive Shop DB in Access
2008.09.02 - SLIDE 3
IS 257 - Fall 2008
Database System Life Cycle
Physical
Creation
2
Design Conversion
1 3
Growth,
Change, & Integration
Maintenance
4
6
Operations
5
2008.09.02 - SLIDE 4
IS 257 - Fall 2008
The Cascade View
Project
Identifcation
and Selection
Project
Initiation
and Planning
Analysis
Logical
Design
Physical
Design
Implementation
Maintenance
See Hoffer, p. 41
2008.09.02 - SLIDE 5
IS 257 - Fall 2008
Another View of the Life Cycle
Integration
4 Operations
5
Design
Physical
1
Creation Conversion Growth,
2 3 Change
6
2008.09.02 - SLIDE 6
IS 257 - Fall 2008
Lecture Outline
Review
Database Life Cycle
Information Systems Planning
Information Systems Architecture
Information Engineering
Database Design
Dive Shop DB in Access
2008.09.02 - SLIDE 7
IS 257 - Fall 2008
Information Systems Planning
2008.09.02 - SLIDE 8
IS 257 - Fall 2008
Information Systems
Planning
To support enterprise-wide computing,
there must be enterprise-wide information
planning
One framework for thinking about and
planning for enterprise-wide computing is
an Information Systems Architecture or
ISA
Most organizations do NOT have such an
architecture
2008.09.02 - SLIDE 9
IS 257 - Fall 2008
Lecture Outline
Review
Database Life Cycle
Information Systems Planning
Information Systems Architecture
Information Engineering
Database Design
Dive Shop DB in Access
2008.09.02 - SLIDE 10
IS 257 - Fall 2008
Information Systems Architecture
2008.09.02 - SLIDE 11
IS 257 - Fall 2008
Information Systems Architecture
Benefits of ISA:
Provides a basis for strategic planning of IS
Provides a basis for communicating with top
management and a context for budget decisions
concerning IS
Provides a unifying concept for the various
stakeholders in information systems.
Communicates the overall direction for information
technology and a context for decisions in this area
Helps achieve information integration when systems
are distributed (increasing important in a global
economy)
Provides a basis for evaluating technology options
(for example, downsizing and distributed processing)
Quotes from McFadden (Modern Database Management, 4 th edition), Ch. 3
2008.09.02 - SLIDE 12
IS 257 - Fall 2008
Information Systems Architecture
2008.09.02 - SLIDE 13
IS 257 - Fall 2008
Information Systems Architecture
2008.09.02 - SLIDE 14
IS 257 - Fall 2008
Zachman Framework
2008.09.02 - SLIDE 15
IS 257 - Fall 2008
Information Systems Architecture
1. Enterprise Scope
(Owner)
2008.09.02 - SLIDE 16
IS 257 - Fall 2008
Information Systems Architecture
2. Enterprise Model
(Architect)
2008.09.02 - SLIDE 17
IS 257 - Fall 2008
Information Systems Architecture
2008.09.02 - SLIDE 18
IS 257 - Fall 2008
Information Systems Architecture
5. Technology Definition/
Detailed Representations
(Contractor)
2008.09.02 - SLIDE 20
IS 257 - Fall 2008
Information Systems Architecture
6. Functioning Enterprise
(User)
2008.09.02 - SLIDE 21
IS 257 - Fall 2008
Lecture Outline
Review
Database Life Cycle
Information Systems Planning
Information Systems Architecture
Information Engineering
Database Design
Dive Shop DB in Access
2008.09.02 - SLIDE 22
IS 257 - Fall 2008
Information Engineering
A formal methodology that is used to
create and maintain information systems
Starts with the Business Model and works
in a Top-Down fashion to build supporting
data models and process models for that
business model
2008.09.02 - SLIDE 23
IS 257 - Fall 2008
Information Engineering
Planning
Analysis
1. Identify Strategic Planning
Factors
a. Goals
Design
b. Critical Success Factors 1. Develop Conceptual
c. Problem Areas
2. Identify Corporate Planning
Objects
Model
(detailed E-R Diagram) Implementation
2. Develop Process
a. Org. Units Models
b. Locations (data flow diagrams)
c. Business Functions 1. Design Databases
d. Entity types (normalized relations)
3. Develop Enterprise Model 2. Design Processes
a. Function decomposition a. Action Diagrams 1. Build database definitions
b. Entity-Relationship b. User Interfaces: (tables, indexes, etc.)
Diagram menus, screens, 2. Generate Applications
c. Planning Matrices reports (program code, control
blocks, etc.)
2008.09.02 - SLIDE 24
IS 257 - Fall 2008
Lecture Outline
Review
Database Life Cycle
Information Systems Planning
Information Systems Architecture
Information Engineering
Database Design
Dive Shop DB in Access
2008.09.02 - SLIDE 25
IS 257 - Fall 2008
Database Design Process
2008.09.02 - SLIDE 26
IS 257 - Fall 2008
Stages in Database Design
Requirements formulation and analysis
Conceptual Design -- Conceptual Model
Implementation Design -- Logical Model
Physical Design --Physical Model
2008.09.02 - SLIDE 27
IS 257 - Fall 2008
Database Design Process
Requirements formulation and analysis
Purpose: Identify and describe the data that
are used by the organization
Results: Metadata identified, Data Dictionary,
Conceptual Model-- ER diagram
2008.09.02 - SLIDE 28
IS 257 - Fall 2008
Database Design Process
Requirements Formulation and analysis
Systems Analysis Process
Examine all of the information sources used in
existing applications
Identify the characteristics of each data element
numeric
text
date/time
etc.
Examine the tasks carried out using the information
Examine results or reports created using the
information
2008.09.02 - SLIDE 29
IS 257 - Fall 2008
Database Design Process
Conceptual Model
Merge the collective needs of all applications
Determine what Entities are being used
Some object about which information is to
maintained
What are the Attributes of those entities?
Properties or characteristics of the entity
What attributes uniquely identify the entity
What are the Relationships between entities
How the entities interact with each other?
2008.09.02 - SLIDE 30
IS 257 - Fall 2008
Database Design Process
Logical Model
How is each entity and relationship
represented in the Data Model of the DBMS
Hierarchic?
Network?
Relational?
Object-Oriented?
2008.09.02 - SLIDE 31
IS 257 - Fall 2008
Database Design Process
Physical (AKA Internal) Model
Choices of index file structure
Choices of data storage formats
Choices of disk layout
2008.09.02 - SLIDE 32
IS 257 - Fall 2008
Database Design Process
External Model
User views of the integrated database
Making the old (or updated) applications work
with the new database design
2008.09.02 - SLIDE 33
IS 257 - Fall 2008
Developing a Conceptual Model
2008.09.02 - SLIDE 34
IS 257 - Fall 2008
Entity
An Entity is an object in the real world (or
even imaginary worlds) about which we
want or need to maintain information
Persons (e.g.: customers in a business,
employees, authors)
Things (e.g.: purchase orders, meetings,
parts, companies)
Employee
2008.09.02 - SLIDE 35
IS 257 - Fall 2008
Attributes
Attributes are the significant properties or
characteristics of an entity that help
identify it and provide the information
needed to interact with it or use it. (This is
the Metadata for the entities.)
Birthdate
First Age
Middle Name Employee
SSN
Last Projects
2008.09.02 - SLIDE 36
IS 257 - Fall 2008
Relationships
Relationships are the associations
between entities. They can involve one or
more entities and belong to particular
relationship types
2008.09.02 - SLIDE 37
IS 257 - Fall 2008
Relationships
Project
Supplies
Supplier project Part
parts
2008.09.02 - SLIDE 38
IS 257 - Fall 2008
Types of Relationships
Employee n Assigned
1 Project
Employee m Assigned
n Project
Chen ER notation
2008.09.02 - SLIDE 39
IS 257 - Fall 2008
Other Notations
Crows Foot
2008.09.02 - SLIDE 40
IS 257 - Fall 2008
Other Notations
IDEFIX Notation
2008.09.02 - SLIDE 41
IS 257 - Fall 2008
More Complex Relationships
Manager
1/1/1
4(2-10) 1
Employee Assigned Project
Manages 1
Employee Is Managed By
Manages
n
2008.09.02 - SLIDE 42
IS 257 - Fall 2008
Weak Entities
Owe existence entirely to another entity
Part#
Rep#
2008.09.02 - SLIDE 43
IS 257 - Fall 2008
Supertype and Subtype Entities
Employee Manages
Sold
Other
Invoice
2008.09.02 - SLIDE 44
IS 257 - Fall 2008
Many to Many Relationships
SSN
Project Is
Assigned Project
Assignment
Assigned
Employee SSN
2008.09.02 - SLIDE 45
IS 257 - Fall 2008
Lecture Outline
Review
Database Life Cycle
Information Systems Planning
Information Systems Architecture
Information Engineering
Database Design
Dive Shop DB in Access
2008.09.02 - SLIDE 46
IS 257 - Fall 2008
Database Environment
Repository
DBMS Database
2008.09.02 - SLIDE 47
IS 257 - Fall 2008
Database Components
DBMS
===============
Design tools
Table Creation
Form Creation
Query Creation
Report Creation Application
Procedural
Database language
Programs
compiler (4GL)
=============
Run time
Database contains:
Form processor
Users Data Query processor
User
Metadata Report Writer Interface
Indexes Language Run time Applications
Application Metadata
2008.09.02 - SLIDE 48
IS 257 - Fall 2008
Diveshop in Access
Access is a Microsoft DBMS intended for
personal or lightweight use
For larger scale uses MS has SQL Server
which also CAN use the same interface as
Access
This is because underneath the Access
interface is software that maps to SQL
(more on this later)
2008.09.02 - SLIDE 49
IS 257 - Fall 2008
Access version of Diveshop
Available through the class website
Lab machines have Access loaded
Quick Demo
2008.09.02 - SLIDE 50
IS 257 - Fall 2008
Assignment 1 (also online)
How many tons was the sunken ship Delaware?
What is customer Karen Ngs address?
At what destinations and sites might you find a
Spotted Eagle Ray?
Where (what destination) is the site Palancar Reef?
What sites might Lorraine Vega dive on her trip?
Keith Lucas wants to see a shipwreck on his trip. Is
he going to the right place?
What equipment is Richard Denning getting?
What is the cost of the equipment rental for Louis
Jazdzewski
2008.09.02 - SLIDE 51
IS 257 - Fall 2008
Assignment 1: cont.
The Database is available on the course web
site
Download your own copy (NEW VERSION!)
For each of the questions create a query in
Access
Create a document (Word, etc.) containing
The query being answered
The results of your query cut and pasted from Access
Due date Sept. 7
2008.09.02 - SLIDE 52
IS 257 - Fall 2008
Next Time
THURSDAY:
More on ER modelling
Designing the Conceptual Model for the
Diveshop Database
Using Access for Assignment 1
2008.09.02 - SLIDE 53
IS 257 - Fall 2008