Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Chapter 2
- • A decomposition view shows how responsibilities are allocated across modules and submodules.
- • 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.
- • 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.
- • 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.
- • 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.
- • 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.
- Chapter 3 Component and connector views
- • 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.
- • The database access connector supports transactional, authenticated access for reading, writing, and monitoring the database.
- • The publish-subscribe connector supports asynchronous event announcement and notification.
- Components have interfaces called ports
- 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.
- Chapter 4
- • Call-return styles. Styles in which components interact through synchronous invocation of capabilities provided by other components.
- • Data flow styles. Styles in which computation is driven by the flow of data through the system.
- • Event-based styles. Styles in which components interact through asynchronous events or messages.
- • Repository styles. Styles in which components interact through large collections of persistent, shared data.
- Pipe and filter
- • Improving reuse due to the independence of filters
- • Improving throughput with parallelization of data processing
- • Simplifying reasoning about overall behavior
- C and S
- Promoting modifiability and reuse by factoring out common services
- • Improving scalability and availability in case server replication is in place
- • Analyzing dependability, security, and throughput
- P2p
- Providing enhanced availability
- • Providing enhanced scalability
- • Enabling highly distributed systems, such as file sharing, instant messaging, and desktop grid computing
- Service oriented
- Allowing interoperability of distributed components running on different platforms or across the Internet
- • Integrating legacy systems
- • Allowing dynamic reconfiguration
- Publis sub
- Sending events to unknown recipients, isolating event producers from event consumers~
- • Providing core functionality for GUI frameworks, mailing lists, bulletin boards, and social networks
- Shared data
- Allowing multiple components to access persistent data
- • Providing enhanced modifiability by decoupling data producers from data consumers
- 2018
- 1 errada -> C) It represents a relation between a component’s port and a port of one of its
- internal components
- 2 erradas -> incremental uses é melhor
- 3 erradas ->
- ABS não tem pubsub
- A view não demonstra a cena do OPC recuperar
- Availability and Performance
- 2017
- 1 errada -> bussiness partner!!!
- 0 erradas -> layer é tipo uma vm because it provides a set of cohesive
- functionalities to the upper layer
- 2016
- 1 - > master/slave muitas copias de computação, devia existir sempre 1 viewe de decomposition
- 2 ->
- componentes é uma instancia, uma view pode ter varias instancias do mesmo componente
- a interação com as peers é simetrica o.O
- 1 -> merge execura merge e stdio, pipes executam modulos lol
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement