Systems Analysis & Design

10th Edition

Chapter 6

1
Content
 Data design concept
 DBMS component
 Web based database design
 Data design terminology
 Data relationship
 Normalization
 Database models
 Data storage
 Data control
2
Data Design Concepts
 Data Structure
o Framework for organizing and storing
data in an IS
o Consists of linked files/tables

 File processing System

 Database Management System

3
Data Design Concepts

 File Processing System  Database Management

 File-oriented system System

Same data is stored in

more than one place! 4
File Processing System
 Can be more efficient
and cost-effective in
certain situations

 Potential problems
o Data redundancy
o Data integrity
o Rigid data structure

5
File Processing System
 Various types of files
o Master file – permanent data
o Table file – reference data
o Transaction file – day-to-day buss &
op. data
o Work file – temp file for a single task
o Security file – audit trail & backup
o History file – archiving purposes

6
 Database System
Database system –
File processing several system built
system – data around a single
files designed database
to fit individual
business
systems

7
 DBMS Components

complete definition controls database operations

of a database,
including
descriptions of all
fields, tables, and
relationships

View of a database
used by one or more
8
system
DBMS Advantages
 Scalability
 Better support for client/server systems
 Economy of scale
 Flexible data sharing
 Enterprise-wide application – database
administrator (DBA)
 Stronger standards
 Controlled redundancy
 Better security
 Increased programmer productivity
 Data independence
9
DBMS Tradeoffs
 Require more expensive hardware,
software, and data networks capable
of supporting a multi-user environment

 More complex than a file processing

system

 Procedures for security, backup, and

recovery are more complicated and
critical

10
Physical Data
Repository
 data dictionary  physical data
repository,
 schema and subschema
 centralized, or distributed
 ODBC compliant software – enables
communication between systems &
DBMS
 ODBC – open database connectivity
 JDBC – Java database connectivity

11
Web-Based Database
Design

12
Internet Terminology
 Web browser
 Web page
 HTML (Hypertext Markup Language)
 Tags
 Web server
 Web site

13
Internet Terminology
 Intranet
 Extranet
 Protocols
 Web-centric
 Clients
 Servers

14
Connecting a Database
to the Web

Translate client requests in HTML 

executable DB commands  HTML form
15
Data Security

 Secure, yet easily accessible to

authorized users

 Provide security at three levels:

 Database
 Web server
 Telecommunication links that connect
the components of the system

16
Data Design
Terminology
 Entity
 Table or file
 Field
 Attribute
 Common field
 Record
 Tuple
17
Data Design
Terminology
Primary key
Combination key
o

o Composite key
o Concatenated key
o Multi-valued key

• Candidate key
o Nonkey field

• Foreign key
• Secondary key
• Referential Integrity

18
Entity-Relationship
Diagrams
Types of Relationships
o One-to-one relationship (1:1)
o One-to-many relationship (1:M)
o Many-to-many relationship (M:N)
Associative entity

19
ERD - Cardinality

20
 Codes
 A set of letters or numbers representing a data item

 Advantage:
• Reduce …..
storage space
costs

transmission time
data entry time
data input errors

21
Types of Codes
1. Sequence codes
2. Block sequence codes
3. Alphabetic codes
4. Significant digit codes
5. Derivation codes
6. Cipher codes
7. Action codes

22
Types of Codes

Sequence codes
 No additional information
 Order of entry
 Eg. Employee number

Block sequence codes

 Number blocks for classification
 Eg. Course code

23
Types of Codes

Alphabetic codes Significant digit

 Alphabet letters codes
 Category  Series of subgroups
or digits
 NG Nasi Goreng, NL
Nasi Lemak  Eg. Postcode,
Inventory location
 Abbreviation
code
(mnemonic)
 KUL Kuala Lumpur,
BKK Bangkok

24
Types of Codes
Derivation codes
 Data combined from different item attributes
 Eg. Magazine subscriber code

Cipher codes
 Keyword to encode a number
 Eg. Wholesale price

Action codes
 Action associated with an item
 Eg. D – Display, A – Add, X - Exit

25
Developing a Code
 Keep codes concise
 Allow for expansion
 Keep codes stable
 Make codes unique
 Use sortable codes
 Avoid confusing codes (5Z081? 5ZO81? 52081?
S2OB1?)
 Make codes meaningful
 Use a code for a single purpose
 Keep codes consistent

26
Steps in Database
Design
1. Create the initial ERD
2. Assign all data elements to entities
3. Create 3NF designs for all tables
4. Verify all data dictionary entries

27
Database Models

Relational Databases
 1970s
 flexible and powerful

Object-Oriented Databases
 Object-oriented database (OODB) design
as a natural extension of the object-
oriented analysis process
 Each object has object identifier

28
Data Storage and
Access
 Tools- Manage data for business
operations & decisions

 Strategic tools for data storage and

access
o Data warehouse
o Data mining

29
 Data Warehouse
 Integrated collection of data that can include unrelated
information, no matter what is stored in the company

 Links various IS and databases

 Eg. Identify the customer on sales order 34071

 Retrieve from order processing system

 But what about …..

Get the May 2007 sales results for Sally Brown, the sales rep
assigned to Jo-Mar Industries

30
 Data Warehouse

Easy, flexible access for users to obtain information

31
Data Mining

 Data mining software looks for

meaningful patterns and
relationships among data.

 Eg.Identify potential customers

based on prior purchases

32
Logical & Physical
Storage
Logical storage
 Information seen through user’s
eyes

Physical storage
 Involves the process of
reading/writing binary data to
physical media
33
Data Storage Format

 Binary digits
 Bit
 Byte
 EBCDIC and ASCII
 Unicode - internationalize

34
Data Storage and
Access
 International Organization for
Standardization (ISO) – YYYYMMDD

 Sorting and comparison

 Store as 20080922 instead as 22092008

 Absolute date
 Total number of days from specific base date
 Eg. Base date – 1st January 1900
35
Data Control
 User ID
 Password
 Permissions
 Encryption
 Backup
 Recovery procedures
 Audit log files
 Audit fields
36