1 SWE 205 - Introduction to Software Engineering Lecture 21 – Architectural Design (Chapter 13)

Slides:



Advertisements
Similar presentations
Chapter 26 Legacy Systems.
Advertisements

1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Application Architectures IS301.
Legacy Systems Older software systems that remain vital to an organisation.
Database System Concepts and Architecture
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 13 Slide 1 Application architectures.
Traditional Approach to Design
Chapter 10 The Traditional Approach to Design
Chapter 9: The Traditional Approach to Design Chapter 10 Systems Analysis and Design in a Changing World, 3 rd Edition.
1 Introduction to Data Flow Modelling The data flow approach to requirements determination in building a system for business use. This type of computer.
SWE Introduction to Software Engineering
© 2005 Prentice Hall7-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Modifed from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 12 & 13 Slide 1 Models of Software Architectures.
1 SWE Introduction to Software Engineering Lecture 25 – Object-Oriented Design (Chapter 14)
1 SWE Introduction to Software Engineering Lecture 22 – Architectural Design (Chapter 13)
Software Engineering: Analysis and Design - CSE3308
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Application architectures
1 SWE Introduction to Software Engineering Lecture 5.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 SWE Introduction to Software Engineering Lecture 11 - Requirements Engineering Processes.
Course Instructor: Aisha Azeem
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements 2.
Application architectures
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 13 Slide 1 Application architectures.
Chapter 6 – Architectural Design Lecture 2 1Chapter 6 Architectural design.
Chapter 1- Introduction
SOFTWARE.
Chapter 9 Moving to Design. The Structured Approach To Designing The Application Architecture Module-an identifiable component of a computer program that.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Chapter 12 Describing Information Systems.
CS 425/625 Software Engineering Legacy Systems
Faculty of Computer & Information Software Engineering Third year
10 ITK261 The traditional approach to design Reading: Chapter 10 Oct 9, 11.
10 The traditional approach to design Hisham Alkhawar.
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Chapter 6 Architectural Design.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
 Repository Model  Client-Server Model  Layered Model  Modular decomposition styles  Object Models  Function Oriented Pipelining  Control Styles.
UHD::3320::CH121 DESIGN PHASE Chapter 12. UHD::3320::CH122 Design Phase Two Aspects –Actions which operate on data –Data on which actions operate Two.
INFO1408 Database Design Concepts Week 15: Introduction to Database Management Systems.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
An Introduction to Software Engineering. Objectives  To introduce software engineering and to explain its importance  To set out the answers to key.
Slide 1 Ch 13 Application architectures Generic architectures that can be configured and adapted to create a system that meets specific requirements Can.
Chapter 9 Web Application Design. Objectives Describe the MVC design pattern as used with Web applications Explain the role and responsibilities of each.
Legacy Systems IS301 – Software Engineering Lecture # 24 – M. E. Kabay, PhD, CISSP Dept of Computer Information Systems Norwich University.
CS223: Software Engineering
Application architectures Advisor : Dr. Moneer Al_Mekhlafi By : Ahmed AbdAllah Al_Homaidi.
ISC321 Database Systems I Chapter 2: Overview of Database Languages and Architectures Fall 2015 Dr. Abdullah Almutairi.
Systems Analysis and Design in a Changing World, Fourth Edition
Application architectures 1. Topics covered In the previous chapter, the discussion of system arcitectures focused on architectural issues such as control,
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.
Databases and DBMSs Todd S. Bacastow January 2005.
CompSci 280 S Introduction to Software Development
Software architecture
CompSci 280 S Introduction to Software Development
Management Movie Management System Customers Databases Vendors
Software Engineering Architectural Design Chapter 6 Dr.Doaa Samy
Software Engineering Architectural Design Chapter 6 Dr.Doaa Samy
Chapter 6 – Architectural Design
Chapter 5 Architectural Design.
Chapter 5 Architectural Design.
Presentation transcript:

1 SWE Introduction to Software Engineering Lecture 21 – Architectural Design (Chapter 13)

2 Lecture Objectives To explain the organization of two fundamental models of business systems – Batch processing; and Transaction processing systems To describe the abstract architecture of resource management systems

3 Generic application architectures Application systems are designed to meet an organisational need. As businesses have much in common, their application systems also tend to have a common architecture that reflects the application requirements. A generic architecture is configured and adapted to create a system that meets specific requirements.

4 Application types Data processing applications Data driven applications that process data in batches without explicit user intervention during the processing. Transaction processing applications Data-centred applications that process user requests and update information in a system database.

5 Application types Event processing systems Applications where system actions depend on interpreting events from the system’s environment. Language processing systems Applications where the users’ intentions are specified in a formal language that is processed and interpreted by the system.

6 Application type examples Data processing systems Billing systems; Payroll systems. Transaction processing systems E-commerce systems; Reservation systems. Event processing systems Word processors; Real-time systems. Language processing systems Compilers; Command interpreters.

7 Data processing systems Systems that are data-centred where the databases used are usually orders of magnitude larger than the software itself. Data is input and output in batches Input: A set of customer numbers and associated readings of an electricity meter; Output: A corresponding set of bills, one for each customer number. Data processing systems usually have an input-process-output structure.

8 Input-process-output model

9 Input-process-output The input component reads data from a file or database, checks its validity and queues the valid data for processing. The process component takes a transaction from the queue (input), performs computations and creates a new record with the results of the computation. The output component reads these records, formats them accordingly and writes them to the database or sends them to a printer.

10 Data-flow diagrams Show how data is processed as it moves through a system. Transformations are represented as round-edged rectangles, data-flows as arrows between them and files/data stores as rectangles.

11 Salary payment DFD

12 Transaction processing systems Process user requests for information from a database or requests to update the database. From a user perspective a transaction is: Any coherent sequence of operations that satisfies a goal; For example - find the times of flights from London to Paris. Users make asynchronous requests for service which are then processed by a transaction manager.

13 Transaction processing

14 ATM system organisation

15 Transaction processing middleware Transaction management middleware or teleprocessing monitors handle communications with different terminal types (e.g. ATMs and counter terminals), serialises data and sends it for processing. Query processing takes place in the system database and results are sent back through the transaction manager to the user’s terminal.

16 Transaction management

17 Key points Generic models of application architectures help us understand and compare applications. Important classes of application are data processing systems, transaction processing systems, event processing systems and language processing system. Data processing systems operate in batch mode and have an input-process-output structure. Transaction processing systems allow information in a database to be remotely accessed and modified by multiple users.