Transcript Lecture 25.ppt

Lecture 25
COMSATS Islamabad
Enterprise
Systems
Development
( CSC447)
Muhammad Usman, Assistant Professor
Service-oriented design: design sub-steps
Service oriented
analysis
step 1
Compose SOA
Service oriented
design
...
step 2
Design entity-centric
business services
step 3
Design infrastructure services
step 4
Design task-centric
business services
step 5
Design SO
business process
7
Entity-centric business services
Goal:
entity-centric business service layer + parent
orchestration layer
Invoice
Customer
Hours billed
Order
1 PO
*
*
*
1
*
1
Receive PO document
<<include>>
...
Validate PO document
*
1
1 Employee
*
Email
Weekly hours
...
1
*
1 Customer
1
PO processing
service
<<include>>
...
(If PO document is invalid,)
send rejection notification
(and end process)
Transform PO document
into native
electronic PO format
...
8
Infrastructure services
PO
processing
service
Verify
PO
service
Orchestration/coordination
layer
PO
service
Business service layer
Notification
service
Transform
service
Infrastructure service
layer
9
Task-centric business services
 UML sequence diagram
 express
and refine order of invocations
implicit in the UML use case diagram
Receive PO document
<<include>>
Validate PO document
PO processing
service
<<include>>
...
(If PO document is invalid,)
send rejection notification
(and end process)
Verify PO
service
PO
service
Notification
service
get_PO
[PO data]
verify
send_reject
Transform PO document
into native
electronic PO format
10
DATABASE DESIGN
Database Management System (DBMS)
 DBMS contains information about a particular enterprise

Collection of interrelated data

Set of programs to access the data

An environment that is both convenient and efficient to use
 Database Applications:

Banking: all transactions

Airlines: reservations, schedules

Universities: registration, grades

Sales: customers, products, purchases

Online retailers: order tracking, customized recommendations

Manufacturing: production, inventory, orders, supply chain

Human resources: employee records, salaries, tax deductions
 Databases touch all aspects of our lives
Purpose of Database Systems
 In the early days, database applications were built directly on top of
file systems
 Drawbacks of using file systems to store data:

Data redundancy and inconsistency


Multiple file formats, duplication of information in different files
Difficulty in accessing data

Need to write a new program to carry out each new task

Data isolation — multiple files and formats

Integrity problems

Integrity constraints (e.g. account balance > 0) become
“buried” in program code rather than being stated explicitly

Hard to add new constraints or change existing ones
Purpose of Database Systems (Cont.)
 Drawbacks of using file systems (cont.)

Atomicity of updates
 Failures may leave database in an inconsistent state with partial
updates carried out
 Example: Transfer of funds from one account to another should
either complete or not happen at all

Concurrent access by multiple users
 Concurrent accessed needed for performance
 Uncontrolled concurrent accesses can lead to inconsistencies
– Example: Two people reading a balance and updating it at the
same time

Security problems
 Hard to provide user access to some, but not all, data
 Database systems offer solutions to all the above problems
Levels of Abstraction
 Physical level: describes how a record (e.g., customer) is stored.
 Logical level: describes data stored in database, and the relationships
among the data.
type customer = record
customer_id : string;
customer_name : string;
customer_street : string;
customer_city : string;
end;
 View level: application programs hide details of data types. Views can
also hide information (such as an employee’s salary) for security
purposes.
View of Data
An architecture for a database system
Instances and Schemas

Similar to types and variables in programming languages

Schema – the logical structure of the database


Example: The database consists of information about a set of customers and
accounts and the relationship between them)

Analogous to type information of a variable in a program

Physical schema: database design at the physical level

Logical schema: database design at the logical level
Instance – the actual content of the database at a particular point in time


Analogous to the value of a variable
Physical Data Independence – the ability to modify the physical schema without
changing the logical schema

Applications depend on the logical schema

In general, the interfaces between the various levels and components should
be well defined so that changes in some parts do not seriously influence others.
Data Models
 A collection of tools for describing




