Skip to content

Commit c4e8790

Browse files
committed
Further cleanup architecture links
1 parent dd2350f commit c4e8790

File tree

1 file changed

+13
-16
lines changed

1 file changed

+13
-16
lines changed

_notes/software-architecture/architecture.md

Lines changed: 13 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,6 @@ layout: notes
2626
* Successfull partitioning allow for the subsystems to be worked on separately by different groups of developers in order to co-operatively develop the system
2727
* Architecture's purpose is to assure that a system's functionality, quality attributes, and other business goals are satisfied
2828

29-
3029
# System/Subsystem Design
3130
![system-design]
3231

@@ -37,7 +36,6 @@ layout: notes
3736
* Application Programmer Interface (API) includes the names of operations, parameters/types, and return types
3837
* System design focuses on defining services
3938

40-
4139
# System/Subsystem Model
4240
![sub-system-model]
4341

@@ -80,7 +78,7 @@ layout: notes
8078
* Transformational systems
8179

8280
# Pipe and Filter Model
83-
![images/pipe-filter.png]
81+
![pipe-filter]
8482

8583
# UNIX Examples
8684
```
@@ -99,33 +97,33 @@ git log --pretty="%aN" | sort | uniq -c | sed "s/ *//" | cut -d ' ' -f2 -f1,3-10
9997
* No realtime feedback, no concurrency
10098

10199
# Batch Sequential Model
102-
![images/mvc.png]
100+
![mvc]
103101

104102
# Batch Sequential Model
105-
![images/repository-ide.png]
103+
![repository-ide]
106104

107105
# Batch Sequential Model
108-
![images/repository.png]
106+
![repository]
109107

110108
# Layered Architecture
111109
* Hierarchical decomposition of a system into subsystems (layers) with each providing a higher level of services provided from lower-level subsystems
112110
* *closed architecture* each layer can only depend on the layer immediately below
113111
* *open architecture* each layer can access any layer below
114112

115113
# Closed Architecture: OSI Network Model
116-
![images/open-arch.png]
114+
![open-arch]
117115

118116
# Open Architecture: Motif Library
119-
![images/closed-arch.png]
117+
![closed-arch]
120118

121119
# Repository Architecture
122-
![images/batch-seq-iii.png]
120+
![batch-seq-iii]
123121

124122
* Subsystems are independent and interact by a central repository
125123
* Examples: Payroll or banking system, Modern IDE/Compiler, Blackboard
126124

127125
# Repository: IDE
128-
![images/batch-seq-ii.png]
126+
![batch-seq-ii]
129127

130128
# Model/View/Controller
131129
* Subsystems
@@ -137,7 +135,7 @@ git log --pretty="%aN" | sort | uniq -c | sed "s/ *//" | cut -d ' ' -f2 -f1,3-10
137135
* Examples: File system, database
138136

139137
# MVC
140-
![images/batch-seq.png]
138+
![batch-seq]
141139

142140
# Client/Server Architecture
143141
* Subsystems:
@@ -146,19 +144,18 @@ git log --pretty="%aN" | sort | uniq -c | sed "s/ *//" | cut -d ' ' -f2 -f1,3-10
146144
* An information system with a central DB is an example
147145
* Web servers (multiple servers)
148146

149-
150147
# Client/Server Model
151-
![images/client-server.png]
148+
![client-server]
152149

153150
# Peer-to-Peer Architecture
154-
![images/peer-2-peer.png]
151+
![peer-2-peer]
155152

156153
# Peer-to-Peer Architecture
157154
* Generalization of client/server, clients can be servers and vice versa
158155
* The control flow of each subsystem is independent of others except for the synchronization of requests.
159156

160157
# Process Control Architecture
161-
![images/process-control.png]
158+
![process-control]
162159

163160
# Event-driven Architecture
164-
![images/event.png]
161+
![event]

0 commit comments

Comments
 (0)