Lecture 92 Test 1 – Take Home Post mortem

Slides:



Advertisements
Similar presentations
ICT AS A level New Specification Unit IT1 Information Systems(AS) Examination 4.2Unit IT2 Presenting Information (AS) Coursework 4.3Unit IT3.
Advertisements

1 Configuring Internet- related services (April 22, 2015) © Abdou Illia, Spring 2015.
Chapter One The Essence of UNIX.
Component Patterns – Architecture and Applications with EJB copyright © 2001, MATHEMA AG Component Patterns Architecture and Applications with EJB JavaForum.
Application architectures
21 21 Web Content Management Architectures Vagan Terziyan MIT Department, University of Jyvaskyla, AI Department, Kharkov National University of Radioelectronics.
CS & ECE Senior Design Project Winter 2008 Karen Davis Chia Han Altan Ferendeci.
Chapter 6 – Architectural Design Lecture 2 1Chapter 6 Architectural design.
© Drexel University Software Engineering Research Group (SERG) 1 Based on the paper by Philippe Kruchten from Rational Software.
CCSB223/SAD/CHAPTER141 Chapter 14 Implementing and Maintaining the System.
T U T O R I A L  2009 Pearson Education, Inc. All rights reserved Bookstore Web Application Introducing Visual Web Developer 2008 Express and the.
Lecture 7 Interaction. Topics Implementing data flows An internet solution Transactions in MySQL 4-tier systems – business rule/presentation separation.
1 MyLicense Log in/Register Login to the MyLicense application with an existing User Account. OR Create a new User Account with the Register link at the.
Recovery-Oriented Computing User Study Training Materials October 2003.
Case Study :. Introduction The ATM network will consist of a large number of ATM machines distributed over a wide geographical area. The network must.
RESTful applications Norman White. REST Representational state transfer Key concepts – Client Server architecture built on transferring resources between.
1 ADP Algebra II End-Of-Course Online Field Test Test Administrator Training September, 2007.
Relational Databases and Transaction Design Lecture 27.
Chapter 1 Introduction to Databases. 1-2 Chapter Outline   Common uses of database systems   Meaning of basic terms   Database Applications  
CS212: Object Oriented Analysis and Design Lecture 32: Use case and Class diagrams.
Representational State Transfer (REST). What is REST? Network Architectural style Overview: –Resources are defined and addressed –Transmits domain-specific.
RESTful Web Services What is RESTful?
CSC 480 Software Engineering High Level Design. Topics Architectural Design Overview of Distributed Architectures User Interface Design Guidelines.
REST By: Vishwanath Vineet.
Component Patterns – Architecture and Applications with EJB copyright © 2001, MATHEMA AG Component Patterns Architecture and Applications with EJB Markus.
CS223: Software Engineering
1 Object-Oriented Static Modeling of the Banking System - III Lecture # 33.
Representational State Transfer COMP6017 Topics on Web Services Dr Nicholas Gibbins –
Chapter 6 : User interface design
Chapter 6: Interoperability
Using Use Case Diagrams
How to Redeem a Cardholder Token in AIM
How to Redeem a Cardholder Token in AIM
Testing Irregularities Web Application System (TIWAS)
How to Redeem a Resource Manager Token in AIM
Software Design and Architecture
Representational State Transfer
CHAPTER 2 CREATING AN ARCHITECTURAL DESIGN.
Chapter 3: Windows7 Part 4.
CSS 422 Education for Service-- tutorialrank.com
Ashish Pandit IT Architect, Middleware & Integration Services
WEB API.
Chapter 7 $ Accounting Bellwork
Ashish Pandit, Louis Zelus, Jonathan Whitman
SAD ::: Spring 2018 Sabbir Muhammad Saleh
Web Application Architectures
Configuring Internet-related services
Chapter 5: Software effort estimation- part 2
Tiers vs. Layers.
Using Use Case Diagrams
A gentle introduction to RESTful APIs
Preparing for Campus Testing
Web Application Architectures
Agenda – week 4 6:00 – 6:05 Questions, announcements, intro
Welcome Traceability Software Integrators
ACIS 3504 Accounting Systems and Controls
ETS – Air Data submission Training
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
REST APIs Maxwell Furman Department of MIS Fox School of Business
RESTful Web Services.
REST på Microsoft-stacken
Agenda – week 3 6:00 – 6:30 Documenting an Architecture Project discussion 6:30 – 7:40 Lecture: Qualities vs functionality 7:40 – 8:00 Break 8:00 – 8:20.
Chapter 5 Architectural Design.
Service-Oriented Computing: Semantics, Processes, Agents
A gentle introduction to RESTful APIs
Web Application Architectures
Web Servers (IIS and Apache)
Chengyu Sun California State University, Los Angeles
Caplink Document Statuses
Information system analysis and design
Presentation transcript:

Lecture 92 Test 1 – Take Home Post mortem CSCE 742 Software Architectures Lecture 92 Test 1 – Take Home Post mortem Topics Questions Grades on take home Grades combined with in-class Comments on each question June 15, 2017

Test 1 – Take Home Summer 2017 1) What is the maximum amount of downtime in a year if one is going to achieve 99.999% (five nines) availability? 2) Page 100 5.1 Write two concrete scenarios: a. one for response measure: Availability percentage and b. one for response measure: time interval when the system must be available 3) Give a 3 or 4 sentence description of REST <Chapter 6> 4) What are the sections of the checklist for the design and analysis process for a quality attribute? (just the names of the 7 sections) 5) What do the annotations used in the Spring Boot tutorial mean? 6) Unix/Linux a. What does the “tree” Linux command do? b. What is a Filter (in Unix/Linux)? c. What is a pipe? 7) What is meant by the term “instrumentation” and why might you do this?

1. What is the maximum amount of downtime in a year if one is going to achieve 99.999% (five nines) availability? Downtime % max = 1-.99999 = 0.00001 Minutes in year = 365 days * 24(hours/day) * 60 (min/hr) = 525600 minutes So max downtime in minutes = 0.00001 * 525600 = 5.256 minutes Comments: should days/yr be 365.25 to average in leap year?

2) Page 100 5. 1 Write two concrete scenarios: a 2)     Page 100 5.1 Write two concrete scenarios: a.     one for response measure: Availability percentage  and b.     one for response measure: time interval when the system must be available

2a concrete scenario for response measure: Availability percentage Any valid user requesting a document printed should have this request satisfied by the document being successfully printed or notified why the request could not be satistifed at least 49 our of 50 requests, i.e. 98% of the time, when the printer is online. i. Source of Stimulus - Any valid User ii. Stimulus - Request to print document iii. Artifact - Printer iv. Environment - Printer is Online v. Response - Document is printed or appropriate error message returned, e.g. "printer out of paper" vi. Response Measurement - Document must be printed at least 98.0% of the time (49 out of 50 requests)

Not a scenario with availability as response measure! A manager asks the development lead what the availability percentage was over the last year of operation for a system. The lead checks the records and gets the cumulative total downtime from the time measured between crashes and successful restarts. The availability percentage was 99.99%. This is reported to the manager. This within the accepted range of availability for the manager.

2b.     one for response measure: time interval when the system must be available A user submits an online banking depoist between the hours of 9am and 5pm EDT and should result in being credited to their account as deposited that same day, the user is notified of the deposit, and the transaction is logged. Online banking deposts outside of this window will be rejected. i. Source of Stimulus - online banking user ii. Stimulus - Submitting a deposit iii. Artifact - Online banking system iv. Environment - Normal banking mode v. Response - If between 9am - 5pm EDT, users account is credited using current date, user is notified, transaction is logged. Othersie deposit request rejected. vi. Response Measurement - System must function properly with no rejected deposits between 9am-5pm EDT. Rejections allowed outise fo 9am-5pm EDT when system is unavailable.

3) Give a 3 or 4 sentence description of REST <Chapter 6>

https://en.wikipedia.org/wiki/Representational_state_transfer

REST -- wikipedia client–server separation of concerns simplifies component implementation, reduces the complexity of connector semantics, improves the effectiveness of performance tuning, and increases the scalability of pure server components. Layered system constraints allow intermediaries—proxies, gateways, and firewalls—to be introduced at various points in the communication without changing the interfaces between components REST enables intermediate processing by constraining messages to be self-descriptive: interaction is stateless between requests, responses explicitly indicate cacheability.[2]

REST Architectural constraints (Wiki) Client-server Stateless - The client–server communication is constrained by no client context being stored on the server between requests. Each request from any client contains all the information necessary to service the request, and session state is held in the client. Cacheable Layered System Code on demand (client-side scripting) Uniform interfaces

4)      What are the sections of  the checklist for the design and analysis process for a quality attribute? (just the names of the 7 sections)

5) What do the annotations used in the Spring Boot tutorial mean?

6) Unix/Linux What does the “tree” Linux command do? What is a Filter (in Unix/Linux)? What is a pipe?

7)      What is meant by the term “instrumentation” and why  might you do this?