Your SlideShare is downloading. ×
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
BIS02 Systems Architecture
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

BIS02 Systems Architecture

2,923

Published on

Course Material for MBA course on Business Information Systems

Course Material for MBA course on Business Information Systems

Published in: Education, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,923
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
309
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Business Information Systems Systems Architecture Prithwis Mukerjee, Ph.D.
  • 2. From Science to Engineering
    • Computer Science refers to Programs
      • Data Structures :describes WHAT is to be processed
      • Algorithms : specifies HOW it is to be processed
    • Information Systems Engineering refers to Systems
      • Database : describes WHAT is to be processed
      • Applications : specifies HOW it is to be processed
  • 3. Integrated Systems
    • First Principle
      • Data must be logically distinct from Applications
    • Single Tier Integrated Systems
      • Need to separate data from applications
      • Even if they are on the same physical hardware
        • Laptop / desktop / server
  • 4. Two Tier : Client Server Architecture
    • Data in the Server
      • server software : Oracle / mySQL / SQL Server / DB2
    • Applications stored on individual machines
      • Business Logic – the business rules
      • Presentation Logic – the GUI : windows, buttons etc
    • LAN : Local Area Network
      • Connects clients machines to server using TCP / IP protocols
  • 5. Two Tier : Client Server Architecture
    • Advantages
      • Convenient graphics user interface
        • Does not place processing burden on server machine when you have hundreds of users
    • Disadvantages
      • High Bandwidth requirements : slows down application
        • Wide Area Network (WAN) issues
      • Maintainance / Version Control of distributed software
  • 6. Three Tier Architecture
    • Application is partitioned
      • Business Logic kept centrally
        • Changes to business logic done at one location
      • Presentation Logic kept locally
        • Data transfer over network is minimised
  • 7. Multi-Tier Architecture
    • “Internet” is no different from WAN
      • Both TCP / IP but WAN is private, Internet is public
        • Inexpensive : no need to invest in corporate network
        • Insecure : need to use security software for corporate use
    • Advantage
      • No need for specialist software at each client location
    • Disadvantage
      • Business Application has to be “web enabled”
    “ internet”
  • 8. Multi Tier Architecture - Consolidation “ internet” Application server and web server physically located on same machine All three servers on same physical machine
  • 9. Two Tier : Multiple Applications
    • Multiple applications
      • Have specific requirements and distinct data
      • Distributed across more than one machine
    • These applications could be
      • From different vendors or developed in-house
      • Based on different technology platforms
        • Oracle ? Excel ? Java ? C++ ?
    Sales server Accounts server machines at Head Office machines at Sales Offices
  • 10. Managing Complexity # 1 : RDBMS
    • Advantages of an Integrated Database System
      • No duplication of data
      • No inconsistency of data across locations / time periods
      • Easier to manage
        • Backup and Restore
        • Security and user access authentication
    Integrated Database Oracle SQL Server MySQL machines at Head Office machines at Sales Offices
  • 11. Managing Complexity # 2 : ERP
    • Advantages of an Integrated ERP System
      • Tighter integration across all functional areas
        • No separate activity required to synchronise data
      • Can be purchase as a single package from established vendors
        • Benefit from best practices available with other companies
      • Faster to implement / Easier to manage and maintain
    Identical software across all company machines Integrated Database Oracle SQL Server MySQL Integrated ERP system SAP Oracle Apps
  • 12. Handling Specialist Requirements Integrated Database Oracle SQL Server MySQL Integrated ERP system SAP Oracle Apps Identical software across all company machines Few specialists may have specific software e.g. Data Warehouse for Business Intelligence
  • 13. Large + Complex + Distributed Systems Database Server Applications Server Wide Area Network
  • 14. Secure, Web Based, Enterprise Systems Database Server Applications Server Firewall Servers Hackers wil get stopped by firewall “ internet”
  • 15. Development of Application Systems Database Server Web + App Server
    • Database Design and Development is based the Relational Model
      • Oracle
      • SQL Server
      • MySQL
      • ZOHO !
    • Application Design and Development
      • Java / C++
      • Visual Basic
      • Ruby-on-Rails
      • ZOHO !
    “ internet”
  • 16. Summary
    • Information Systems need to be partitioned into
      • Data Systems
      • Application Systems
    • Application Architecture
      • Two tier
      • Three tier
      • Three tier web based
    • Data Architecture is based on the Relational Model
      • Theoretically consistent
      • Easy to use
      • Widely supported by major vendors
    • What is the relational model for database systems ?
      • That is the next topic in the

×