deploy: 9eb6f0e

handouts/adr/index.html

@@ -1,4 +1,4 @@
-Last Updated on 2024/03/18
+Last Updated on 2024/04/30
 
 
 <?xml version="1.0" encoding="iso-8859-1" ?> 
@@ -203,7 +203,7 @@ <h3 class="sectionHead"><span class="titlemark">3    </span> <a
 means the business logic only needs to be implemented once. This follows good design practices and common
 user interface design patterns.
 </p><!--l. 109--><p class="indent" >   The business logic will be implemented in Java. This suits the current development team&#8217;s experience and is a
-common environment. Java has good performance characteristices. Java has good support for interacting with
+common environment. Java has good performance characteristics. Java has good support for interacting with
 databases, to deliver the data storage and transaction processing requirements.
 
 
@@ -341,10 +341,10 @@ <h3 class="sectionHead"><span class="titlemark">6    </span> <a
 Blog</a><span class="footnote-mark"><a 
 href="#fn1x0" id="fn1x0-bk"><sup class="textsuperscript">1</sup></a></span><a 
  id="x1-6001f1"></a>
-<span class="cite">[<a 
-href="#Xwhy-write-adrs">5</a>]</span>.
 
 
+<span class="cite">[<a 
+href="#Xwhy-write-adrs">5</a>]</span>.
 </p><!--l. 1--><p class="noindent" >
 </p>
    <h3 class="likesectionHead"><a 

handouts/architecture/index.html

@@ -44,8 +44,6 @@ <h3 class="sectionHead"><span class="titlemark">1    </span> <a
  id="x1-1003r1"></a>
 </p>
    <div class="tcolorbox tcolorbox" id="tcolobox-1">     
-<div class="tcolorbox-title">
-   </div> 
 <div class="tcolorbox-content"><!--l. 15--><p class="noindent" ><span 
 class="Cabin-Bold-tlf-t1-x-x-120">Definition</span><span 
 class="Cabin-Bold-tlf-t1-x-x-120">&#x00A0;1. Software Architecture</span>
@@ -60,8 +58,6 @@ <h3 class="sectionHead"><span class="titlemark">1    </span> <a
  id="x1-1004r2"></a>
 </p>
    <div class="tcolorbox tcolorbox" id="tcolobox-2">     
-<div class="tcolorbox-title">
-   </div> 
 <div class="tcolorbox-content"><!--l. 24--><p class="noindent" ><span 
 class="Cabin-Bold-tlf-t1-x-x-120">Definition</span><span 
 class="Cabin-Bold-tlf-t1-x-x-120">&#x00A0;2. Software Architecture: The Course</span>
@@ -89,11 +85,11 @@ <h3 class="sectionHead"><span class="titlemark">2    </span> <a
 to deliver everything to the highest standard. The development team has to balance competing
 expectations and priorities to develop a software system that is a good compromise and meets its key
 goals.
-
-
 </p><!--l. 43--><p class="indent" >   From the perspective of designing a software architecture, competing expectations provides what are
 sometimes called <span 
 class="Cabin-Italic-tlf-t1-x-x-120">architectural drivers</span>.
+
+
 </p><!--l. 45--><p class="noindent" >
 </p>
    <h4 class="subsectionHead"><span class="titlemark">2.1    </span> <a 
@@ -244,15 +240,15 @@ <h3 class="sectionHead"><span class="titlemark">3    </span> <a
 </p><!--l. 143--><p class="indent" >   The role of a software architect is to identify which quality attributes are crucial to the success of their
 project, and to design an architecture and implement principles which ensure the quality attributes are
 achieved.
+
+
 </p><!--l. 147--><p class="indent" >   The first law of software architecture, as defined by Richards <span class="cite">[<a 
 href="#Xrichards2020fundamentals">4</a>]</span>, reflects the difficultly in supporting multiple
 quality attributes.
 <a 
  id="x1-8001r3"></a>
 </p>
    <div class="tcolorbox tcolorbox" id="tcolobox-3">     
-<div class="tcolorbox-title">
-   </div> 
 <div class="tcolorbox-content"><!--l. 149--><p class="noindent" ><span 
 class="Cabin-Bold-tlf-t1-x-x-120">Definition</span><span 
 class="Cabin-Bold-tlf-t1-x-x-120">&#x00A0;3. The First Law of Software Architecture</span>
@@ -266,8 +262,6 @@ <h3 class="sectionHead"><span class="titlemark">3    </span> <a
  id="x1-8002r4"></a>
 </p>
    <div class="tcolorbox tcolorbox" id="tcolobox-4">     
-<div class="tcolorbox-title">
-   </div> 
 <div class="tcolorbox-content"><!--l. 156--><p class="noindent" ><span 
 class="Cabin-Bold-tlf-t1-x-x-120">Definition</span><span 
 class="Cabin-Bold-tlf-t1-x-x-120">&#x00A0;4. Wicked Architecture</span>
@@ -280,8 +274,6 @@ <h3 class="sectionHead"><span class="titlemark">3    </span> <a
 fuzziness in software engineering&#8221;.
 </p><!--l. 164--><p class="indent" >   Despite this difficultly, in this course we intend to expose you to a number of case studies, architectures, and
 tools which aim to give you experience in tackling the trade-offs involved in software architecture.
-
-
 </p><!--l. 167--><p class="noindent" >
 </p>
    <h3 class="sectionHead"><span class="titlemark">4    </span> <a 
@@ -314,9 +306,9 @@ <h3 class="sectionHead"><span class="titlemark">5    </span> <a
 <a 
  id="x1-10001r5"></a>
 </p>
+
+
    <div class="tcolorbox tcolorbox" id="tcolobox-5">     
-<div class="tcolorbox-title">
-   </div> 
 <div class="tcolorbox-content"><!--l. 192--><p class="noindent" ><span 
 class="Cabin-Bold-tlf-t1-x-x-120">Definition</span><span 
 class="Cabin-Bold-tlf-t1-x-x-120">&#x00A0;5. Software Architecture: The Course</span>
@@ -345,8 +337,6 @@ <h3 class="sectionHead"><span class="titlemark">5    </span> <a
 from it in your careers as software development professionals!
 </p><!--l. 1--><p class="noindent" >
 </p>
-
-
    <h3 class="likesectionHead"><a 
  id="x1-11000"></a>References</h3>
 <!--l. 1--><p class="noindent" >
@@ -385,6 +375,8 @@ <h3 class="likesectionHead"><a
    Association for Computing Machinery, 2016.
 </p>
    </div>
+
+
    <div class="footnotes"><a 
  id="x1-1002x1"></a>
 <!--l. 12--><p class="indent" >       <span class="footnote-mark"><a 

handouts/distributed1/index.html

@@ -38,8 +38,6 @@ <h3 class="sectionHead"><span class="titlemark">1    </span> <a
  id="x1-1001r1"></a>
 </p>
    <div class="tcolorbox tcolorbox" id="tcolobox-1">     
-<div class="tcolorbox-title">
-   </div> 
 <div class="tcolorbox-content"><!--l. 14--><p class="noindent" ><span 
 class="Cabin-Bold-tlf-t1-x-x-120">Definition</span><span 
 class="Cabin-Bold-tlf-t1-x-x-120">&#x00A0;1. Distributed System</span>
@@ -81,8 +79,6 @@ <h3 class="sectionHead"><span class="titlemark">2    </span> <a
 
 
    <div class="tcolorbox tcolorbox" id="tcolobox-2">     
-<div class="tcolorbox-title">
-   </div> 
 <div class="tcolorbox-content"><!--l. 42--><p class="noindent" ><span 
 class="Cabin-Bold-tlf-t1-x-x-120">Definition</span><span 
 class="Cabin-Bold-tlf-t1-x-x-120">&#x00A0;2. Fallacy</span>
@@ -135,10 +131,10 @@ <h4 class="subsectionHead"><span class="titlemark">3.2    </span> <a
 </p>
    <h4 class="subsectionHead"><span class="titlemark">3.3    </span> <a 
  id="x1-60003.3"></a>Bandwidth is Infinite</h4>
-
-
 <!--l. 82--><p class="noindent" >Similar to the previous fallacy, the fallacy of infinite bandwidth is a plea for architects to be mindful and
 conservative in their system designs. We need to be mindful of the internal and external consumption
+
+
 of bandwidth for our systems. There are hard limits on bandwidth. A dubious statement from
 Wikipedia<span class="footnote-mark"><a 
 href="#fn2x0" id="fn2x0-bk"><sup class="textsuperscript">2</sup></a></span><a 
@@ -185,10 +181,10 @@ <h4 class="subsectionHead"><span class="titlemark">3.6    </span> <a
 to solve all your problems? There isn&#8217;t one; it is important to account for and plan for that. When
 things start failing, can you deploy to a different AWS region? Can you deploy to a different hosting
 provider? Can you deploy parts of your application on-premise? Likewise we need to be aware of
-
-
 this fallacy when trying to resolve less drastic failures, for example, high latency, permission errors,
 etc.
+
+
 </p><!--l. 137--><p class="noindent" >
 </p>
    <h4 class="subsectionHead"><span class="titlemark">3.7    </span> <a