CIIT-Human Computer Interaction-CSC456-Fall-2015-Mr

Slides:



Advertisements
Similar presentations
Welcome to Middleware Joseph Amrithraj
Advertisements

Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
Objectives In this session, you will learn to:
8.
Technical Architectures
2 Object-Oriented Analysis and Design with the Unified Process Objectives  Explain how statecharts can be used to describe system behaviors  Use statecharts.
1 Pertemuan 13 Servers for E-Business Matakuliah: M0284/Teknologi & Infrastruktur E-Business Tahun: 2005 Versi: >
Distributed Systems Architectures
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica System architectures Updated: November 2014.
Satzinger, Jackson, and Burd Object-Orieneted Analysis & Design
Introduction to Web Applications Instructor: Enoch E. Damson.
Client/Server Architecture
Chapter 2 Client Server Architecture
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 12 Slide 1 Distributed Systems Design 1.
Web Application Architecture: multi-tier (2-tier, 3-tier) & mvc
Web application architecture
N-Tier Architecture.
Software Development Architectures Ankur K. Rajopadhye Louisiana Tech University.
Client/Server Architectures
Chapter 9 Moving to Design Part 2.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
Advanced Web Forms with Databases Programming Right from the Start with Visual Basic.NET 1/e 13.
® IBM Software Group © 2007 IBM Corporation J2EE Web Component Introduction
Database Application Security Models Database Application Security Models 1.
Csi315csi315 Client/Server Models. Client/Server Environment LAN or WAN Server Data Berson, Fig 1.4, p.8 clients network.
Unit – I CLIENT / SERVER ARCHITECTURE. Unit Structure  Evolution of Client/Server Architecture  Client/Server Model  Characteristics of Client/Server.
Implementation - Part 2 CPS 181s March 18, Pieces of the Site-building Puzzle Page 180, figure 4.1.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
Distributed System Architectures Yonsei University 2 nd Semester, 2014 Woo-Cheol Kim.
CSC 480 Software Engineering Lecture 17 Nov 4, 2002.
1 LM 6 Database Applications Dr. Lei Li. Learning Objectives Explain three components of a client-server system Describe differences between a 2-tiered.
E-commerce Architecture Ayşe Başar Bener. Client Server Architecture E-commerce is based on client/ server architecture –Client processes requesting service.
Zoljargal.M  Introduction  Methods, approaches  Specifics of Web architecture  Typical components of architectures.
Chapter-04 Building an Ecommerce Website. Building an E-commerce Site: A Systematic Approach The two most important management challenges in building.
12. DISTRIBUTED WEB-BASED SYSTEMS Nov SUSMITHA KOTA KRANTHI KOYA LIANG YI.
Distributed Systems Architectures Chapter 12. Objectives  To explain the advantages and disadvantages of different distributed systems architectures.
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
CompSci 280 S Introduction to Software Development
Web Engineering CS-4513 Prepared By: Junaid Hassan Lecturer at UOS M.B.Din Campus
N-Tier Architecture.
Web Application Architecture
Web Development Web Servers.
Introduction to Oracle Forms Developer and Oracle Forms Services
SOA (Service Oriented Architecture)
Principles of Network Applications
E-commerce | WWW World Wide Web - Concepts
Introduction to Oracle Forms Developer and Oracle Forms Services
MVC and other n-tier Architectures
E-commerce | WWW World Wide Web - Concepts
Software Design and Architecture
CSC 480 Software Engineering
Processes The most important processes used in Web-based systems and their internal organization.
Introduction to J2EE Architecture
Chapter 16 Designing Distributed and Internet Systems
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
Chapter 2 Database Environment Pearson Education © 2009.
Web Application Architectures
Introduction to Databases Transparencies
Lecture 1: Multi-tier Architecture Overview
Database Environment Transparencies
Chapter 6 – Architectural Design
Software models - Software Architecture Design Patterns
An Introduction to Software Architecture
A Component-based Architecture for Mobile Information Access
Chapter 17: Client/Server Computing
KNOWLEDGE MANAGEMENT (KM) Session # 34
Design Yaodong Bi.
Web Servers (IIS and Apache)
Presentation transcript:

CIIT-Human Computer Interaction-CSC456-Fall-2015-Mr CIIT-Human Computer Interaction-CSC456-Fall-2015-Mr. Tehseen Riaz Abbasi

Web Technologies and Programming Lecture 05 Modeling web applications

Web application architecture

Presentation modeling Summary of the previous lecture System modeling Requirement Modeling use-case diagram, activity diagram Content modeling class diagram, state machine diagram Navigation modeling Presentation modeling

Summary of the previous lecture Technologies for web development Protocol client-side technologies server-side technologies Testing web applications Objectives Levels Web application specifics challenges

Outline Software system architecture Specifics of web application architecture Layered web architecture 2-layered architecture 3-layered architecture N-layered architecture Department of Computer Science, CIIT Islamabad.

1. Software system architecture The architecture of a computer system is the high-level (most general) design on which the system is based Architectural features include: Components (a Component is a part of a program) It contains one or several routines Connectors (how components communicate) Collaborations (how components interact)

