Skip to content

Commit

Permalink
Finialised supplementary assessment requirements.
Browse files Browse the repository at this point in the history
  • Loading branch information
applebyter committed Aug 8, 2023
1 parent 83cae37 commit 2750c41
Show file tree
Hide file tree
Showing 2 changed files with 27 additions and 121 deletions.
77 changes: 0 additions & 77 deletions assessment/supplementary/criteria.tex

This file was deleted.

71 changes: 27 additions & 44 deletions assessment/supplementary/main.tex
Original file line number Diff line number Diff line change
Expand Up @@ -11,51 +11,26 @@
}
\makeatother

% RUBRIC
\usepackage{multirow}
\usepackage{array}
\usepackage{xltabular}
\usepackage{pdflscape}
\usepackage{enumitem}

\newcolumntype{P}[1]{>{\centering\arraybackslash}p{#1}}
% RUBRIC

\title{Supplementary Assessment}
\author{Richard Thomas}
\date{Semester 1, 2023}


\begin{document}
\maketitle

\section*{Summary}
To assess that you have achieved the learning objectives for the course,
you need to design and evaluate the architecture for a complex system.
\begin{itemize}
\item propose a non-trivial software project,
\item identify the primary quality attributes which would enable success of the project,
\item design an architecture suitable for the aims of the project,
\item deploy the architecture, utilising any techniques you have learnt in or out of the course, and
\item evaluate and report on the success of the software project.
\end{itemize}

\noindent
The successful completion of the project will result in three deliverables, namely,
\begin{enumerate}[label=\roman*]
\item a proposal of a software project, the proposal must clearly indicate and prioritise two or three quality attributes most important to the project's success,
\item the developed software, as both source code, and a deployed artifact, and
\item a report which evaluates the success of the developed software relative to the chosen quality attributes.
\end{enumerate}

\noindent
Your software deliverable must include all supporting software (e.g. test suites or utilities) that are developed to support the delivered software.

\section{Introduction}
TradeOverflow wishes to provide a more dynamic shopping experience than traditional auction sites.
Rather than items being listed for auction over a period of time, with a fixed end date,
the sales model will be a trading platform.
TradeOverflow will scan all items that are listed for sale on the site.
It will aggregate all items of the same type.
It will aggregate all items of the same type into a trading set.
(e.g. It will find all copies of the Dune Ultra HD Bluray that are for sale, and aggregate them into a single trading set.)

Once items have been aggregated into a trading set, the system will provide a dynamic trading platform for the item.
Expand Down Expand Up @@ -125,25 +100,24 @@ \section{Design}
\item Performing the trading strategy of when the active purchasing group wants to purchase more items than are available in the active sales group.
\item A seller changing the minimum sales price for a listing that has not yet been sold.
\end{itemize}

You should make use of an appropriate architectural view that allows you to demonstrate how the architecture achieves the non-functional requirements described above.


\section{Evaluation}
You need to describe how you would test the TradeOverflow system to demonstrate that it delivers its key non-functional requirements.
What infrastructure and test environment would be needed to perform adequate testing?
This needs to describe the infrastructure and test environment that would be needed to perform adequate testing.
You need to justify why the proposed testing strategy would be sufficient to provide confidence that the system meets its functional and non-functional requirements.


\section{Report}
The report should include the following content.

You need to submit a report that includes the following content.
\begin{description}
\item[Diagrams] C4 diagrams of the system's architecture.
\item[Architecture] Textual description of the software architecture.
\item[Justification] Describe how the architecture delivers the key non-functional requirements. Justify the architectural choices you made in the design. Explain why the selected AWS services are suitable to deliver the key non-functional requirements.
\item[Security] Describe the potential digital attack surface of the system and how it should be designed and implemented to reduce the risk of unauthorised access to the system.
\item[Evaluation] Summarise how the TradeOverflow system could be tested.
\end{description}

You do not need to have sections for each topic above, though your report needs to contain the content summarised above.
For example, the architectural description and diagrams could be interleaved with each other.

Expand All @@ -155,18 +129,26 @@ \section{Report}
\section{Presentation}
You must complete a presentation as part of this supplementary assessment.
You cannot pass the assessment without completing the presentation.
The presentation will consist of a five minute summary of your architectural design.
The presentation will consist of a six minute summary of your architectural design and justification of your design choices.
You should use diagrams from your report to help the audience understand your architecture.

After your five minute summary, you will need to answer questions about your architectural design.
After your summary presentation, you will need to answer questions about your architectural design.
Questions may ask you to
\begin{itemize}[itemsep=3pt]
\begin{itemize}
\item explain parts of the detail of your architecture,
\item justify choices made in your architectural design, or
\item justify the technologies or services selected to deliver the architecture.
\end{itemize}


\section{Submission}
\begin{itemize}
\item Submit your report by 4pm on 18 August 2023 through the Supplementary Assessment TurnItIn link on the CSSE6400 BlackBoard site.
\item Arrange an appointment to make your presentation by emailing \href{mailto:[email protected]}{[email protected]} by 4pm on 18 August 2023.
\item Make your presentation in-person by 4pm on 22 August 2023, unless external factors make that impossible, in which case the presentation will be made over Zoom.
\end{itemize}


\section{Academic Integrity}
As this is a higher-level course, you are expected to be familiar with the importance of academic integrity in general, and the details of UQ's rules.
If you need a reminder, review the \link{Academic Integrity Modules}
Expand All @@ -183,16 +165,17 @@ \section{Academic Integrity}


\section{Grading Criteria}

\begin{description}[itemsep=3pt]
\item[20\%] Extent to which project's scope was delivered.
\item[20\%] Suitability of architecture to deliver system goals.
\item[20\%] Quality and thoroughness of testing.
\item[20\%] Clarity, accuracy and completeness of architecture's description.
\item[20\%] Insightfulness of architecture's evaluation.
This is a pass/fail assessment.
Your result will either be a passing or failing grade for the course.
You must pass \textbf{all} of the following criteria.
\begin{description}
\item[Architecture] The described architecture is capable of delivering the system's functional and non-functional requirements.
\item[Technology] The selected AWS services are capable of achieving the non-functional requirements of the system and the architecture structures these in a fashion that will work.
\item[Justification] You demonstrate appropriate consideration of trade-offs when selecting services and making architectural design choices.
\item[Security] You demonstrate adequate knowledge of potential security risks in the architecture and how these may be managed.
\item[Evaluation] You demonstrate adequate knowledge of how to test a complex distributed system.
\item[Presentation] You demonstrate in-depth knowledge of the architecture design and its rationale.
\end{description}


\input{criteria}

\end{document}

0 comments on commit 2750c41

Please sign in to comment.