Slide 1 Ch 13 Application architectures Generic architectures that can be configured and adapted to create a system that meets specific requirements Can.

Slides:



Advertisements
Similar presentations
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Application Architectures IS301.
Advertisements

Ch 26.
Chapter 6 Architectural Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 13 Slide 1 Application architectures.
Chapter 13 Review Questions
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
© 2005 Prentice Hall7-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Modifed from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 12 & 13 Slide 1 Models of Software Architectures.
1 SWE Introduction to Software Engineering Lecture 21 – Architectural Design (Chapter 13)
1 SWE Introduction to Software Engineering Lecture 22 – Architectural Design (Chapter 13)
Application architectures
REAL-TIME SOFTWARE SYSTEMS DEVELOPMENT Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
©Ian Sommerville 2000 Software Engineering, 6th edition Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing.
Course Instructor: Aisha Azeem
Architectural Styles SE 464 / ECE 452 / CS 446 Chang Hwan Peter Kim Based on slides prepared by Michał Antkiewicz June 24, 2006.
Application architectures
Chapter 3 Software Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 13 Slide 1 Application architectures.
Chapter 6 – Architectural Design
Chapter 6 – Architectural Design Lecture 2 1Chapter 6 Architectural design.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 31 Slide 1 Service-centric Software Engineering 2.
Architectural Design.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
CS 425/625 Software Engineering Legacy Systems
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
1 Components of a Computer System Lesson 17: Modes Of Use.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
CSc 461/561 Software Engineering Lecture 7 – Architectural Design.
Chapter 6 Architectural Design.
 Repository Model  Client-Server Model  Layered Model  Modular decomposition styles  Object Models  Function Oriented Pipelining  Control Styles.
Lecture 1 Chapter 6 Architectural design1. Topics covered Architectural design decisions Architectural views Architectural patterns Application architectures.
Chapter 6 – Architectural Design 1Chapter 6 Architectural design.
Chapter 6 – Architectural Design 1Chapter 6 Architectural design CS 425 October 29, 2013 Ian Sommerville, Software Engineering, 9 th Edition Pearson Education,
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
Types of Processing. Data Processing Types of Processing Batch processing Interactive processing Real Time processing.
Chapter 6 – Architectural Design Chapter 6 Architectural Design1 CS 425 October 29, 2015 Note: These are a slightly modified version of Chapter 6 slides.
Chapter 6 Architectural design Chapter 6 – Architectural Design Lecture 1 1.
Software Architectural Design 1. Topics covered  Architectural design decisions  Architectural views  Architectural patterns  Application architectures.
CS223: Software Engineering
Real time processing In real time processing, input is processed and acted upon immediately. Real time processing is used in mission critical applications.
Application architectures Advisor : Dr. Moneer Al_Mekhlafi By : Ahmed AbdAllah Al_Homaidi.
Application architectures 1. Topics covered In the previous chapter, the discussion of system arcitectures focused on architectural issues such as control,
Chapter 6 – Architectural Design 1Chapter 6 Architectural design CS 425 October 20, 2011 Ian Sommerville, Software Engineering, 9 th Edition Pearson Education,
Application architectures. Objectives l To explain the organisation of two fundamental models of business systems - batch processing and transaction processing.
A PPLICATION ARCHITECTURES Chapter 13. O BJECTIVES To explain the organisation of two fundamental models of business systems - batch processing and transaction.
Lecture 6 – Architectural Design
Software architecture
CompSci 280 S Introduction to Software Development
Chapter 6 – Architectural Design
Architectural Design.
Chapter 6 – Architectural Design
Chapter 6 – Architectural Design
Chapter 6 – Architectural Design
Software Engineering Architectural Design Chapter 6 Dr.Doaa Samy
Software Engineering Architectural Design Chapter 6 Dr.Doaa Samy
Chapter 6 – Architectural Design
Chapter 6 – Architectural Design
Chapter 6 – Architectural Design
Chapter 5 Architectural Design.
Chapter 6 – Architectural Design
Chapter 6 – Architectural Design
CS385 T&D Software Engineering Dr.Doaa Sami Khafaga
The Main Features of Operating Systems
Chapter 5 Architectural Design.
Chapter 6: Architectural Design
Chapter 6 – Architectural Design
Presentation transcript:

Slide 1 Ch 13 Application architectures Generic architectures that can be configured and adapted to create a system that meets specific requirements Can be used as a starting point for architectural design design checklist way of organizing the work of the development team means of assessing components for reuse vocabulary for talking about application types Read this chapter to help structure your project Some repetition

Slide 2 Application types 1. Data processing data driven applications that process data in batches without explicit user intervention during the processing billing systems, payroll systems 2. Transaction processing data-centered applications that process user requests and update information in a system database e-commerce, reservation systems 3. Event processing system actions depend on interpreting environmental events word processors, games 4. Language processing user intentions are specified in a formal language that is processed and interpreted by the system compilers, command interpreters

Slide 3 1. Data processing systems Data-centered Databases usually larger than the software Data input and output in batches input: customer #s and associated readings of an elec. meter output: one bill for each customer # Typical structure.

Slide 4 2. Transaction processing systems Process user requests for information from or to update a database From a user perspective: any coherent sequence of operations that satisfies a goal e.g. find the times of flights from London to Paris Users make asynchronous requests which are processed by a transaction manager

Slide 5 ATM (transaction processing) System organization: Transaction management:

Slide 6 Information systems (transaction processing.) Usually layered Generic: Library information system

Slide 7 Resource allocation systems (transaction processing) Systems that manage a fixed amount of some resource airspace in air traffic control systems rooms in a hotel tickets on Ticketmaster books in a library Usually layered

Slide 8 3. Event processing systems These systems respond to events in the system’s environment. Their key characteristic is that event timing is unpredictable so the architecture has to be organised to handle this. Many common systems such as word processors, games, etc. are event processing systems.

Slide 9 Editing systems (event processing) Characteristics: single user must provide rapid feedback to user actions transactions may be long and need recovery facilities Naturally object-oriented screen event command editor data ancillary data file system display

Slide Language processing systems Natural or artificial language input Output is some other representation of that language May include an interpreter to act on the instructions in the language being processed

Slide 11 Data-flow model of a compiler

Slide 12 Repository model of a compiler

Slide 13 To think about How do editing and language processing systems differ? How does your project fit any of these models?