Data
Data relationships
Data semantics
Data constraints
 Relational model
 Entity-Relationship data model (mainly for database design)
 Object-based data models (Object-oriented and Object-relational)
 Semistructured data model (XML)
 Other older models:


Network model
Hierarchical model
Data Manipulation Language (DML)
 Language for accessing and manipulating the data organized by the
appropriate data model

DML also known as query language
 Two classes of languages

Procedural – user specifies what data is required and how to get
those data

Declarative (nonprocedural) – user specifies what data is
required without specifying how to get those data
 SQL is the most widely used query language
Data Definition Language (DDL)
 Specification notation for defining the database schema
Example:
create table account (
account_number
branch_name
char(10),
char(10),
balance
integer)
 DDL compiler generates a set of tables stored in a data dictionary
 Data dictionary contains metadata (i.e., data about data)

Database schema
 Data storage and definition language
Specifies the storage structure and access methods used
 Integrity constraints
 Domain constraints
 Referential integrity (e.g. branch_name must correspond to a
valid branch in the branch table)


Authorization
Relational Model
Attributes
 Example of tabular data in the relational model
A Sample Relational Database
SQL
 SQL: widely used non-procedural language

Example: Find the name of the customer with customer-id 192-83-7465
select customer.customer_name
from
customer
where customer.customer_id = ‘192-83-7465’

Example: Find the balances of all accounts held by the customer with
customer-id 192-83-7465
select account.balance
from
depositor, account
where depositor.customer_id = ‘192-83-7465’ and
depositor.account_number = account.account_number
 Application programs generally access databases through one of

Language extensions to allow embedded SQL

Application program interface (e.g., ODBC/JDBC) which allow SQL
queries to be sent to a database
Database Design
The process of designing the general structure of the database:
 Logical Design – Deciding on the database schema. Database design
requires that we find a “good” collection of relation schemas.

Business decision – What attributes should we record in the
database?

Computer Science decision – What relation schemas should we
have and how should the attributes be distributed among the various
relation schemas?
 Physical Design – Deciding on the physical layout of the database
The Entity-Relationship Model
 Models an enterprise as a collection of entities and relationships

Entity: a “thing” or “object” in the enterprise that is distinguishable
from other objects


Described by a set of attributes
Relationship: an association among several entities
 Represented diagrammatically by an entity-relationship diagram:
Other Data Models
 Object-oriented data model
 Object-relational data model
Database Application Architectures
(web browser)
Old
Modern
Database Management System Internals
 Storage management
 Query processing
 Transaction processing
Storage Management
 Storage manager is a program module that provides the interface
between the low-level data stored in the database and the application
programs and queries submitted to the system.
 The storage manager is responsible to the following tasks:

Interaction with the file manager

Efficient storing, retrieving and updating of data
 Issues:

Storage access

File organization

Indexing and hashing
Query Processing
1. Parsing and translation
2. Optimization
3. Evaluation
Query Processing (Cont.)
 Alternative ways of evaluating a given query

Equivalent expressions

Different algorithms for each operation
 Cost difference between a good and a bad way of evaluating a query can
be enormous
 Need to estimate the cost of operations

Depends critically on statistical information about relations which the
database must maintain

Need to estimate statistics for intermediate results to compute cost of
complex expressions
Transaction Management
 A transaction is a collection of operations that performs a single
logical function in a database application
 Transaction-management component ensures that the database
remains in a consistent (correct) state despite system failures (e.g.,
power failures and operating system crashes) and transaction failures.
 Concurrency-control manager controls the interaction among the
concurrent transactions, to ensure the consistency of the database.
Overall System Structure
History of Database Systems
 1950s and early 1960s:

Data processing using magnetic tapes for storage


Tapes provide only sequential access
Punched cards for input
 Late 1960s and 1970s:

Hard disks allow direct access to data

Network and hierarchical data models in widespread use

