West Virginia University Slide 1 Copyright © K.Goseva 2010 CS 736 Software Performance Engineering Comments on Homework #1  Please revise the solution.

Slides:



Advertisements
Similar presentations
Use cases Use-cases are a scenario based technique in the UML which identify the actors in an interaction and which describe the interaction itself A set.
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagram Corrected to match newer conventions.
Actors and use cases Use-case diagram Brief notation Prioritization Fully dressed notation Requirements Functional requirements  Use-cases.
COMP106 Assignment 2 – A new interface design Proposal 6.
Run Run Shaw Library of CityU By CyberFarm2000 (Janice, Winter and Frank)
IT 240 Intro to Desktop Databases Introduction. About this course Design a database: Entity Relation (ER) modeling and normalization techniques Create.
1 Section 4.1 Basics of Counting. 2 Basic Counting Principles: Sum Rule Suppose you have two tasks to perform: –The first task can be done in n 1 ways;
COMP106 Assignment 2 Proposal 11. The Choice of Metaphor The metaphor that I am going to chose is the library. I have decided to use this metaphor because.
1 Real-time requirements  Intro to Software Engineering  Software Development Process Models  Formal methods in software specification  Structured.
Chapter 3 Planning Your Solution
Copyright © , Software Engineering Research. All rights reserved. Creating Responsive Scalable Software Systems Dr. Lloyd G. Williams Software.
Chapter 3 : Software Process and Other Models Juthawut Chantharamalee Curriculum of Computer Science Faculty of Science and Technology, Suan Dusit University.
TK2023 Object-Oriented Software Engineering CHAPTER 6 SYSTEM SEQUENCE DIAGRAMS.
CMPT 275 Software Engineering
CS190/295 Programming in Python for Life Sciences: Lecture 1 Instructor: Xiaohui Xie University of California, Irvine.
Financial Information Management Managing Financial Information Critical Thinking Business Process Modeling WINIT Control Structures Homework.
Mandatory Annual ACE Training Fiscal Year 2011 – 2012.
WEEK 1 CS 361: ADVANCED DATA STRUCTURES AND ALGORITHMS Dong Si Dept. of Computer Science 1.
CSE 1340 Introduction to Computing Concepts Class 2.
Introduction CSE 1310 – Introduction to Computers and Programming
CS223 Algorithms D-Term 2013 Instructor: Mohamed Eltabakh WPI, CS Introduction Slide 1.
CPSC 171 Introduction to Computer Science 3 Levels of Understanding Algorithms More Algorithm Discovery and Design.
Mandatory Annual ACE Training Fiscal Year 2010 – 2011.
Flowchart IDT. What is a flowchart? Visual representation of a flow of data Outline of process or a solution to a problem Outline the basic logic behind.
Information Trapping Subscribing to RSS Feeds or Alerts to Make Research Easier.
1 CMPT 275 Phase: Design. Janice Regan, Map of design phase DESIGN HIGH LEVEL DESIGN Modularization User Interface Module Interfaces Data Persistance.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis Activity (Identifying Objects, Scenarios) Janice Regan,
1 Sub-Phase Low Level Design (cont). Janice Regan, Map of design phase DESIGN HIGH LEVEL DESIGN Modularization User Interface Module Interfaces.
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
CS 338Query Evaluation7-1 Query Evaluation Lecture Topics Query interpretation Basic operations Costs of basic operations Examples Textbook Chapter 12.
Faculty of Computer & Information
C++ Programming Language Lecture 2 Problem Analysis and Solution Representation By Ghada Al-Mashaqbeh The Hashemite University Computer Engineering Department.
CS 858 – Hot Topics in Computer and Communications Security Winter 2009 Introduction.
Get Access to your Online Course Tools Course: Instructor: Office: Hours:
Object Oriented Design Jerry KotubaSYST Object Oriented Methodologies1.
Get Access to your Online Course Tools Course: Instructor: Office: Hours:
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour UML Sequence Diagram.
How Computers Work in Simple english Dr. John P. Abraham Professor UTPA.
DESIGN PART 2: OBJECT-LEVEL SEQUENCE DIAGRAMS WITH AN EXAMPLE OF COMPOSITION BTS430 Systems Analysis and Design using UML.
1 Section 2.1 Algorithms. 2 Algorithm A finite set of precise instructions for performing a computation or for solving a problem.
Library Guide: Borrowing eBooks. Take some time to browse the Digital Catalogue:
IGCSE ICT Stock Control.
ECG INTEGRATION MAC600 SD Card – EMIS WEB Intelligent Integration GE MAC600 ECG.
The Hashemite University Computer Engineering Department
Specifying the Interactions Builds on agent types and scenario descriptors Interaction Diagrams( IDs) involve –Replacing each functionality with the agent.
Sequential Processing to Update a File Please use speaker notes for additional information!
Chapter 15 Running Time Analysis. Topics Orders of Magnitude and Big-Oh Notation Running Time Analysis of Algorithms –Counting Statements –Evaluating.
Database Applications (15-415) DBMS Internals- Part III Lecture 13, March 06, 2016 Mohammad Hammoud.
Software Engineering, COMP201 Slide 1 Software Engineering CSE470.
Get Access to your Online Course Tools
Adding animations. To add an animations to text or picture you have to click on the text or animation and on the top navigation bar click on animation.
Design methods: JSP and JSD†
Start at 17th March 2012 end at 31th March 2012
Get Access to your Online Course Tools
CS190/295 Programming in Python for Life Sciences: Lecture 1
Register training Using the college register system
Get Access to your Online Course Tools
Please use speaker notes for additional information!
Get Access to your Online Course Tools
TransCAD Vehicle Routing 2018/11/29.
Algorithm Discovery and Design
Get Access to your Online Course Tools
Get Access to your Online Course Tools
Get Access to your Online Course Tools
Get Access to your Online Course Tools
Homework Reading Machine Projects Labs
Trevor Brown DC 2338, Office hour M3-4pm
Lecture 8 Object Concepts
Get Access to your Online Course Tools
Presentation transcript:

