|
21 | 21 | \maketitle |
22 | 22 |
|
23 | 23 | \point[So far\dots]{Layered architectures reduce the impact of changing a layer} |
| 24 | +\note{Emphasizing idea that pipeline architecture is a layered architecture taken to an extreme, |
| 25 | + minus the ability to have upward notifications.} |
24 | 26 |
|
25 | | -%\note{We're emphasizing that pipeline architecture is a layered architecture taken to an extreme, minus the ability to have upward notifications.} |
26 | | - |
27 | | -\questionanswer{Why does the layer order matter?\note{A consequence is layers have order.}}{Each layer implements a different interface.} |
| 27 | +\questionanswer{Why does the layer order matter?\note{A consequence is layers have order.}} |
| 28 | + {Each layer implements a different interface.} |
28 | 29 |
|
29 | 30 | \point[So\dots]{If every layer implements the same interface?} |
30 | | - |
31 | 31 | \note{We essentially have a pipeline architecture.} |
32 | 32 |
|
33 | 33 | \point[Extreme layered architecture]{Pipeline Architectures\footnote{sorta}} |
34 | 34 |
|
35 | 35 | \definition{Pipeline Architecture}{Components connected in such a way that the output of one component is the input of another.} |
36 | 36 |
|
37 | | -\questionanswer{Can you think of a \highlight{pipeline architecture}?}{How about \highlight{bash}?} |
38 | | - |
| 37 | +\questionanswer{Can you think of a \highlight{pipeline architecture}?} |
| 38 | + {How about \highlight{bash}?} |
39 | 39 | \note[itemize]{ |
40 | 40 | \item Bash |
41 | 41 | \item Compilers |
|
72 | 72 | \end{frame} |
73 | 73 |
|
74 | 74 | \begin{frame}[c] |
75 | | - |
76 | 75 | \only<1->{{\large\par\bigskip |
77 | 76 | \begin{center} |
78 | 77 | \begin{tikzpicture}[>=latex'] |
|
90 | 89 | \end{center} |
91 | 90 | } |
92 | 91 | } |
93 | | - |
94 | 92 | \note{Note the simplicity and modularity.} |
95 | 93 |
|
96 | 94 | \only<2->{ |
|
254 | 252 | ; |
255 | 253 | \end{tikzpicture} |
256 | 254 | \end{frame} |
257 | | -
|
258 | 255 | \note{Just an aside looking at it more practically rather than philosophically.} |
259 | 256 |
|
| 257 | +
|
260 | 258 | %\point[Case Study]{Compilers} |
261 | 259 |
|
262 | 260 | %\note{Exploring how the pipeline architecture can be integrated with other architectural styles like blackboard.} |
|
269 | 267 |
|
270 | 268 | %\question{Using pipeline terminology, what filters do the \highlight{map} and \highlight{reduce} operators correspond to?} |
271 | 269 |
|
| 270 | +
|
272 | 271 | \point[Reading...]{``Pipeline Architecture'' Notes \cite{pipeline-notes}} |
273 | 272 |
|
274 | 273 | \references{articles,books,ours} |
|
0 commit comments