¡GoConqr estrena diseño! Cuéntanos qué te parece.

Fichas

Architecture, patterns, reuse

Claire Lemon software engineering Inglés 20 fichas

Fichas del conjunto (20)

  1. 1peer-to-peerAn architecture where there is no clear distinction between clients and servers.
  2. 2architectural viewA model of the architecture, that captures the concerns of a group of stakeholders of the system.
  3. 3idiomA pattern that applies within a programming language.
  4. 4Architectural style / patternCodifies recurrent software architectures by describing the key elements of the architecture and how they fit together. It also describes the qualities of systems that are assembled following the pattern.
  5. 5Name 9 Architectural stylesClient–server
    Call-return
    Layered
    Peer-to-peer
    Data flow
    Data-centred
    Independent components
    Service-oriented
    Notification
  6. 6pipes and filtersAn architecture where filters are the elements that take some data and process it to produce a result, and pipes are the conduits along which the data flows. Also known as data-flow
  7. 7peer-to-peer styleAn architectural style in which all components are both clients and servers and any component can request services from any other component.
  8. 8call-return styleAn architectural style in which one component (the caller) makes a procedure call to another component (often known as the callee) and waits for the call to return.
  9. 9client-serverAn architectural style in which one component (the server) waits for requests from clients, processes each one as it as received, and returns a response to the client.
  10. 10service-oriented styleAn architectural style in which set of service providers makes services available to a set of service consumers. Consumers can combine services in order to carry out business processes.
  11. 11independent components styleAn architectural style in which components are largely decoupled and execute concurrently, but coordinate with one another or exchange data by means of asynchronous messages.
  12. 12notification / publish-subscribeArchitectural style where subscribers register to receive updates (often messages) whenever a publisher posts a new item.
  13. 13layered styleAn architectural style in which the system is structured as a series of layers, each layer communicating only with the layers immediately above and below it.
  14. 14data-flow styleAn architectural style in which each component (called a filter) accepts a stream of data, processes it, and passes the result on to the next filter. A filter has no knowledge of other filters upstream or downstream but simply operates on the data it is given.
  15. 15data-centred styleAn architectural style in which there is a centralised data provider, together with a number of clients who are data consumers. If the provider simply responds to client requests it is called a database. A variant in which the data store informs clients when a change occurs is known as a blackboard.
  16. 16What are the various ingredients that make up a framework?A framework consists of an architecture, a small amount of software for the framework, a set of components suitable for use within the framework and the documentation needed to make use of the framework.
  17. 17product lineA set of related software products for different customers, reusing major parts of the software from customer to customer, with only those parts peculiar to the particular customer being different.
  18. 18adapterA design pattern that addresses the problem of a class having an interface different from the one the client expects.
  19. 19design patternA middle-level pattern describing a solution at a software design level.
  20. 20What is the difference between generalisation and realisation?Generalisation expresses a subtyping relationship between two classes. The subclass is a specialised subtype of its superclass and inherits the attributes and operations defined by the superclass.
    Realisation is not a subtyping relationship but instead expresses the fact that a class provides an implementation for all the operations specified by an interface.

Información

Descripción
(9 - Architecture, patterns and reuse) software engineering Fichas sobre Architecture, patterns, reuse, creado por Claire Lemon el 06/03/2017.
Creado por
Claire Lemon
Visitas
0
Valoración

Escríbenos

¿Sobre qué es tu mensaje?

¿Qué te parece el nuevo diseño?

¿Te gusta?