Ted Codd defines the relational data model


Would win the ACM Turing Award for this work

IBM Research begins System R prototype

UC Berkeley begins Ingres prototype
High-performance (for the era) transaction processing
History (cont.)
 1980s:

Research relational prototypes evolve into commercial systems
 SQL becomes industry standard
 Parallel and distributed database systems
 Object-oriented database systems
 1990s:

Large decision support and data-mining applications
 Large multi-terabyte data warehouses
 Emergence of Web commerce
 2000s:

XML and XQuery standards
 Automated database administration

Increasing use of highly parallel database systems
 Web-scale distributed data storage systems
RELATIONAL MODEL
Example of a Relation
Attribute Types
 Each attribute of a relation has a name
 The set of allowed values for each attribute is called the domain of the
attribute
 Attribute values are (normally) required to be atomic; that is, indivisible

E.g. the value of an attribute can be an account number,
but cannot be a set of account numbers
 Domain is said to be atomic if all its members are atomic
 The special value null is a member of every domain
 The null value causes complications in the definition of many operations
Relation Schema
 Formally, given domains D1, D2, …. Dn a relation r is a subset of
D1 x D2 x … x Dn
Thus, a relation is a set of n-tuples (a1, a2, …, an) where each ai  Di
 Schema of a relation consists of


attribute definitions

name

type/domain
integrity constraints
Relation Instance
 The current values (relation instance) of a relation are specified by a
table
 An element t of r is a tuple, represented by a row in a table
 Order of tuples is irrelevant (tuples may be stored in an arbitrary
order)
attributes
(or columns)
customer_name customer_street
Jones
Smith
Curry
Lindsay
Main
North
North
Park
customer
customer_city
Harrison
Rye
Rye
Pittsfield
tuples
(or rows)
Database
 A database consists of multiple relations
 Information about an enterprise is broken up into parts, with each
relation storing one part of the information
 E.g.
account : information about accounts
depositor : which customer owns which account
customer : information about customers
The customer Relation
The depositor Relation
Why Split Information Across Relations?
 Storing all information as a single relation such as
bank(account_number, balance, customer_name, ..)
results in

repetition of information


e.g.,if two customers own an account (What gets repeated?)
the need for null values

e.g., to represent a customer without an account
 Normalization theory deals with how to design relational schemas
Keys
 Let K  R
 K is a superkey of R if values for K are sufficient to identify a unique tuple of
each possible relation r(R)

by “possible r ” we mean a relation r that could exist in the enterprise we
are modeling.

Example: {customer_name, customer_street} and
{customer_name}
are both superkeys of Customer, if no two customers can possibly have
the same name

In real life, an attribute such as customer_id would be used instead of
customer_name to uniquely identify customers, but we omit it to keep
our examples small, and instead assume customer names are unique.
Keys (Cont.)
 K is a candidate key if K is minimal
Example: {customer_name} is a candidate key for Customer, since it
is a superkey and no subset of it is a superkey.
 Primary key: a candidate key chosen as the principal means of
identifying tuples within a relation

Should choose an attribute whose value never, or very rarely,
changes.

E.g. email address is unique, but may change
Foreign Keys
 A relation schema may have an attribute that corresponds to the primary
key of another relation. The attribute is called a foreign key.

E.g. customer_name and account_number attributes of depositor are
foreign keys to customer and account respectively.

Only values occurring in the primary key attribute of the referenced
relation may occur in the foreign key attribute of the referencing
relation.
Schema Diagram
Query Languages
 Language in which user requests information from the database.
 Categories of languages

Procedural

Non-procedural, or declarative
 “Pure” languages:

Relational algebra

Tuple relational calculus

Domain relational calculus
 Pure languages form underlying basis of query languages that people
use.
Relational Algebra
 Procedural language
 Six basic operators

select: 

project: 

union: 

set difference: –

Cartesian product: x

rename: 
 The operators take one or two relations as inputs and produce a new
