CS 501: Software Engineering
Fall 2000
Lecture 14
System Architecture I
Data Intensive Systems
docsity.com
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Data Intensive Systems-Software Engineering-Lecture Slides, Slides of Software Engineering
Software Engineering one of core subject in Computer Science. This lecture was delived by Dr. Shrya Gopal at Bengal Engineering and Science University as one of lecture from lecture series on course. This lecture includes: Data, Intensive, Systems, Architecture, Design, Interfaces, Protocols, Networks, Databases, Security, Authentication, Operations, Software
Typology: Slides
2011/2012
1 / 25
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Data Intensive Systems-Software Engineering-Lecture Slides and more Slides Software Engineering in PDF only on Docsity!
CS 501: Software Engineering
Fall 2000
Lecture 14
System Architecture I Data Intensive Systems
docsity.com
Administration
Midterm examination, October 16, 7:30 to 8:30 p.m.
-- Hollister B14 (note change of room)
-- See course notices for sample questions
docsity.com
Data Intensive Systems
Examples
- Electricity utility customer billing
- Telephone company call recording and billing
- Car rental reservations (e.g., Hertz)
- Stock market brokerage (e.g., Charles Schwab)
- Web sales (e.g., Amazon.com)
docsity.com
Example 1: Electricity Utility Billing
First attempt:
Transaction (^) Data input Master file Bill
Each transaction handled as it arrives.
docsity.com
Transaction Types
- Create account / close account
- Meter reading
- Payment received
- Other credits / debits
- Check cleared / check bounced
- Account query
- Correction of error
- etc., etc., etc.,
docsity.com
Typical Requirements
- All payments to be credited on day received
- Customers must be able to query account by telephone
- Cutting off service for non-payment requires management authorization
- Data input staff should process n transactions per day per person
- Error rate must be below 0.01%
- System available 99.9% of business hours
docsity.com
Batch Processing: Master File Update
Master file update
Bills
Validated transactions in batches
Sort by account
errors Reports
Instructions docsity.com
Benefits of Batch Updating
- All transactions for an account are processed together
- Backup and recovery have fixed checkpoints
- Better management control of operations
- Efficient use of staff and hardware
docsity.com
Example 2: A Small-town Stockbroker
- Transactions Received by mail or over telephone For immediate or later action
- Complex customer inquiries
- Highly competitive market
docsity.com
A Database Architecture
Database(s):
- Customer and account database
- Financial products (e.g., account types, pension plans, savings schemes)
- External databases (e.g., stock markets, mutual funds, insurance companies)
docsity.com
Real-time Transaction
Customer & account database
Products & services database
External services
Real-time transactions
docsity.com
Real-time Transactions & Batch
Processing
Customer & account database
Products & services database
External services
Real-time transactions
Batch processing
Data input
docsity.com
Example: Merger of Two Banks
Each bank has a database with its customer accounts. The databases are used by staff at many branches and for back-office processing.
The requirement is to integrate the two banks so that they appear to the customers to be a single organization and to provide integrated service from all branches.
docsity.com
Merger of Two Banks: Options
A B
docsity.com