Advertisement
Guest User

Untitled

a guest
Nov 19th, 2018
73
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.58 KB | None | 0 0
  1. Chapter 2
  2.  
  3. • A decomposition view shows how responsibilities are allocated across modules and submodules.
  4. • A uses view shows how modules depend on one another. This view helps achieve incremental development and is especially suitable for performing change-impact analysis.
  5. • A generalization view relates modules by showing how one is a generalization or specialization of the other. This view is widely used in object-oriented systems, where inheritance is used to exploit commonality among modules.
  6. • A layered view divides a system into groups of modules that provide cohesive responsibilities. These groups are called layers and relate to each other unidirectionally by the allowed-to-use relation. A layered design helps a system achieve portability and modifiability.
  7. • An aspects view shows special modules called aspects, which are responsible for crosscutting concerns. This view is particularly useful if the system implementation is going to use AOP.
  8. • A data model view describes the structure of the data used in the system in terms of data entities and their relationships. It guides implementation and helps to improve performance and modifiability in data-centric systems.
  9.  
  10. Chapter 3 Component and connector views
  11.  
  12. • Client-server connectors allow a set of concurrent clients to retrieve data synchronously via service requests. This variant of the client-server style supports transparent failover to a backup server.
  13. • The database access connector supports transactional, authenticated access for reading, writing, and monitoring the database.
  14. • The publish-subscribe connector supports asynchronous event announcement and notification.
  15.  
  16. Components have interfaces called ports
  17.  
  18. Connectors have roles, which are its interfaces, defining the ways in which the connector may be used by components to carry out interaction. For example, a client-server connector might have invokes-services and provides-services roles. A pipe might have writer and reader roles. Like component ports, connector roles differ from module interfaces in that they can be replicated, indicating how many components can be involved in its interaction. A publish-subscribe connector might have many instances of the publisher and subscriber roles.
  19.  
  20. Chapter 4
  21.  
  22. • Call-return styles. Styles in which components interact through synchronous invocation of capabilities provided by other components.
  23. • Data flow styles. Styles in which computation is driven by the flow of data through the system.
  24. • Event-based styles. Styles in which components interact through asynchronous events or messages.
  25. • Repository styles. Styles in which components interact through large collections of persistent, shared data.
  26.  
  27. Pipe and filter
  28. • Improving reuse due to the independence of filters
  29. • Improving throughput with parallelization of data processing
  30. • Simplifying reasoning about overall behavior
  31.  
  32. C and S
  33. Promoting modifiability and reuse by factoring out common services
  34. • Improving scalability and availability in case server replication is in place
  35. • Analyzing dependability, security, and throughput
  36.  
  37. P2p
  38. Providing enhanced availability
  39. • Providing enhanced scalability
  40. • Enabling highly distributed systems, such as file sharing, instant messaging, and desktop grid computing
  41.  
  42. Service oriented
  43. Allowing interoperability of distributed components running on different platforms or across the Internet
  44. • Integrating legacy systems
  45. • Allowing dynamic reconfiguration
  46.  
  47. Publis sub
  48. Sending events to unknown recipients, isolating event producers from event consumers~
  49. • Providing core functionality for GUI frameworks, mailing lists, bulletin boards, and social networks
  50.  
  51. Shared data
  52. Allowing multiple components to access persistent data
  53. • Providing enhanced modifiability by decoupling data producers from data consumers
  54.  
  55.  
  56.  
  57.  
  58. 2018
  59. 1 errada -> C) It represents a relation between a component’s port and a port of one of its
  60. internal components
  61.  
  62. 2 erradas -> incremental uses é melhor
  63.  
  64. 3 erradas ->
  65. ABS não tem pubsub
  66. A view não demonstra a cena do OPC recuperar
  67. Availability and Performance
  68.  
  69.  
  70. 2017
  71.  
  72. 1 errada -> bussiness partner!!!
  73. 0 erradas -> layer é tipo uma vm because it provides a set of cohesive
  74. functionalities to the upper layer
  75.  
  76. 2016
  77.  
  78. 1 - > master/slave muitas copias de computação, devia existir sempre 1 viewe de decomposition
  79.  
  80.  
  81. 2 ->
  82. componentes é uma instancia, uma view pode ter varias instancias do mesmo componente
  83. a interação com as peers é simetrica o.O
  84.  
  85.  
  86. 1 -> merge execura merge e stdio, pipes executam modulos lol
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement