1 / 24

Project 2 Presentations CS554 – Designs for Software and Systems

Project 2 Presentations CS554 – Designs for Software and Systems. Team HAND – Seokin Hong, Gieil Lee, Jesung Kim, Yebin Lee Department of Computer Science, KAIST. Contents. Requirements Quality Attribute (Utility Tree) Rating Candidate Architecture Style Pipe-filter Client-server

nam
Download Presentation

Project 2 Presentations CS554 – Designs for Software and Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project 2 PresentationsCS554 – Designs for Software and Systems Team HAND – Seokin Hong, Gieil Lee, Jesung Kim, Yebin Lee Department of Computer Science, KAIST

  2. Contents • Requirements • Quality Attribute (Utility Tree) • Rating • Candidate Architecture Style • Pipe-filter • Client-server • Scenarios Analysis • Architectural Analysis • Rating • Architecture Overview

  3. Requirements – Quality Attribute (Utility Tree) Response time Throughput Performance Deadline time Latency Utility Modifiability Prevent ripple events Availability Repair time Built-in monitor Testability

  4. Requirements – Quality Attribute (Utility Tree) When the fault occurs, fault protection system invoked asynchronously at any time [H, L] Response time [M, L] Upper layer component checks parameter of lower layer components Throughput Performance Fault occurs when the critical function is running, the fault protection system responses within specific time [H, H] Deadline time In order to check parameter, a component accesses DB for fetching predefined operating range value [H, L] Latency

  5. Requirements – Quality Attribute (Utility Tree) Fault protection software can be added into existing fault protection software or replaced or eliminated [M, M] Prevent ripple events Modifiability Verification of fault protection system is performed by the combination of inspection, simulation, and analysis [M, H] Testability Built-in monitor [H, M] Fault protection system tests itself for detecting its fault Availability Repair time

  6. Requirements – Rating • Quality Attribute Rating

  7. Candidate Architecture Style • Pipe-filter • Asynchronous, concurrent, Independent • Data stream • Non-recursive, pipeline • Client/Server • Asynchronous / synchronous • Performance, Modifiability, Reliability • N-tier

  8. Scenarios Analysis • Performance – Throughput

  9. Scenarios Analysis • Performance – Throughput

  10. Scenarios Analysis • Performance – Latency

  11. Scenarios Analysis • Performance – Latency

  12. Scenarios Analysis • Performance – Response time

  13. Scenarios Analysis • Performance – Response time

  14. Scenarios Analysis • Performance – Deadline time

  15. Scenarios Analysis • Performance – Deadline time

  16. Scenarios Analysis • Modifiability – Prevent ripple events

  17. Scenarios Analysis • Modifiability – Prevent ripple events

  18. Scenarios Analysis • Testability – Built-in monitor

  19. Scenarios Analysis • Testability – Built-in monitor

  20. Scenarios Analysis • Availability – Repair time

  21. Scenarios Analysis • Availability – Repair time

  22. Rating • Measurement metrics • + = 3, - = 1 • Performance = x 1, Availability = x 0.9 • Modifiability = x 0.8, Testability = x 0.7

  23. Architecture Overview– client / sever • Client-server Architecture Approach

  24. Thank you!

More Related