Architecture

Question 1

architecture

Answer 1

way of organizing code

Question 2

information hiding

Answer 2

the less a part of a program knows about other parts of a program, the easier it is to change. Basis of architecture.

Question 3

encapsulation

Answer 3

idea of designing self-contained abstractions with well-defined interfaces that separate different concerns in a program.

Question 4

programming languages offer encapsulation support through things like

Answer 4

functions and classes, which encapsulate data and functionality together.

Question 5

scoping

Answer 5

another programming language encapsulation method; hides variables and other names from other parts of program outside a scope.

Question 6

cross-cutting concerns

Answer 6

things like features and functionality that span multiple different components of a system, or even an entire system. A big ball of mud or spaghetti code.

Question 7

cross-cutting concerns can lead to

Answer 7

difficulties in program comprehension and long-term design degradation, all of which reduce productivity and increase the risk of defects.

Question 8

technical debt

Answer 8

the degree to which an implementation is out of sync with a team’s understanding of what a product is intended to be.

Question 9

Unified Modeling Language (UML)

Answer 9

series of notations for expressing the architectural design of a system before implementing it.

Question 10

architectural styles

Answer 10

patterns of interactions and information exchange between encapsulated components.

Question 11

client/server

Answer 11

data is transacted in response to requests.

Question 12

pipe and filter

Answer 12

data is passed from component to component, and transformed and filtered along the way.

Question 13

Model-view-controller (MVC)

Answer 13

data is separated from views of the data and from manipulations of data.

Question 14

Peer to peer (P2P)

Answer 14

components transact data through a distributed standard interface.

Question 15

Event-driven

Answer 15

components “broadcast” events and others “subscribe” to notifications of these events.

Question 16

component (first fundamental unit of architecture)

Answer 16

refers to any abstraction—any code, really—that attempts to encapsulate some well defined functionality or behavior separate from other functionality and behavior. have interfaces that decide how it can communicate with other components

Question 17

connectors (second fundamental unit of architecture)

Answer 17

abstractions (code) that transmit information between components. They’re brokers that connect components, but do not necessarily have meaningful behaviors or states of their own. function calls, api calls, events, requests, etc.

Question 18

architectural mismatch

Answer 18

Even with carefully selected architectures, systems can still be difficult to put together.

Question 19

when a mismatch occurs

Answer 19

connecting two styles can require dramatic amounts of code to connect, imposing significant risk of defects and cost of maintenance.

Question 20

coupled

Answer 20

the user interface needs to know a lot about the data, its meaning, and its structure in order to render it meaningfully.

Question 21

refactoring

Answer 21

changing the architecture of an implementation without changing its behavior.