Skip to content
Snippets Groups Projects
Commit 9267d652 authored by Yuchen Liu's avatar Yuchen Liu
Browse files

designdoc add section 5 non-functional and section 7

parent 622bf640
No related merge requests found
designdoc.pdf 100644 → 100755
No preview for this file type
designdoc.tex 100644 → 100755
......@@ -157,6 +157,25 @@ implemented by Java so there is no need to re-implement them.
\section{Connection Between Requirements and Design}
\subsection{Nonfunctional Requirements}
non-Req1: Look And Feel Requirements: Look and feel requirement mainly require the GUI part of the Design model.
non-Req2: Usability And Humanity Requirements: this part is mainly related to the Logic and the Hint module which decided the diffculity of the game.
non-Req3: Performance Requirements: this part should relating to the hardware part(hoardware should have good CPU, memory, graphic...) and each module's algorithm.
non-Req4: Operational And Environmental Requirements this requirement can be complished by using the Jave language for programming and then it can run on any Java machine
non-Req5: Maintainability And Support Requirements: the logic and hint module should ba able to handel this
non-Req6: Security Requirements: for the software part, there won't be any offentive code
non-Req7: Cultural Requirements: for this part we will not allow the offensive pictures to be added to our database
non-Req8: Legal Requirements: the logical won't allow conpile the picture without permission
\section{Module Decomposition}
\subsection{Hardware Hiding Module (M1)}
......@@ -216,6 +235,58 @@ implemented by Java so there is no need to re-implement them.
\section{Traceability Matrix}
Anticipated Changes
\begin{tabular} { l | c c c c c}
\hline
AC & Modules & & & & \\
\hline
AC1 & M1 & M9 & & & \\
AC2 & M1 & M8 & M9 & & \\
AC3 & M1 & M8 & M9 & & \\
AC4 & M4 & M5 & M7 & & \\
AC5 & M2 & M6 & & & \\
AC6 & M3 & M4 & M6 & & \\
AC7 & M4 & M5 & M7 & & \\
AC8 & M3 & M6 & M8 & M9 & \\
\end{tabular}
Non-Functional Requirement
\begin{tabular} { l | c c c c c}
\hline
non-Req & Modules & & & & \\
\hline
non-Req1 & M4 & M5 & & & \\
non-Req2 & M2 & M6 & & & \\
non-Req3 & M1 & M6 & M7 & & \\
non-Req4 & M1 & & & & \\
non-Req5 & M9 & & & & \\
non-Req6 & M9 & & & & \\
non-Req7 & & & & & \\
non-Req8 & M9 & & & & \\
\end{tabular}
Functional Requirement
\begin{tabular} { l | c c c c c}
\hline
Req & Modules & & & & \\
\hline
Req1 & M4 & M5 & & & \\
Req2 & M4 & M5 & & & \\
Req3 & M4 & M5 & & & \\
Req4 & M4 & M5 & & & \\
Req5 & M4 & M5 & & & \\
Req6 & M4 & M5 & M6 & & \\
Req7 & M4 & M5 & M6 & & \\
Req8 & M4 & M5 & M6 & & \\
Req9 & M4 & M5 & M6 & & \\
Req10 & M4 & M5 & M6 & & \\
Req11 & M4 & M5 & M6 & & \\
Req12 & M4 & M5 & M6 & & \\
\end{tabular}
\section{Uses Hierarchy Between Modules}
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment