Bài giảng Kiến trúc phần mềm: Các tiêu chí và yêu cầu về Kiến trúc phần mềm - PGS.TS. Trần Minh Triết
Số trang: 41
Loại file: pdf
Dung lượng: 561.26 KB
Lượt xem: 16
Lượt tải: 0
Xem trước 5 trang đầu tiên của tài liệu này:
Thông tin tài liệu:
Bài giảng Kiến trúc phần mềm - Các tiêu chí và yêu cầu về Kiến trúc phần mềm cung cấp cho người học các kiến thức: What are quality attributes, performance, performance throughput, performance response time, response time,... Mời các bạn cùng tham khảo.
Nội dung trích xuất từ tài liệu:
Bài giảng Kiến trúc phần mềm: Các tiêu chí và yêu cầu về Kiến trúc phần mềm - PGS.TS. Trần Minh Triết Trường Đại học Khoa Học Tự Nhiên Khoa Công Nghệ Thông Tin Bộ môn Công Nghệ Phần Mềm CTT526 - Kiến trúc phần mềm Các tiêu chí và yêu cầu về Kiến trúc phần mềm PGS.TS. Trần Minh Triết tmtriet@fit.hcmus.edu.vn Version 1.0 CuuDuongThanCong.com https://fb.com/tailieudientucntt Nội dung của bài giảng sử dụng: Session 3: Quality Attributes trong bộ slide Software Architecture Essential của GS. Ian Gorton Software Engineering Institute Carnegie Mellon University 2 CuuDuongThanCong.com https://fb.com/tailieudientucntt What are Quality Attributes Often know as –ilities Reliability Availability Portability Scalability Performance (!) Part of a system‟s NFRs “how” the system achieves its functional requirements 3 CuuDuongThanCong.com https://fb.com/tailieudientucntt Quality Attribute Specification Architects are often told: “My application must be fast/secure/scale” Far too imprecise to be any use at all Quality attributes (QAs) must be made precise/measurable for a given system design, e.g. “It must be possible to scale the deployment from an initial 100 geographically dispersed user desktops to 10,000 without an increase in effort/cost for installation and configuration.” 4 CuuDuongThanCong.com https://fb.com/tailieudientucntt Quality Attribute Specification QA‟s must be concrete But what about testable? Test scalability by installing system on 10K desktops? Often careful analysis of a proposed solution is all that is possible “It‟s all talk until the code runs” 5 CuuDuongThanCong.com https://fb.com/tailieudientucntt Performance Many examples of poor performance in enterprise applications Performance requires a: Metric of amount of work performed in unit time Deadline that must be met Enterprise applications often have strict performance requirements, e.g. 1000 transactions per second 3 second average latency for a request 6 CuuDuongThanCong.com https://fb.com/tailieudientucntt Performance - Throughput Measure of the amount of work an application must perform in unit time Transactions per second Messages per minute Is required throughput: Average? Peak? Many system have low average but high peak throughput requirements 7 CuuDuongThanCong.com https://fb.com/tailieudientucntt Throughput Example C PU % MST (ms p) 300 250 200 150 100 50 0 0 5 10 15 20 # o f th r e a d s Throughput of a message queuing system Messages per second (msp) Maximum sustainable throughput (MST) Note throughput changes as number of receiving threads increases 8 CuuDuongThanCong.com https://fb.com/tailieudientucntt Performance - Response Time measure of the latency an application exhibits in processing a request Usually measured in (milli)seconds Often an important metric for users Is required response time: Guaranteed? Average? E.g. 95% of responses in sub-4 seconds, and all within 10 seconds 9 CuuDuongThanCong.com https://fb.com/tailieudientucntt Response Time Example shows response time distribution for a J2EE application 10 CuuDuongThanCong.com https://fb.com/tailieudientucntt Performance - Deadlines „something must be completed before some specified time‟ Payroll system must complete by 2am so that electronic transfers can be sent to bank Weekly accounting run must complete by 6am Monday so that figures are available to management Deadlines often associated with batch jobs in IT systems. 11 CuuDuongThanCong.com https://fb.com/tailieudientucntt Something to watch for … What is a Transaction? Message? Request? All are application specific measures. System must achieve 100 mps throughput BAD!! System must achieve 100 mps peak throughput for PaymentReceived messages GOOD!!! 12 Cuu ...
Nội dung trích xuất từ tài liệu:
Bài giảng Kiến trúc phần mềm: Các tiêu chí và yêu cầu về Kiến trúc phần mềm - PGS.TS. Trần Minh Triết Trường Đại học Khoa Học Tự Nhiên Khoa Công Nghệ Thông Tin Bộ môn Công Nghệ Phần Mềm CTT526 - Kiến trúc phần mềm Các tiêu chí và yêu cầu về Kiến trúc phần mềm PGS.TS. Trần Minh Triết tmtriet@fit.hcmus.edu.vn Version 1.0 CuuDuongThanCong.com https://fb.com/tailieudientucntt Nội dung của bài giảng sử dụng: Session 3: Quality Attributes trong bộ slide Software Architecture Essential của GS. Ian Gorton Software Engineering Institute Carnegie Mellon University 2 CuuDuongThanCong.com https://fb.com/tailieudientucntt What are Quality Attributes Often know as –ilities Reliability Availability Portability Scalability Performance (!) Part of a system‟s NFRs “how” the system achieves its functional requirements 3 CuuDuongThanCong.com https://fb.com/tailieudientucntt Quality Attribute Specification Architects are often told: “My application must be fast/secure/scale” Far too imprecise to be any use at all Quality attributes (QAs) must be made precise/measurable for a given system design, e.g. “It must be possible to scale the deployment from an initial 100 geographically dispersed user desktops to 10,000 without an increase in effort/cost for installation and configuration.” 4 CuuDuongThanCong.com https://fb.com/tailieudientucntt Quality Attribute Specification QA‟s must be concrete But what about testable? Test scalability by installing system on 10K desktops? Often careful analysis of a proposed solution is all that is possible “It‟s all talk until the code runs” 5 CuuDuongThanCong.com https://fb.com/tailieudientucntt Performance Many examples of poor performance in enterprise applications Performance requires a: Metric of amount of work performed in unit time Deadline that must be met Enterprise applications often have strict performance requirements, e.g. 1000 transactions per second 3 second average latency for a request 6 CuuDuongThanCong.com https://fb.com/tailieudientucntt Performance - Throughput Measure of the amount of work an application must perform in unit time Transactions per second Messages per minute Is required throughput: Average? Peak? Many system have low average but high peak throughput requirements 7 CuuDuongThanCong.com https://fb.com/tailieudientucntt Throughput Example C PU % MST (ms p) 300 250 200 150 100 50 0 0 5 10 15 20 # o f th r e a d s Throughput of a message queuing system Messages per second (msp) Maximum sustainable throughput (MST) Note throughput changes as number of receiving threads increases 8 CuuDuongThanCong.com https://fb.com/tailieudientucntt Performance - Response Time measure of the latency an application exhibits in processing a request Usually measured in (milli)seconds Often an important metric for users Is required response time: Guaranteed? Average? E.g. 95% of responses in sub-4 seconds, and all within 10 seconds 9 CuuDuongThanCong.com https://fb.com/tailieudientucntt Response Time Example shows response time distribution for a J2EE application 10 CuuDuongThanCong.com https://fb.com/tailieudientucntt Performance - Deadlines „something must be completed before some specified time‟ Payroll system must complete by 2am so that electronic transfers can be sent to bank Weekly accounting run must complete by 6am Monday so that figures are available to management Deadlines often associated with batch jobs in IT systems. 11 CuuDuongThanCong.com https://fb.com/tailieudientucntt Something to watch for … What is a Transaction? Message? Request? All are application specific measures. System must achieve 100 mps throughput BAD!! System must achieve 100 mps peak throughput for PaymentReceived messages GOOD!!! 12 Cuu ...
Tìm kiếm theo từ khóa liên quan:
Bài giảng Kiến trúc phần mềm Kiến trúc phần mềm Performance throughput Performance response time Response timeTài liệu liên quan:
-
Đề cương chi tiết học phần Vi xử lý
12 trang 298 0 0 -
Giáo trình Công nghệ phần mềm nâng cao: Phần 1
151 trang 198 0 0 -
Giáo trình môn học: Cấu trúc máy tính (Trình độ: Trung cấp/cao đẳng)
103 trang 84 0 0 -
Tập bài giảng Kiến trúc máy tính
227 trang 51 0 0 -
Bài giảng Phân tích thiết kế phần mềm: Chương 10 - Trường ĐH Ngoại ngữ - Tin học TP.HCM
8 trang 30 0 0 -
Bài giảng Bộ môn Công nghệ phần mềm - Bài 3: Kiến trúc phần mềm
27 trang 30 0 0 -
Giáo trình Kiến trúc và thiết kế phần mềm: Phần 1
93 trang 29 0 0 -
Hello World: Bộ kiểm thử hiệu năng Rational
36 trang 28 0 0 -
Cài đặt IBM Rational Team Concert Express-C
11 trang 28 0 0 -
Giáo trình Kiến trúc và thiết kế phần mềm: Phần 2
117 trang 27 0 0