West Virginia University Slide 1 Copyright © K.Goseva 2010 CS 736 Software Performance Engineering Comments on Homework #1  Please revise the solution of your Homework 1 by following the comments given on your assignment and on the following slides  Include an alternative (i.e., case node in the software execution model) to model the possibility that the borrows ID is not authorized  Reassign the software resources as needed  Correct the solution of the model  Provide the corrected software execution model with the solution of Homework 3 (to be assigned Sept 30, 2010)  If you have any questions  Stop by my office during office hours (Tuesday & Thursday 2:00 – 3:00 pm)  Send me an . I do my best to check my as often as possible and get back to you

West Virginia University Slide 2 Copyright © K.Goseva 2010 CS 736 Software Performance Engineering Comments on Homework #1  On the use case model  Borrower does not interact directly with the system for “check-out”, “return”, “add” or “remove book”  Borrower interacts with the “search book” use case  DB may be added as an actor or assumed to be part of the system. Either way, there should be steps for some use cases (e.g., “check-out” that update book’s and/or borrower’s records  System admin may be added as an actor (not necessary)

West Virginia University Slide 3 Copyright © K.Goseva 2010 CS 736 Software Performance Engineering Comments on Homework #1  On the scenario & sequence diagram  Write a scenario in some sort of pseudo code  Develop an UML sequence diagram using the standard notation  Include loop for checking-out more than one book (in our example it is assumed exactly three books)  Scanning and authorization of the borrowers card is dome only once (not for each book, i.e., it is not part of the loop)  Have to include DB as an object or as part of the ‘Library system’  May have other devices, such as card reader

West Virginia University Slide 4 Copyright © K.Goseva 2010 CS 736 Software Performance Engineering Comments on Homework #1  On the software execution model  Have to correspond to the sequence diagram  Follow the standard notation  On the assignments of software resources  Have to include assignment to software resources first  Include delay in steps that require response from the human or some slow, mechanical operation such as Scanning borrowers ID or Scanning book  In steps that only require computer operations delays are not needed in most cases  The other resources such as DB access or Network access will account for the slower operations

West Virginia University Slide 5 Copyright © K.Goseva 2010 CS 736 Software Performance Engineering Comments on Homework #1  Example for assignment of software resources  Authorize borrower’s ID needs more CPU work units than Scan borrower’s ID  No DB access is needed for Scan borrower’s ID since the DB is accessed when the authorization is done (e.g., in the Authorize borrower’s ID operation)  Delay in the Scan borrower’s ID step has to be larger than the delay (if any) assigned to the Authorize borrower’s ID since it includes human/computer interaction and slow, mechanical device  In most cases assigning delay to steps such as Authorize borrower’s ID is not needed since the slow disk and network operations usually are accounted for through software resources such as DB and Network Work unit1 DB0 Delay3 Work unit2 DB2 Delay0 Scan borrower’s IDAuthorize borrower’s ID

West Virginia University Slide 6 Copyright © K.Goseva 2010 CS 736 Software Performance Engineering Comments on Homework #1  On the solution of the software execution model  Do not simply sum up the values. USE THE REDUCTION RULES  Multiply the values for the steps in the loop with the number of times the loop is executed  In cases of other structures (e.g., case structure which represents alternative or optional steps) estimate best/worst/average time  Since Software execution model provides input to the System execution model, it is better to first estimate the Total for each hardware resource and then multiply with the Service times and sum  This way you will have the visit counts and service times, that is, the demands for each hardware resource. These are inputs for the System execution model.