Systems Analysis & Design
Phase Description
5th Edition
Chapter 6
Data Design
Chapter Objectives
● Explain data design concepts and data
structures
● Describe file processing systems and
various types of files
● Understand database systems and define
the components of a database
management system (DBMS)
● Describe Web-based data design and
characteristics
3 4
Chapter Objectives
● Describe hierarchical, network,
relational, and object-oriented database
models
● Explain data warehousing/data mining
● Differentiate between logical and
physical storage and records
● Explain data control measures
5 6
● Systems Design is the third of five
phases in the systems development life
cycle (SDLC)
● Now you are ready to begin the physical
design of the system that will meet the
specifications described in the system
requirements document
● Systems design tasks include data
design, user interface design, and
system architecture
2
Chapter Objectives
● Explain data design terminology,
including entities, fields, common fields,
records, files, tables, and key fields
● Describe data relationships, draw an
entity-relationship diagram, define
cardinality and use cardinality notation
● Explain the concept of normalization
● Understand the steps in database
design
Introduction
● You will develop a physical plan for data
organization, storage, and retrieval
● Begins with a review of data design
concepts and terminology, then discusses
file-based systems and database systems,
including Web-based databases
● Concludes with a discussion of data
mining, data warehousing, physical
design issues, logical and physical
records, data storage formats, and data
controls
Data Design Concepts Data Design Concepts
● Before constructing an information ● Data Structures
system, a systems analyst must –A file or table contains data about people, places or
understand basic design concepts, events that interact with the system
including data structures and the –File-oriented system
characteristics of file-oriented and –File processing
database systems, including Web-based –Database system
database design

7 8

Data Design Concepts Data Design Concepts

● Overview of File Processing ● Overview of File Processing
–Some companies use file processing to handle – Potential problems
large volumes of structured data • Data redundancy
• Data integrity
–Although less common today, file processing can be • Rigid data structure
more efficient and cost less than a DBMS in certain
– Uses various types of files
situations • Master file
• Table file
• Transaction file
• Work file – scratch file
• Security file
• History file

9 10

Data Design Concepts Data Design Concepts

● Overview of Database Systems ● Overview of Database Systems

– A properly designed database system offers a
solution to the problems of file processing
– Provides an overall framework that avoids data
redundancy and supports a real-time, dynamic
environment

11 12
Data Design Concepts Data Design Concepts
● Overview of Database Systems ● Overview of Database Systems
– A database management system (DBMS) is a – Advantages
collection of tools, features, and interfaces that • Scalability
enables users to add, update, manage, access, • Better support for client/server systems
• Economy of scale
and analyze the contents of a database
• Flexible data sharing
– The main advantage of a DBMS is that it offers • Enterprise-wide application – database administrator
timely, interactive, and flexible data access (DBA)
• Stronger standards
• Controlled redundancy
• Better security
• Increased programmer productivity
• Data independence

13 14

Data Design Concepts DBMS Components

● Database Tradeoffs ● A DBMS provides an interface between a
– Because DBMSs are powerful, they require database and users who need to access the
more expensive hardware, software, and data data
networks capable of supporting a multiuser
environment
– More complex than a file processing system
– Procedures for security, backup, and recovery
are more complicated and critical

15 16

DBMS Components DBMS Components

● Interfaces for Users, Database ● Interfaces for Users, Database

Administrators, and Related Systems Administrators, and Related Systems
– Users – Related information systems
• Query language • A DBMS can support several related information
• Query by example (QBE) systems that provide input to, and require specific
• SQL (structured query language) data from, the DBMS

– Database Administrators ● Data Manipulation Language

• A DBA is responsible for DBMS management and – A data manipulation language (DML) controls
support database operations, including storing,
retrieving, updating, and deleting data