1. Software system architecture… Key attributes of an architecture architecture describes structure architecture forms the transition from analysis to implementation different viewpoints (conceptual, runtime, process and implementation) makes a system understandable

1. Software system architecture… Factors influence the system architecture Quality considerations with Performance Scalability Reusability Other? Functional Requirements Clients Users Other Stakeholders Architecture

1. Software system architecture… Factors influence the system architecture Architecture Experience with Existing Architecture Patterns Project Management Other? Technical Aspects Operating System Middleware Legacy Systems Other?

2. Specifics in web application architecture A number of architectures for specific requirement in several application domain have been developed For web application architecture, usually we consider layering aspect: to implement the principle of ‘separation of concerns’ data aspects: to support processing of structured and non-structured data

2. Specifics in web application architecture… For web applications quality requirements are more demanding as compared to desktop applications performance, security, scalability, and availability etc. Need specific technical infrastructures both for the development and the operation of web applications

2. Specifics in web application architecture we have to consider web infrastructure architecture (WPA) web application architecture (WAA) Web application architecture (WAA) depends on the problem domain of the application, therefore we focus on web platform architecture (WPA)

2. 1 Components of a web application architecture Client: generally a browser (user agent) is controlled by a user to operate the web application the client’s functionality can be expanded by installing plug-ins Firewall: a piece of software regulating the communication between insecure networks(e.g., the Internet) and secure networks (e.g., corporate LANs) this communication is filtered by access rules

2. 1 Components of a web application architecture Proxy: A proxy is typically used to temporarily store web pages in a cache Web server: A Web server is a piece of software that supports various Web protocols like HTTP, and HTTPS, etc., to process client requests

2. 1 Components of a web application architecture Database server: this server normally supplies data in structured form, e.g., in tables Legacy application: A legacy application is an older system that should be integrated as an internal or external component

2. 1 Components of a web application architecture Media server: This component is primarily used for content streaming of non-structured bulk data (e.g., audio or video) Application server: An application server holds the functionality required by several applications

2. 1 Components of a web application architecture Client Firewall proxy Web-server CGI support Browser HTML, XML Plug -In Database server Application server Media server Legacy application

3. Layered architecture for web applications Presentation tier: Every web application needs to communicate with external entities, human users or other computers allows these entities to interact with the system implemented as a GUI interface How the data should appear to the user

3. Layered architecture for web applications Application tier: Web applications do more than information delivery, they perform data processing (Business Logic & calculation) behind the results being delivered This tier is often referred to as Services Business logic

3. Layered architecture for web applications Data tier: Web applications needs data to work with Data can reside in databases or other information repositories Deals with and implements different data sources of Information Systems

3.1 two-layer web architecture Presents architecture in two layers: Layer 1: Client platform, hosting a web browser Layer 2: server platform, hosting all server software components Also called client/server architecture Client directly send request to the server Server respond to the client request Static or dynamic requests

3.1 two-layer web architecture Client Client Server Web/App Server Services Database Dynamic HTML Static HTML

3.1 two-layer web architecture Advantage: Inexpensive (single platform) Disadvantages: Interdependency (coupling) of components No redundancy Limited scalability Typical application: 10-100 users Small company or organization

3.2 three-layer web architecture Usually implemented in 3 layers Layer 1: Data Layer 2: Application Layer 3: presentation Additionally, security mechanism (Firewall) and caching mechanism (Proxies) can be added

3.1 three-layer web architecture Client Firewall Proxy Presentation Layer Web Server Business Layer Application Server (Business Logic, Connectors, Personalization, Data Access) Backend (Legacy Application, Enterprise Info System) Data Layer DBMS

3.2 three-layer web architecture Advantages: Improved performance Decreased coupling of software components Improved scalability Disadvantages: No redundancy Typical Application: 100-1000 users Small business or regional organization, e.g., specialty retailer, small college

3.3 N-layer web architecture A multitier (N-layer) architecture is an expansion of the 3-layer architecture, in one of several different possible ways Replication of the function of a layer Specialization of function within a layer

3.3 N-layer web architecture… Replication: Application and data servers are replicated Servers share the total workload

3.3 N-layer web architecture… Specialization: Servers are specialized Each server handles a designated part of the workload, by function

3.3 N-layer web architecture…

3.3 N-layer web architecture… Advantages: Decoupling of software components Flexibility to add/remove platforms in response to load Scalability Redundancy Disadvantages: Higher costs (maintenance, design, electrical load, cooling) Typical Application: 1000+ users Large business or organization

3.4 Comparison of layered architecture large e-commerce, business, or organization small e-commerce, regional business or organization local business or organization N-Tier 1000 3-Tier users 100 2-Tier 10 capacity scalability redundancy cost

3.5 example Client Presentation Layer Web Server Business Layer Application Server (Business Logic, Connectors, Personalization, Data Access) Business Layer Media Server DBMS Data Layer

Summary Software system architecture Specifics of web application architecture Layered web architecture 2-layered architecture 3-layered architecture N-layered architecture

THANK YOU