Release capstone project specification.

Author: applebyter

assessment/project/main.tex

@@ -24,7 +24,7 @@
 
 \title{Capstone Project}
 \author{Richard Thomas \& Brae Webb}
-\date{Semester 1, 2024}
+\date{Semester 1, 2025}
 
 \begin{document}
 
@@ -120,9 +120,9 @@ \section{Report}
     \item[Reflection] Lessons learnt and what you would do differently.
 \end{description}
 
-%No page limit is specified.
-%You are expected to be able to make rationale choices of what to include in your report.
-%A key phrase to keep in mind is ``less is more''.
+No page limit is specified.
+You are expected to be able to make rationale choices of what to include in your report.
+A key phrase to keep in mind is ``less is more''.
 
 You do not need to have sections for each topic above, though your report needs to contain the content summarised above.
 For example, the description of the architecture could include discussion of trade-offs.
@@ -166,8 +166,8 @@ \section{Report}
 Provide links to any test plans, scripts or code in your repository.
 Where feasible, tests should be automated.
 Describe how to run the tests.
-Ideally, you should use \link{GitHub Actions}{https://docs.github.com/en/actions}
-to run tests and potentially deploy artefacts.
+%Ideally, you should use \link{GitHub Actions}{https://docs.github.com/en/actions}
+%to run tests and potentially deploy artefacts.
 
 Your report should end with a reflection that summarises what you have learnt from designing and implementing this project.
 It should include descriptions of what you would do differently, after the experience of implementing the project.
@@ -192,7 +192,7 @@ \section{Repository}
 It is recommended that you use LaTeX, or possibly markdown, to write your report.
 If you use LaTeX, you should use GitHub actions to produce a PDF of the report.
 
-Your final submission will be what is in the main branch of your repository at the due date of 15:00 on 3 June 2024.
+Your final submission will be what is in the main branch of your repository at the due date of 15:00 on 9 June 2025.
 
 
 \section{Academic Integrity}
@@ -208,7 +208,7 @@ \section{Academic Integrity}
 All references for citations must be included in a file called \texttt{refs.md}.
 This file should be in the root directory of your repository.
 
-You are encouraged to use a generative AI tool (e.g. copilot) to help you write the source code for this project.
+You are encouraged to use a generative AI tool (e.g. Copilot) to help you write the source code for this project.
 The expectation is that the software architecture and detailed design are your team's own work.
 Create a file in the root directory of your repository called \texttt{ai.md}.
 In this file, describe how you used generative AI to develop your project.
@@ -226,10 +226,10 @@ \section{Academic Integrity}
 You must include a link to each library's homepage.
 This \texttt{libs.md} file must be in your repository's root directory.
 
-Uncited, unreferenced or unacknowledged material will be treated as not being your own work.
+Uncited, unreferenced, or unacknowledged material will be treated as not being your own work.
 Significant amounts of cited material from other sources will be considered to be of no academic merit.
 Having an AI tool produce significant amounts of source code is acceptable,
-\textit{if} the design is your own and you have verified that the code is correct.
+\textbf{\textit{if}} the design is your own and you have conducted detailed verification of the code.
 
 
 \section{Demonstration}
@@ -238,14 +238,16 @@ \section{Demonstration}
 or briefly summarising how the architecture facilitates delivering a quality attribute.
 
 Your project demonstration will be a video.
+This is completely separate from your presentation assessment.
+It is a demonstration of your completed project.
 Provide a link to the video in a file called \textbf{\texttt{demo.md}}, stored in the root directory of your repository.
 Do \textbf{\textit{not}} store the video in your GitHub repository.
 The link may be to the video on a platform like YouTube, or a file sharing site from where the video may be downloaded.
 If you upload the video to a platform like YouTube, you may make it private.
 If it is a private video, you must share it with \texttt{[email protected]},
-\texttt{evan.hughes@uq.edu.au}, \texttt{mdarafat.hossain@uq.edu.au}, \\\texttt{[email protected]},
-\texttt{r.wibawa@uq.edu.au}, and all of your team members.
-The video must remain available until \textit{at least} 31 July 2024.
+\texttt{g.bai@uq.edu.au}, \texttt{thanhthuy.dao@uq.edu.au}, \\\texttt{[email protected]},
+\texttt{[email protected]}, \texttt{n.garg@uq.edu.au}, and all of your team members.
+The video must remain available until \textbf{\textit{at least}} 31 July 2025.
 Viewers must be able to easily see what is being demonstrated and read any text or images.
 Audio must be clear and comprehensible.
 
@@ -262,7 +264,7 @@ \section{Demonstration}
 \end{samepage}
 
 \noindent
-The total duration of your video should be \textbf{\emph{less}} than 15 minutes.
+The total duration of your video must be \textbf{\emph{less}} than 15 minutes.
 
 \paragraph{Introduction} Briefly introduce the project context and summarise the delivered functional and non-functional requirements.
 Mention any differences between what was originally proposed, what was renegotiated, and what was delivered.

assessment/project/publish.not assessment/project/publishassessment/project/publish.not renamed to assessment/project/publish

@@ -244,15 +244,11 @@ <h2>Assessment</h2>
                 </tr>
                 <tr class="table">
                     <th scope="row">
-					<!--
 					    <a href="/assessment/project.pdf" target="_blank">
-					-->
 						    Capstone Project
-					<!--
 						</a>
-					-->
 					</th>
-                    <td>April 7th</td>
+                    <td>April 12th</td>
                     <td><strong>June 9th @ 3pm</strong> (Exam Block)</td>
                     <td>35%</td>
                 </tr>