17 18
DBMS Components
● Schema
– The complete definition of a database,
including descriptions of all fields, tables, and
relationships, is called a schema
– You also can define one or more subschemas
● Physical Data Repository
– The data dictionary is transformed into a
physical data repository, which also contains
the schema and subschemas
– The physical repository might be centralized, or
distributed at several locations
Web-Based Database Design
● Characteristics of Web-Based Design
– In a Web-based design, the Internet serves as the
front end, or interface for the database
management system. Internet technology
provides enormous power and flexibility
– Web-based systems are popular because they
offer ease of access, cost-effectiveness, and
worldwide connectivity

19 20

Web-Based Database Design Web-Based Database Design

● Internet Terminology ● Internet Terminology
– Web browser – Extranet
– Web page – Protocols
– HTML – Hypertext Markup Language – Web-centric
– Web server – Clients
– Web site – Servers
– Intranet

21 22

Web-Based Database Design Web-Based Database Design

● Connecting a Database to the Web ● Data Security

– Database must be connected to the Internet or – Web-based data must be totally secure, yet
intranet easily accessible to authorized users
• Middleware – To achieve this goal, well-designed systems
• Macromedia’s ColdFusion provide security at three levels: the database
itself, the Web server, and the
telecommunication links that connect the
components of the system

23 24
Data Design Terminology Data Design Terminology
● Definitions ● Key Fields
–Entity – Primary key
–Table or file • Combination key
• Composite key
–Field
• Concatenated key
• Attribute - Common field • Multi-valued key
–Record – Candidate key
• Tuple • Nonkey field
– Foreign key
– Secondary key

25 26

Data Design Terminology Data Relationships

● Referential Integrity
– Validity checks can help avoid data input errors
– In a relational database, referential integrity
means that a foreign key value cannot be
entered in one table unless it matches an
existing primary key in another table
● A relationship is a logical link between
entities based on how they interact
● Entity-Relationship Diagrams
– One-to-one relationship (1:1)
– One-to-many relationship (1:M)
– Many-to-many relationship (M:N)
– Cardinality
• Cardinality notation
• Crow’s foot notation
• Unified Modeling Language (UML)

27 28

Data Relationships Normalization

● Entity-Relationship Diagrams ● Normalization

● Table design
● Involves four stages: unnormalized
design, first normal form, second
normal form, and third normal form
● Most business-related databases must
be designed in third normal form

29 30
Normalization Normalization
● Standard Notation Format ● Repeating Groups and Unnormalized
– Designing tables is easier if you use a standard Design
notation format to show a table’s structure, –Repeating group
fields, and primary key • Often occur in manual documents prepared by users
–Unnormalized design
Example: NAME (FIELD 1, FIELD 2, FIELD 3)

31 32

Normalization Normalization
● First Normal Form ● Second Normal Form
–A table is in first normal form (1NF) if it does not – To understand second normal form (2NF), you
contain a repeating group must understand the concept of functional
–To convert, you must expand the table’s primary key dependence
to include the primary key of the repeating group – Field X is functionally dependent on field Y if
the value of field X depends on the value of
field Y

33 34

Normalization Normalization

● Second Normal Form ● Second Normal Form

– A standard process exists for converting a
table from 1NF to 2NF
1. Create and name a separate table for each field in
the existing primary key
2. Create a new table for each possible combination
of the original primary key fields
3. Study the three tables and place each field with its
appropriate primary key
– Four kinds of problems are found with 1NF
description that do not exist with 2NF
• Consider the work necessary to change a particular
product’s description
• 1NF tables can contain inconsistent data
• Adding a new product is a problem
• Deleting a product is a problem