relation as a result.
Select Operation – Example
 Relation r
 A=B ^ D > 5 (r)
A
B
C
D


1
7


5
7


12
3


23 10
A
B
C
D


1
7


23 10
Project Operation – Example
 Relation r:
A,C (r)
A
B
C

10
1

20
1

30
1

40
2
A
C
A
C

1

1

1

1

1

2

2
=
Union Operation – Example
 Relations r, s:
A
B
A
B

1

2

2

3

1
s
r
 r  s:
A
B

1

2

1

3
Set Difference Operation – Example
 Relations r, s:
A
B
A
B

1

2

2

3

1
s
r
 r – s:
A
B

1

1
Cartesian-Product Operation – Example
 Relations r, s:
A
B
C
D
E

1

2




10
10
20
10
a
a
b
b
r
s
 r x s:
A
B
C
D
E








1
1
1
1
2
2
2
2








10
10
20
10
10
10
20
10
a
a
b
b
a
a
b
b
Rename Operation
 Allows us to name, and therefore to refer to, the results of relational-
algebra expressions.
 Allows us to refer to a relation by more than one name.
 Example:
 x (E)
returns the expression E under the name X
 If a relational-algebra expression E has arity n, then
 x ( A ,A
1
2 ,...,An
)
(E )
returns the result of expression E under the name X, and with the
attributes renamed to A1 , A2 , …., An .
Composition of Operations
 Can build expressions using multiple operations
 Example: A=C(r x s)
 rxs
A
B
C
D
E








1
1
1
1
2
2
2
2








10
10
20
10
10
10
20
10
a
a
b
b
a
a
b
b
A
B
C
D
E



1
2
2
 10
 10
 20
a
a
b
 A=C(r x s)
Banking Example
branch (branch_name, branch_city, assets)
customer (customer_name, customer_street, customer_city)
account (account_number, branch_name, balance)
loan (loan_number, branch_name, amount)
depositor (customer_name, account_number)
borrower (customer_name, loan_number)
Example Queries
 Find all loans of over $1200
amount > 1200 (loan)
 Find the loan number for each loan of an amount greater than
$1200
loan_number (amount > 1200 (loan))
 Find the names of all customers who have a loan, an account, or both,
from the bank
customer_name (borrower)  customer_name (depositor)
Example Queries
 Find the names of all customers who have a loan at the Perryridge
branch.
customer_name (branch_name=“Perryridge”
(borrower.loan_number = loan.loan_number(borrower x loan)))
 Find the names of all customers who have a loan at the
Perryridge branch but do not have an account at any branch of
the bank.
customer_name (branch_name = “Perryridge”
(borrower.loan_number = loan.loan_number(borrower x loan))) –
customer_name(depositor)
Example Queries
 Find the names of all customers who have a loan at the Perryridge branch.


customer_name (branch_name = “Perryridge” (
borrower.loan_number = loan.loan_number (borrower x loan)))
customer_name(loan.loan_number =
borrower.loan_number (
(branch_name = “Perryridge” (loan)) x borrower))
Additional Operations
 Additional Operations

Set intersection

Natural join

Aggregation

Outer Join

Division
 All above, other than aggregation, can be expressed using basic
operations we have seen earlier
Set-Intersection Operation – Example
 Relation r, s:
A
B



1
2
1
r
A
B


2
3
s
 rs
A
B

2
Natural Join Operation – Example
 Relations r, s:
A
B
C
D
B
D
E





1
2
4
1
2





a
a
b
a
b
1
3
1
2
3
a
a
a
b
b





r
 r
s
s
A
B
C
D
E





1
1
1
1
2





a
a
a
a
b





Natural-Join Operation

Notation: r
s
 Let r and s be relations on schemas R and S respectively.
s is a relation on schema R  S obtained as follows:
Then, r

Consider each pair of tuples tr from r and ts from s.

If tr and ts have the same value on each of the attributes in R  S, add
a tuple t to the result, where

