2424 id ="Q1-1-1 "> </ a >
2525_________________________________________________________________________________________________
2626< h2 class ="titleHead "> Chatterbox</ h2 > Software Architecture
27- < div class ="date " > May 8 , 2025</ div > < div class ="author " > Brae
27+ < div class ="date " > May 6 , 2025</ div > < div class ="author " > Brae
2828Webb</ div >
2929______________________________________________________________________________________________
3030 </ div >
31+
3132 < h3 class ="sectionHead "> < span class ="titlemark "> 1 </ span > < a
3233 id ="x1-10001 "> </ a > Brief</ h3 >
3334<!--l. 25--> < p class ="noindent " > Text-to-speech software supports accessibility, enables smart-home devices, and even breaks down
@@ -38,7 +39,7 @@ <h3 class="sectionHead"><span class="titlemark">1 </span> <a
3839impaired students in their studies. All course content from Ed discussion forum posts and blackboard
3940announcements to textbooks must be converted to speech. You are responsible for designing and implementing
4041a service to generate synthesized speech for use across the entire university.
41- </ p > <!--l. 38--> < p class =" noindent " >
42+
4243</ p >
4344 < h3 class ="sectionHead "> < span class ="titlemark "> 2 </ span > < a
4445 id ="x1-20002 "> </ a > Requirements</ h3 >
@@ -54,18 +55,17 @@ <h3 class="sectionHead"><span class="titlemark">2 </span> <a
5455class ="newline " /> < a
5556href ="https://csse6400.uqcloud.net/api/chatterbox " class ="url " > < span
5657class ="ectt-1200 "> https://csse6400.uqcloud.net/api/chatterbox</ span > </ a >
57- </ p > <!--l. 55--> < p class =" noindent " >
58+
5859</ p >
5960 < h3 class ="sectionHead "> < span class ="titlemark "> 3 </ span > < a
6061 id ="x1-30003 "> </ a > Outline</ h3 >
61- <!--l. 57--> < p class ="noindent " >
62- </ p >
62+
6363 < h4 class ="likesubsectionHead "> < a
6464 id ="x1-4000 "> </ a > Introduction (5 minutes)</ h4 >
6565<!--l. 58--> < p class ="noindent " > Introduction to the brief and resources including the API specification and quality scenarios.
6666
6767
68- </ p > <!--l. 61--> < p class =" noindent " >
68+
6969</ p >
7070 < h4 class ="likesubsectionHead "> < a
7171 id ="x1-5000 "> </ a > Planning (10 minutes)</ h4 >
@@ -83,28 +83,29 @@ <h4 class="likesubsectionHead"><a
8383 </ dd > < dt class ="enumerate-enumitem ">
8484 4. </ dt > < dd
8585class ="enumerate-enumitem "> What are the likely bottlenecks?</ dd > </ dl >
86- <!--l. 72--> < p class ="noindent " >
87- </ p >
86+
8887 < h4 class ="likesubsectionHead "> < a
8988 id ="x1-6000 "> </ a > Design (20 minutes)</ h4 >
9089<!--l. 74--> < p class ="noindent " > In your group, design an appropriate system. You need to consider the flow of an API request through your
9190system, use the API specification to ensure all use cases have been considered.
92- </ p > <!--l. 78--> < p class =" noindent " >
91+
9392</ p >
9493 < h4 class ="likesubsectionHead "> < a
9594 id ="x1-7000 "> </ a > Presentation (15 minutes)</ h4 >
9695<!--l. 80--> < p class ="noindent " > In the remaining time, each group should present their proposed design. This is an opportunity for discussion
9796amongst the class to point out limitations of the proposed system designs.
98- </ p > <!--l. 85--> < p class =" noindent " >
97+
9998</ p >
10099 < h3 class ="sectionHead "> < span class ="titlemark "> 4 </ span > < a
101100 id ="x1-80004 "> </ a > Quality Scenarios</ h3 >
101+
102102<!--l. 87--> < p class ="noindent " > < span class ="paragraphHead "> < a
103103 id ="x1-9000 "> </ a > < span
104104class ="Cabin-Bold-tlf-t1-x-x-120 "> Semester break</ span > </ span >
105105 Your application will see decreased usage during the semester break. Minimal students and staff may
106106periodically query pre-generated speech when revising content. During this period we might see traffic of not
107107more than 20 parallel users, querying read-only endpoints.
108+
108109
109110
110111</ p >
@@ -114,6 +115,7 @@ <h3 class="sectionHead"><span class="titlemark">4 </span> <a
114115 During the 20 minutes prior to an exam of a large course, such as CSSE1001, you might expect the entire
115116cohort of over one thousand students to be revising the content. Revising the content will consist primarily of
116117read-only requests.
118+
117119</ p >
118120<!--l. 98--> < p class ="noindent " > < span class ="paragraphHead "> < a
119121 id ="x1-11000 "> </ a > < span
@@ -124,6 +126,7 @@ <h3 class="sectionHead"><span class="titlemark">4 </span> <a
124126</ p > <!--l. 104--> < p class ="indent " > In addition, teaching staff for exams later in the week have begun uploading revision material. We might
125127expect about 30 staff members to upload their one page course summaries, about 3,500 characters
126128each.
129+
127130</ p >
128131<!--l. 108--> < p class ="noindent " > < span class ="paragraphHead "> < a
129132 id ="x1-12000 "> </ a > < span
@@ -132,6 +135,7 @@ <h3 class="sectionHead"><span class="titlemark">4 </span> <a
132135the call to cancel teaching for the week. Coordinators are responsible for disseminating this information to their
133136students. All 1,957 courses must send announcements averaging 100 characters (many exact copies of the
134137suggested announcement), to relay this information.
138+
135139</ p >
136140<!--l. 115--> < p class ="noindent " > < span class ="paragraphHead "> < a
137141 id ="x1-13000 "> </ a > < span
@@ -141,6 +145,7 @@ <h3 class="sectionHead"><span class="titlemark">4 </span> <a
141145Suddenly your system receives a large amount of requests to generate the spoken version of textbooks (we
142146estimate that textbooks are around 350,000 characters). About 100 coordinators submit their reading list at the
143147last minute.
148+
144149</ p >
145150<!--l. 122--> < p class ="noindent " > < span class ="paragraphHead "> < a
146151 id ="x1-14000 "> </ a > < span
0 commit comments