Software Development Architectures Ankur K. Rajopadhye Louisiana Tech University.

Slides:



Advertisements
Similar presentations
Welcome to Middleware Joseph Amrithraj
Advertisements

ICS 434 Advanced Database Systems
Chapter 13 Review Questions
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Distributed Systems Architectures Slide 1 1 Chapter 9 Distributed Systems Architectures.
Objectives In this session, you will learn to:
CS 415 N-Tier Application Development By Umair Ashraf July 2nd,2013 National University of Computer and Emerging Sciences Lecture # 7 N-Tier Architecture.
Technical Architectures
Distributed Systems Architectures
Introduction to Web Application Architectures Web Application Architectures 18 th March 2005 Bogdan L. Vrusias
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System architectures Updated: November 2014.
12 Chapter 12 Client/Server Systems Hachim Haddouti.
Client/Server Architecture
Chapter 2 Client Server Architecture
Tiered architectures 1 to N tiers. 2 An architectural history of computing 1 tier architecture – monolithic Information Systems – Presentation / frontend,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 12 Slide 1 Distributed Systems Design 1.
Client/Server Computing. Information processing is distributed among several workstations and servers on a network, with each function being assigned.
E-Business Lecture 3 Website Development and Management Process.
The Client/Server Database Environment
Dynamics AX Technical Overview Application Architecture Dynamics AX Technical Overview.
Web Application Architecture: multi-tier (2-tier, 3-tier) & mvc
Web application architecture
Introduction to Databases Transparencies 1. ©Pearson Education 2009 Objectives Common uses of database systems. Meaning of the term database. Meaning.
N-Tier Architecture.
Client/Server Architectures
The Design Discipline.
LAYING OUT THE FOUNDATIONS. OUTLINE Analyze the project from a technical point of view Analyze and choose the architecture for your application Decide.
Copyright © cs-tutorial.com. Introduction to Web Development In 1990 and 1991,Tim Berners-Lee created the World Wide Web at the European Laboratory for.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
Internet Basics Dr. Norm Friesen June 22, Questions What is the Internet? What is the Web? How are they different? How do they work? How do they.
Introduction to distributed systems Dr. S. Indran 23 January 2004.
1 Copyright © 2004, Oracle. All rights reserved. Introduction to Oracle Forms Developer and Oracle Forms Services.
Lecture On Database Analysis and Design By- Jesmin Akhter Lecturer, IIT, Jahangirnagar University.
CSC271 Database Systems Lecture # 4.
E-Learning Material Web Application Design 3. Web Application Design Architecture Which objects go where? The final model notation Summary.
DAT602 Database Application Development Lecture 12 C/S Model Database Application.
® IBM Software Group © 2007 IBM Corporation J2EE Web Component Introduction
SAMANVITHA RAMAYANAM 18 TH FEBRUARY 2010 CPE 691 LAYERED APPLICATION.
Firewalls Nathan Long Computer Science 481. What is a firewall? A firewall is a system or group of systems that enforces an access control policy between.
Unit – I CLIENT / SERVER ARCHITECTURE. Unit Structure  Evolution of Client/Server Architecture  Client/Server Model  Characteristics of Client/Server.
Client – Server Architecture. Client Server Architecture A network architecture in which each computer or process on the network is either a client or.
The Client/Server Database Environment Ployphan Sornsuwit KPRU Ref.
2-Tier,3-Tier datawarehouse Submitted by Manisha Dubey & Akanksha Agrawal.
Database Architectures Database System Architectures Considerations – Data storage: Where do the data and DBMS reside? – Processing: Where.
Position Paper How should the business logic be developed? As middle-tier application? or as a DBMS stored procedures? Akash Sharma Hiren Nagar.
Distributed System Architectures Yonsei University 2 nd Semester, 2014 Woo-Cheol Kim.
CSC 480 Software Engineering High Level Design. Topics Architectural Design Overview of Distributed Architectures User Interface Design Guidelines.
Chapter 1 Revealed Distributed Objects Design Concepts CSLA.
JDBC Chapter 1 JDBC Introduction
CSC 480 Software Engineering Lecture 17 Nov 4, 2002.
Client – Server Architecture A Basic Introduction 1.
E-commerce Architecture Ayşe Başar Bener. Client Server Architecture E-commerce is based on client/ server architecture –Client processes requesting service.
Distributed Systems Architectures. Topics covered l Client-server architectures l Distributed object architectures l Inter-organisational computing.
Introduction to Oracle Forms Developer and Oracle Forms Services
INLS 623– Stored Procedures
CIIT-Human Computer Interaction-CSC456-Fall-2015-Mr
N-Tier Architecture.
Introduction to Oracle Forms Developer and Oracle Forms Services
Introduction to Oracle Forms Developer and Oracle Forms Services
MVC and other n-tier Architectures
Software Design and Architecture
The Client/Server Database Environment
CSC 480 Software Engineering
Introduction to J2EE Architecture
Enterprise Application Architecture
Introduction to Databases Transparencies
Lecture 1: Multi-tier Architecture Overview
Tiers vs. Layers.
Internet Protocols IP: Internet Protocol
Client/Server Architecture
Presentation transcript:

Software Development Architectures Ankur K. Rajopadhye Louisiana Tech University

Needs of large business Applications Functionality Stability Adaptability under rising workloads and changing business requirements Highest levels of performance and availability Cost Effective

Contents of Business Applications Business Logic Database Graphical User Interface

Explanation of keywords Business Logic: Rules governing the business. These can change frequently depending upon the business. Database: Contains the data relevant for the business. Graphical User Interface: Provides the platform for interaction of the user with the system.

The 1-Tier Architecture

Advantages  Easy and quick to develop  Useful for small offices Disadvantages  Difficult to upgrade  Not scalable  Don't protect valuable "Business Logic"

The 2-Tier Architecture

Advantages: Protects business logic from UI Disadvantages: Business-logic is implemented on the PC Increased network traffic Application logic can’t be reused Must design/implement protocol for communication between client and server.

The 3-Tier Architecture

Advantages Clear separation of user-interface-control and data presentation from application- logic. Change in business logic wont need change in other layers. Dynamic load balancing by use of multiple servers

N-tier architecture Also known as the “layered” architecture N usually denotes 3 or more tiers (layers) Can be used to model both a web-based application and a desktop application

The N-tier architecture

The tiers may contain one or more components of the application The components in one tier can communicate ONLY with the components in the tiers above and below

The N-tier architecture The components implement major functionalities in the application Every application can have at least three tiers: The UI tier The Business Logic tier The Data Storage tier

The N-tier architecture Disadvantages In small applications, the benefits are usually not visible. Every data that goes in the system from the user to the database must pass through the components in the middle layers, and therefore the response time of the system will be slower.

The N-tier architecture Advantages Easy to change: you can decide to switch from desktop applications to web based applications by just changing the UI layer (a small part of the application). The same thing with the database system. Easy to manage: if each layer has its own functionality, when something needs to be changed you will know what to change

The N-tier architecture Advantages Easy to reuse: if another application is developed for the same domain, it can use a big part of the business layer Easy to develop: each layer can be developed by separate teams, and focus only on theirs specific problems (you don’t have to know HTML, ASP, OO design and SQL at the same time)

Thank you!