The Intersection of Computer Interaction and Software Models A “5 by 5” Non-functional Performance Matrix Tom Hill Summer 2005 CS 6362.

Slides:



Advertisements
Similar presentations
PCT303 – Content Publishing in SharePoint Eugene Rosenfeld Black Blade Associates
Advertisements

09/04/2015Unit 2 (b) Back-Office processes Unit 2 Assessment Criteria (b) 10 marks.
Chapter 2 Operating System Overview Operating Systems: Internals and Design Principles, 6/E William Stallings.
CS 345 Computer System Overview
Page 1 More information at; gaddsoftware.comgaddsoftware.com.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
Chapter 3 Operating Systems. Chapter 3 Operating Systems 3.1 The Evolution of Operating Systems 3.1 The Evolution of Operating Systems 3.2 Operating System.
1 SWE Introduction to Software Engineering Lecture 21 – Architectural Design (Chapter 13)
Database Management: Getting Data Together Chapter 14.
Sergey Belov, LIT JINR 15 September, NEC’2011, Varna, Bulgaria.
Leveraging User Interactions for In-Depth Testing of Web Applications Sean McAllister, Engin Kirda, and Christopher Kruegel RAID ’08 1 Seoyeon Kang November.
Ambient Displays of User Mood Tony Morelli Department of Computer Science, University of Nevada, Reno Abstract: Determining a user’s mood can be a very.
1 Introduction Introduction to database systems Database Management Systems (DBMS) Type of Databases Database Design Database Design Considerations.
Copyright © 2014 Pearson Education, Inc. 1 It's what you learn after you know it all that counts. John Wooden Key Terms and Review (Chapter 6) Enhancing.
CHAPTER 6 ELECTRONIC DATA PROCESSING SYSTEMS
CHAPTER 11 Managerial Support Systems. CHAPTER OUTLINE  Managers and Decision Making  Business Intelligence Systems  Data Visualization Technologies.
Computer System Lifecycle Chapter 1. Introduction Computer System users, administrators, and designers are all interested in performance evaluation. Whether.
D ATA, D ATABASE, DBMS, DBMS SOFTWARE, R ELATION, A PPLICATION, ENVIRONMENT, BENEFITS. Week 8 Mr.Mohammed Rahmath.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 13 Slide 1 Application architectures.
Chapter 5 Business Intelligence: Data Warehousing, Data Acquisition, Data Mining, Business Analytics, and Visualization.
Chapter 2 Operating System Overview Patricia Roy Manatee Community College, Venice, FL ©2008, Prentice Hall Operating Systems: Internals and Design Principles,
1 Requirements Analysis and Design Engineering Southern Methodist University CSE 7313.
CS 4310: Software Engineering Lecture 3 Requirements and Design.
Beyond DHTML So far we have seen and used: CGI programs (using Perl ) and SSI on server side Java Script, VB Script, CSS and DOM on client side. For some.
Chapter 10 State Machine Diagrams
Type of Software There are two main types of software They are System software Application software Hardware System Software (OS) Application Software.
Lecture 7 Interaction. Topics Implementing data flows An internet solution Transactions in MySQL 4-tier systems – business rule/presentation separation.
Transaction Processing System
FatMax Licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.5 LicenseCreative Commons Attribution-NonCommercial-ShareAlike 2.5.
Transaction Processing System  Business Transactions are certain events that occur routinely in a business firm.  A transaction is a set of activities.
7/5: Ch. 2 Fundamentals of IS What is a system? What is an information system?
◦ What is an Operating System? What is an Operating System? ◦ Operating System Objectives Operating System Objectives ◦ Services Provided by the Operating.
Configuration Management (CM)
Tutorial DFD Cap I. Najwa AlGhamdi. context diagram  Why context diagram ?  To know Who will interact with system. What's the main input and output.
Faculty of Computer & Information
1 Categories of data Operational and very short-term decision making data Current, short-term decision making, related to financial transactions, detailed.
 Repository Model  Client-Server Model  Layered Model  Modular decomposition styles  Object Models  Function Oriented Pipelining  Control Styles.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 9 Enabling the Organization – Decision Making.
1 Topics about Data Warehouses What is a data warehouse? How does a data warehouse differ from a transaction processing database? What are the characteristics.
Use Cases -Use Case Diagram Chapter 3 1. Where are we? 2 Analysis Chapters Ch 2Investigating System Requirements Ch 3Use Cases Ch 4Domain Modeling Ch.
Data resource management
Next Back MAP 3-1 Management Information Systems for the Information Age Copyright 2002 The McGraw-Hill Companies, Inc. All rights reserved Chapter 3 Data.
By N.Gopinath AP/CSE. There are 5 categories of Decision support tools, They are; 1. Reporting 2. Managed Query 3. Executive Information Systems 4. OLAP.
1 Chapter 5 Modeling System Requirements Finding the Use Cases Page
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
Module 9 Planning and Implementing Monitoring and Maintenance.
By Tom and James. Hardware is a physical part of the system that you can pick up and move. There are two types of hardware, external and internal. External.
Slide 1 Ch 13 Application architectures Generic architectures that can be configured and adapted to create a system that meets specific requirements Can.
Data Resource Management Agenda What types of data are stored by organizations? How are different types of data stored? What are the potential problems.
UML - Development Process 1 Software Development Process Using UML.
CSC 480 Software Engineering Lecture 17 Nov 4, 2002.
CS4315A. Berrached:CMS:UHD1 Introduction to Operating Systems Chapter 1.
Business Models and Information Flow 10 th Meeting Course Name: Business Intelligence Year: 2009.
Oracle 8i Data Warehousing (chapter 1, 2) Data Warehousing Lab. 석사 1 학기 HyunSuk Jung.
Business Intelligence Overview. What is Business Intelligence? Business Intelligence is the processes, technologies, and tools that help us change data.
Introduction to Business Analytics
Distributed Systems Architectures. Topics covered l Client-server architectures l Distributed object architectures l Inter-organisational computing.
Section 10.1 Define scripting
Use Cases -Use Case Diagram
Transaction processing systems
Information Technology Deanship
Introduction to Operating System (OS)
Chapter 8: Modelling Interactions and Behaviour UML Activity Diagram
Overview of Databases and Transaction Processing
Use Cases & Use Case Diagrams
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Databases and Information Systems
CHAPTER 6 ELECTRONIC DATA PROCESSING SYSTEMS
Chapter 2 Operating System Overview
Presentation transcript:

The Intersection of Computer Interaction and Software Models A “5 by 5” Non-functional Performance Matrix Tom Hill Summer 2005 CS 6362

Page 2 Human/Computer Interaction and Software Models Computer Interaction A. Transaction B. Event C. Analytical D. Decision E. Batch Software Reference 1. Data-Centered 2. Data-flow 3. Virtual Machine 4. Call and Return 5. Independent Components

Page 3 A. Transaction Interaction Model ATM Model Attributes: Scenario: user enters request, user waits for the system to respond, user takes next step Performance Metric: response time, sub-second or seconds Dependencies: transactions structured into pre- defined execution sequences Usage: credit card processing, shopping sites, automatic teller machines

Page 4 B. Event Interaction Model Intrusion Detection Events Model Attributes: Scenario: external event triggers, processing steps or other events, user not required, information collected for analysis Performance Metric: event response time, number of events, and trigger limits – dictated by business process Dependencies: state model used to define Usage: security detection, problem management, real-time audit

Page 5 C. Analytical Interaction Model Multidimensional Views Model Attributes: Scenario: data pre-processed for specialized database, user submits request for analysis and report, system performs complex calculations, user reviews analysis Performance Metric: throughput time to pre-process data and analysis time, minutes to hours - dictated by business process Dependencies: close coordination required between data pre-processing and analysis request Usage: OLAP, cluster analysis, statistical analysis

Page 6 D. Decision Interaction Model Intelligent Decisions Model Attributes: Scenario: system automatically gathers and assembles data, user views the data and makes decisions Performance Metric: display response time, sub-second or seconds, gathering and assembling throughput time from seconds to hours Dependencies: an operational data store must be updated prior to the gathering and assembling operation Usage: executive dashboards, business intelligence, real-time stock ticker

Page 7 E. Batch Interaction Model Batch Scripts Model Attributes: Scenario: No user interaction, however, user defines a pre-determined sequence of processing steps and, in some cases, the time the system starts execution Performance Metric: throughput time, minutes to hours Dependencies: a pre-defined execution sequence and some level of conditional execution is provided by the scripting language Usage: billing systems, system and database backup operations

Page 8 1. Data-centered Reference Model

Page 9 2. Data-flow Reference Model

Page Virtual Machine Reference Model

Page Call and Return Reference Model

Page Independent Components Reference Model

Page 13 A “5 x 5” Non-functional Performance Matrix A. Transaction B. Event C. Analytical D. Decision E. Batch 1. Data-Centered 2. Data-flow 3. Virtual Machine 4. Call and Return 5. Independent Components Computer Interaction Software Reference Throughput time = T Response time = R Good = + Poor = - T R+ T++ R- T- R T R+ T R+ R-- R- R+R++ R+R-- R- R+ T+T++ T- TT T+T++ T- T+