35 36
Normalization
● Third Normal Form
–3NF design avoids redundancy and data integrity
problems that still can exist in 2NF designs
–A table design is in third normal form (3NF) if it is in
2NF and if no nonkey field is dependent on another
nonkey field
37
Normalization
● A Normalization Example
– To show the normalization process, consider the
familiar situation in Figure 6-24 which might depict
several entities in a school advising system:
ADVISOR, COURSE, and STUDENT
– The relationships among the three entities are
shown in the ERD in Figure 6-25
39
Database Models
● Hierarchical and Network Databases
– In a hierarchical database, data is organized
like a family tree or organization chart, with
branches representing parent records and child
records
– A network database resembles a hierarchical
design, but provides somewhat more flexibility
41
Normalization
● Third Normal Form
– To convert the table to 3NF, you must remove
all fields from the 2NF table that depend on
another nonkey field and place them in a new
table that uses the nonkey field as a primary
key
38
Steps in Database Design
1. Create the initial ERD
2. Assign all data elements to entities
3. Create 3NF designs for all tables, taking
care to identify all primary, secondary,
and foreign keys
4. Verify all data dictionary entries
● After creating your final ERD and
normalized table designs, you can
transform them into a database
40
Database Models
● Relational Databases
– The relational model was introduced during the
1970s and became popular because it was
flexible and powerful
– Because all the tables are linked, a user can
request data that meets specific conditions
– New entities and attributes can be added at any
time without restructuring the entire database
42
Database Models Data Storage
● Object-Oriented Databases ● Data Warehousing
–Many systems developers are using object-oriented – Data warehouse - dimensions
database (OODB) design as a natural extension of – Without a data warehouse it would be difficult for a
the object-oriented analysis process user to extract data that spans several information
• Object Data Standard systems and time frames
• Object Database Management Group (ODMG)
– Allows users to retrieve and analyze the data
• Each object has a unique object identifier
easily

43 44

Data Storage Data Storage

● Data Mining ● Logical and Physical Storage
– Works best when you have clear, measurable – Logical storage
goals • As seen through a user’s eyes
• Characters
• Increase average pages viewed per session
• Date element or data item
• Increase number of referred customers
• Logical record
• Reduce clicks to close
– Physical storage
• Increase checkouts per visit
• Hardware-related
• Increase average profit per checkout
• Physical record or block
• Blocking factor

45 46

Data Storage Data Storage

● Data Storage Formats ● Data Storage Formats

– Binary digits – Binary
– Bit • Binary storage format
• Integer format
– Byte
• Long integer format
– EBCDIC and ASCII • Other binary formats exist for efficient storage of
– Unicode exceedingly long numbers

47 48
Data Storage
● Selecting a Data Storage Format
– In many cases, a user can select a specific data
storage format
– For example, when using Microsoft Office, you
can store documents, spreadsheets, and
databases in Unicode-compatible form by using
the font called Arial Unicode MS
– Selecting the right data storage format depends
on the situation
Data Storage
● Date Fields
– Most date formats now are based on the model
established by the International Organization for
Standardization (ISO)
– Can be sorted easily and used in comparisons
– Absolute date
– Best method for storing date fields depends on
how the specific date will be printed, displayed or
used in a calculation

49 50

Data Control Data Control

● File and database control must include all ● User ID
measures necessary to ensure that data ● Password
storage is correct, complete, and secure ● Backup
● A well-designed DBMS must provide built- ● Recovery procedures
in control and security features, including
subschemas, passwords, encryption, audit ● Audit log files
trail files, and backup and recovery ● Audit fields
procedures to maintain data ● Encryption

51 52

Chapter Summary Chapter Summary

● Files and tables contain data about people,
places, things, or events that affect the
information system
● DBMS designs are more powerful and
flexible than traditional file-oriented
systems
● Data design tasks include creating an
initial ERD; assigning data elements to an
entity; normalizing all table designs; and
completing the data dictionary entries for
files, records, and data elements
● The four basic database models are
hierarchical, network, relational, and
object-oriented

53 54
 Systems Analysis & Design
Chapter Summary
5th Edition
● Logical storage is information seen
through a user’s eyes, regardless of how
or where that information actually is
organized or stored Chapter 6 Complete
● Physical storage is hardware-related and
involves reading and writing blocks of
binary data to physical media
● File and database control measures
include limiting access to the data, data
encryption, backup/recovery procedures,
audit-trail files, and internal audit fields
55