t has the same value as tr on r

t has the same value as ts on s
 Example:
R = (A, B, C, D)
S = (E, B, D)

Result schema = (A, B, C, D, E)

r
s is defined as:
r.A, r.B, r.C, r.D, s.E (r.B = s.B  r.D = s.D (r x s))
Aggregate Functions and Operations
 Aggregation function takes a collection of values and returns a single
value as a result.
avg: average value
min: minimum value
max: maximum value
sum: sum of values
count: number of values
 Aggregate operation in relational algebra
G1,G2 ,,Gn
F ( A ),F ( A ,,F ( A ) (E )
1
1
2
2
n
n
E is any relational-algebra expression

G1, G2 …, Gn is a list of attributes on which to group (can be empty)

Each Fi is an aggregate function

Each Ai is an attribute name
Aggregate Operation – Example
 Relation r:
 g sum(c) (r)
A
B
C








7
7
3
10
sum(c )
27
 Question: Which aggregate operations cannot be expressed
using basic relational operations?
Aggregate Operation – Example
 Relation account grouped by branch-name:
branch_name account_number
Perryridge
Perryridge
Brighton
Brighton
Redwood
branch_name
g
balance
A-102
A-201
A-217
A-215
A-222
400
900
750
750
700
sum(balance) (account)
branch_name
Perryridge
Brighton
Redwood
sum(balance)
1300
1500
700
Aggregate Functions (Cont.)
 Result of aggregation does not have a name

Can use rename operation to give it a name

For convenience, we permit renaming as part of aggregate
operation
branch_name g sum(balance) as sum_balance (account)
Outer Join
 An extension of the join operation that avoids loss of information.
 Computes the join and then adds tuples form one relation that does not
match tuples in the other relation to the result of the join.
 Uses null values:

null signifies that the value is unknown or does not exist

All comparisons involving null are (roughly speaking) false by
definition.
Outer Join – Example
 Relation loan
loan_number branch_name
L-170
L-230
L-260
Downtown
Redwood
Perryridge
amount
3000
4000
1700
 Relation borrower
customer_name loan_number
Jones
Smith
Hayes
L-170
L-230
L-155
Outer Join – Example
 Join
loan
borrower
loan_number
branch_name
L-170
L-230
Downtown
Redwood
amount customer_name
3000
4000
Jones
Smith
 Left Outer Join
loan
borrower
loan_number
branch_name
L-170
L-230
L-260
Downtown
Redwood
Perryridge
amount customer_name
3000
4000
1700
Jones
Smith
null
Outer Join – Example
 Right Outer Join
loan
borrower
loan_number
branch_name
L-170
L-230
L-155
Downtown
Redwood
null
amount customer_name
3000
4000
null
Jones
Smith
Hayes
 Full Outer Join
loan
borrower
loan_number
branch_name
L-170
L-230
L-260
L-155
Downtown
Redwood
Perryridge
null
amount customer_name
3000
4000
1700
null
Jones
Smith
null
Hayes
Null Values
 It is possible for tuples to have a null value, denoted by null, for some
of their attributes
 null signifies an unknown value or that a value does not exist.
 The result of any arithmetic expression involving null is null.
 Aggregate functions simply ignore null values (as in SQL)
 For duplicate elimination and grouping, null is treated like any other
value, and two nulls are assumed to be the same (as in SQL)
Bank Example Queries
 Find the names of all customers who have a loan and an account at
bank.
customer_name (borrower)  customer_name (depositor)
 Find the name of all customers who have a loan at the bank and the
loan amount
customer_name, loan_number, amount (borrower
loan)
Bank Example Queries
 Find all customers who have an account from at least the “Downtown”
and the Uptown” branches.
 Query 1
customer_name (branch_name = “Downtown” (depositor
customer_name (branch_name = “Uptown” (depositor
account )) 
account))
Reference
 Silberschatz, Database System Concepts-5th edition