1 / 18

Software architecture for the MP4 system

Software architecture for the MP4 system. Group 3. Gati M. Elena S. Alena K. Egor B. Lucian V. 1 / 18. Introduction. SW Architecture. Contents:. Business model Initial model System architecture Logic view - Components (static) - Interactions (dynamic)

nishan
Download Presentation

Software architecture for the MP4 system

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. Software architecture for the MP4 system Group 3 Gati M.Elena S. Alena K. Egor B. Lucian V. 1 / 18

  2. Introduction SW Architecture Contents: • Business model • Initial model • System architecture • Logic view - Components (static) - Interactions (dynamic) • Process view - Main tasks - Component state charts - Data flows • Deployment + Implementation - Resource utilization • Architecture Evaluation - SAAM , ATAM • Conclusions • Questions 2 / 18

  3. Introduction 3 / 18

  4. Record houses Marketing Distribution rights Maintainer Payment in % from each sold song Muzak owner Money Money Bank AUDIO - CDs Payment Shop owner Shop owner Shop owner Music to download Payment for downloaded songs Music to download Payment for downloaded songs Business model 4 / 18

  5. Initial Model 5 / 18

  6. MP3 MP3 MP3 JPG JPG Loading Server Operator Player $$$ Point (2x) (10x) $$$ MP3 JPG $$$ JPG $$$ Cass Printer DB System architecture • Design Decisions: • Player – Loading point communication • Pre-listening • Transferring songs 6 / 18

  7. Software Architecture 7 / 18

  8. Logic view (static) – Component diagram + use cases Defend Pressing Score 8 / 18

  9. Pre-listening Score + Logic view (dynamic) 9 / 18

  10. Pre-listening Content Manager DBMS Controller DBMS Source Buffer Target Buffer Prelistening Manager PrelistenSong(x) Pass(ball) RequestMusic(x) RetrieveMusic(x) PushData() FillBuffer() Pass(ball) Ack() Ack() Enable() StartTransfer() (After buffer thresholdis reached) Play() readData(x) Shoot (ball) ackReadData(x) Logic view (dynamic) – Interaction diagram Score 10 / 18

  11. Prelisten / Preview Paying Selecting Managing player’scontent Browsing Pressing Score Print Download Defend Statistics generation Checkpoint managing Acquire new material Backup generation Process view (main tasks) 11 / 18

  12. DBMS Controller Priority high Pas Shoot Look at the referee Priority low Process view (Component state charts) Radio -> TV 12 / 18

  13. Deployment + Implementation Resource utilization Goal Middlefield Attack 13 / 18

  14. Architecture evaluation : SAAM Scenarios: 1.Scale the loading points from 10 to 20 or more Direct 2.Change the audio encoding method from MP3 to MP4 • This scenario affects the number of components that indicate low cohesion and high coupling • This change in the system brings high benefits for system but requires high effort for realization (9 person-week) 14 / 18

  15. Architecture evaluation : ATAM • Utility tree: • 6 HW failures • 3 network failures • 4 SW failures • 3 Risks & 3 Non-risks • 3 Sensitivity points • 3 tradeoffs Fault hypothesis: 22 possible crashes Change-case scenarios: 6 most important CASE 1 Stimulus: failure of main server Response: traffic is redirected to backup server in 10 sec Risk: backup server failures is a single point of failure CASE 2 Stimulus: connection failure during payment Response: status of transaction will be restored Risk: if Content Manager’s failure happens, status of payment transaction can be lost 15 / 18

  16. Conclusions for ATAM • NFR are satisfied • availability is met • Derived risks are second-order phenomena • affect no first order components • concern components whose purpose is to prevent different failures (backup components) 16 / 18

  17. Conclusions • 2 minutes requirement is met • Architecture is scalable with respect to number of loading points (SAAM) • The change-case “from MP3 to MP4” is possible with extra effort • Availability requirement is met (ATAM) • There are only second order risks 17 / 18

  18. Questions and Answers 18 / 18

More Related