1 / 77

WARNING

WARNING. These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010. They may not show up well on other PowerPoint versions . You can download PowerPoint 2010 viewer from here .

blanca
Download Presentation

WARNING

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. WARNING • These slides are not optimized for printing or exam preparation. These are for lecture delivery only. • These slides are made for PowerPoint 2010. They may not show up well on other PowerPoint versions. You can download PowerPoint 2010 viewer from here. • These slides contain a lot of animations. For optimal results, watch in slideshow mode.

  2. WAITING WAITING WAITING WAITING WAITING WAITING TEAMMATE WAITING WAITING TEAMMATE working

  3. But not like scrum

  4. The View from the Top: Architecture CS2103/T, Lecture 4, Part 1, [Feb 7, 2014]

  5. Architecture Architecture Architecture Architecture Architecture Architecture Architecture Architecture Architecture The View from the Top: Architecture Architecture Architecture Architecture CS2103/T, Lecture 4, Part 1, [Feb 7, 2014]

  6. Architecture • + (important technical decisions)

  7. Architecture • + (important technical decisions)

  8. TEAMMATES

  9. Architecture • + (important technical decisions)

  10. Architecture a c d b

  11. Architecture a c d b

  12. The architect

  13. The architect

  14. The architect

  15. Architecture a c d b

  16. styles Architecture a c d b

  17. styles Architecture a c d b

  18. styles Architecture n-tier | Client-server| Transaction processing | service-oriented | pipes and filters

  19. styles Architecture n-tier | Client-server| Transaction processing | service-oriented | pipes and filters GUI Console FTP Access Tier n UI Encryption Tier 2 Logic Network Protocol Tier 1 Storage Hardware Access Tier 0

  20. styles Architecture n-tier | Client-server| Transaction processing | service-oriented | pipes and filters Client n Client 1 Client 2 Server Mobile Browser Game Client 2 Game Client 1 Browser 2 Browser 1 Network Web Game Server Web Server

  21. styles Architecture n-tier | Client-server| Transaction processing | service-oriented | pipes and filters T1 Transaction executor 1 T5 Transaction creator 1 T2 T4 Dispatcher Transaction creator n T3 T6 Transaction executor n A1 Account Manager A5 Teller1 A2 C4 Dispatcher Teller n C3 Currency Mgt System A6

  22. styles Architecture n-tier | Client-server| Transaction processing | service-oriented | pipes and filters xml data eBookShop Internet xml data Web services Internet xml data

  23. styles Architecture n-tier | Client-server| Transaction processing | service-oriented | pipes and filters

  24. Architecture a c d b

  25. Architecture a c d API [Application Programming Interface] b

  26. UI A C B

  27. UI A C B

  28. UI A C B

  29. UI A C B

  30. Define APIs systematically to match features UI A C B

  31. System: Minesweeper Use case: 01 - play game Actors: Player MSS: 1. Player starts a new game. 2. Minesweeper shows the mine field with all cells initially hidden. 3. Player marks or clears a hidden cell. 4. Minesweeper shows the updated mine field. Steps 3-4 are repeated until the game is either won or lost. 5. Minesweeper shows the result. Use case ends.

  32. System: Minesweeper Use case: 01 - play game Actors: Player MSS: 1. Player starts a new game. 2. Minesweeper shows the mine field with all cells initially hidden. 3. Player marks or clears a hidden cell. 4. Minesweeper shows the updated mine field. Steps 3-4 are repeated until the game is either won or lost. 5. Minesweeper shows the result. Use case ends. The architect

  33. System: Minesweeper Use case: 01 - play game Actors: Player MSS: 1. Player starts a new game. 2. Minesweeper shows the mine field with all cells initially hidden. 3. Player marks or clears a hidden cell. 4. Minesweeper shows the updated mine field. Steps 3-4 are repeated until the game is either won or lost. 5. Minesweeper shows the result. Use case ends.

  34. UI MSLogic History Storage

  35. UI Sequence Diagrams [interactions between components for a given scenario]

  36. :UI operation returned value Sequence Diagrams [interactions between components for a given scenario]

  37. :UI

  38. :UI

  39. :UI

  40. :UI

  41. :UI

More Related