ESBI

NCC Education Limited
V1.0
Enterprise Software and
Business Infrastructure
Week 3 Reference Models and
Business Architectures
Reference Models and Business Architecture Part 2 Lecture 3 - 3.2
V1.0
Objectives
Define database systems
Introduce data modeling and SQL
Discuss emerging requirements of
database systems
Introduce enterprise system architecture
Discuss system landscape
V1.0
Enterprise Systems And Data
Enterprise system = business processes +
state of an enterprise
Programs define and implement the
process
Data define the processes
Process without data are empty shells
V1.0
Enterprise Systems And Data
Data management technology is key to
enable enterprise systems
The data must be managed as a whole,
flexible enough to be shared and changed
without a major overhaul of the system, and
capable of expressing complex
relationships and interactions.
V1.0
Database Fundamentals
Attributes of data
Sharable
Moveable
Secure
Accurate
Timely
Relevant
V1.0
Database Fundamentals
Data hierarchy
Bits
Characters
Fields (columns)
Records (rows)
Files (table)
Database
V1.0
Why Build A Database?
Manage large amounts of data
Serve multiple users
Make information retrieval faster
Make data input faster
Provide greater accuracy
V1.0
Database Versus Database
Management System (DBMS)
A Database is a collection of integrated files
A DBMS is a complex computer program
that supervises the transfer of data between
the end user and the database
V1.0
Advantages Of DBMS
Reduction of data duplication
Improved data integrity
Programs are independent of the data
format
Sharing of data resources
V1.0
Disadvantages of DBMS
Expensive
More hardware may be needed
Design and programming skills required
Additional training needs
Security is critical to control access to data
V1.0
Relational Model
Relational model structured around:
Attributes data fields
Rows/Tuples collection of data fields
Tables collection of rows
A relational model will store a single piece of
information only once in a database
Each row in a database must have a attribute or
group of attributes that uniquely identifies it key
Relationships established between tables by
including a key of one table as a foreign key in
another table
V1.0
Relational DB Rules
Every row must have exactly the same
number of columns (fields or attributes)
Each row can have only one value stored in
each column (fields or attributes)
A column must contain the same kind of
value in every row of that column
No two rows can be exactly the same
V1.0
Terminology
Data
Processing
Informal
Relational DB
Formal
Relational DB
File Table
Relation
Record Row
Tuple
Field Column
Attribute
V1.0
Data Modelling
The purpose of data modelling is to control
and manage large volumes of data. It
involves gathering requirements and the
result is forms and diagrams
V1.0
Normalisation
The purpose of normalisation is to avoid
anomalies and reduce data redundancy
The process of normalisation involves the
successive application of rules moving from
first through to fifth normal form.
V1.0
Cust
ID Cust Name Street City Out In County Post Code Film Name
1 John Smith 123 Any Street Anytown 05/05/1985 03/06/1985 Anywhere AN1 2YY Bambi
2 Sarah Sugden 321Any Street Anytown 03/06/1985 04/08/1985 Anywhere AN1 2YY Ice Age
3 John Smith 123 Any Street Anytown 27/03/1986 26/04/1986 Anywhere AN1 2YY Jungle Book
4 Sarah Sugden 321Any Street Anytown 03/04/1984 05/02/1985 Anywhere AN1 2YY ET
5 John Smith 123 Any Street Anytown 07/06/1985 08/10/1985 Anywhere AN1 2YY Shrek
6 Sarah Sugden 321Any Street Anytown 02/09/1986 08/03/1986 Anywhere AN1 2YY Toy Story
7 John Smith 123 Any Street Anytown 03/02/1987 14/04/1987 Anywhere AN1 2YY Madagascar
Cust
ID Cust Name Street City County
Post
Code
4
Sarah
Sugden
321Any
Street Anytown
Anywher
e AN1 2YY
5 John Smith
123 Any
Street Anytown
Anywher
e AN1 2YY
Cust ID Film ID Out In
6 34 03/04/1984 05/02/1985
3 12 07/06/1985 08/10/1985
8 87 03/02/1987 14/04/1987
V1.0
Entity Relationship Modeling
This involves listing the entities (data
objects) in the environment
The purpose of ERM is to describe the
relationship between entities
A single row in table A can be related to how
many rows in table B (one or many)
A single row in table B can be related to how
many rows in table A (one or many)
V1.0
Customer
Cust ID
Name
Street
City
County
Post Code
Rental
Date Out
Returned
Film
Film Name
Number in Stock
Actor
Actor ID
Actor Name
V1.0
Structured Query Language (SQL)
SQL allows queries of relational databases
Example SQL commands:
Definition (Data Definition Language)
CREATE, ALTER, DROP
Manipulation (Data Manipulation Language)
SELECT, INSERT, UPDATE, DELETE
V1.0
General Format Of SELECT
SELECT [ DI STI NCT] i t em( s)
FROM t abl e( s)
[ WHERE condi t i on]
[ GROUP BY col umns]
[ HAVI NG condi t i on]
[ ORDER BY r ow( s) ]
V1.0
Emerging Data Requirements
Current RDBMS
Complex
Simple
Unstructured Structured
Audio Streams
Images
Video Streams
Text
Graphics
Audio
Spatial Data
Time Series
HTML/
SGML
Video
V1.0
Enterprise System Architecture
to understand enterprise systems, examine
on 2 dimensions:
logical architecture that defines the components
and functionalities supported by the systems
physical architecture that defines how specific
components are implemented
V1.0
Logical Architecture
enterprise
structure
&
environment
data
end users
applications
operational
data
ACCOUNTING
SALES &
DISTRIBUTION
PRODUCTION
HR
V1.0
Physical Architecture
Typical enterprise system uses the tiered
client-server architecture
Usually layers are implemented on a
different computer or cluster of computers -
scalability
V1.0
Tiered Configurations
Application
Database
Presentation
Database, application,
presentation processes
Central system Two-tier Three-tier
Presentation
processes
Database,
application
processes
Database processes
Application processes
Presentation processes
V1.0
Enterprise System Scalability
Scalability
Application
Database
Presentation
V1.0
Master
Data
Organizational
structure
Programs
Log files
Database server
Database Layer
Contains Most Objects
Data dictionary
Transaction
Data
Application servers
V1.0
Application Layer:
Application server
Database server
Dispatcher
W
o
r
k
P
r
o
c
e
s
s
W
o
r
k
P
r
o
c
e
s
s
W
o
r
k
P
r
o
c
e
s
s
V1.0
Application Servers:
Contain Work Processes
Dispatcher
W
o
r
k
P
r
o
c
e
s
s
W
o
r
k
P
r
o
c
e
s
s
W
o
r
k
P
r
o
c
e
s
s
Work process can be:
Dialog
Batch
Update
Spool
Message
Gateway
Messages Server:
Coordinates message exchanges between different application servers
Gateway Server:
Allows the communication between R2, R3, and external systems
V1.0
Presentation Layer
Provides the interface between users
and applications
Little processing at presentation layer so
front-end clients do not have to be very
powerful
V1.0
Transport Management
Attempt to isolate production system from
development, testing, and training systems
Changes done on separate system and
incorporated into production system when
changes tested.
Transport directory stores all change requests
V1.0
Transport Management
Version management
Import changes in an
orderly manner
Apply changes
consistently
Development
Transport Directory
(FIFO Buffer)
release
apply
release
release
apply
apply
Test
Quality test
user training
Production
V1.0
Summary
Defined of database systems
Introduced data modeling and SQL
Discussed emerging requirements of
database systems
Introduced enterprise system architecture
Discussed transport management
V1.0

ESBI

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ESBI

Uploaded by

Copyright:

Available Formats

NCC Education Limited

You might also like