Updates to blank project templates

BlankProjectTemplate/docs/Design/MG/MG-Checklist.tex

@@ -54,15 +54,16 @@
   \item Traceability matrix between likely changes and modules shows a one to
     one mapping, or, if this is not the case, explains the exceptions to this
     rule.
-    \item Level 1 of the decomposition by secrets shows: Hardware-Hiding,
-      Behaviour-Hiding and Software Decision Hiding.
-    \item Behaviour-Hiding modules are related to the requirements
-    \item Software-Decision hiding modules are concepts that need to be
-      introduced, but are not detailed in the requirements
-    \item Each Software Decision Hiding module is used by at least one
-      Behaviour-Hiding Module (if this isn't the case, an explanation should be
-      provided)
-    \item Uses relation is not confused with a data flow chart
+  \item Level 1 of the decomposition by secrets shows: Hardware-Hiding,
+    Behaviour-Hiding and Software Decision Hiding.
+  \item Behaviour-Hiding modules are related to the requirements
+  \item Software-Decision hiding modules are concepts that need to be
+    introduced, but are not detailed in the requirements
+  \item Each Software Decision Hiding module is used by at least one
+    Behaviour-Hiding Module (if this isn't the case, an explanation should be
+    provided)
+  \item Uses relation is not confused with a data flow chart
+  \item Anticipated changes are a superset of the likely changes in the SRS
   \end{todolist}
 
 \item MG quality

BlankProjectTemplate/docs/SRS/SRS-Checklist.tex

@@ -133,7 +133,10 @@
   \begin{todolist}
   \item Each assumption is ``atomic'' (no explicit or implicit ``ands'')
   \item Assumptions are a refinement of the scope
-  \item Each assumption is referenced at least once
+  \item Each assumption is referenced at least once in the document
+  \item If an assumption is listed as being referenced by another chunk (T, IM
+    etc), that other chunk should explicitly invoke the assumption in the
+    describing text or derivation
   \item A link exists between each chunk and anything that references it
   \item The rationale is given for assumptions that require justification
   \item The derivation of all GDs as refinements from other models is clear
@@ -141,7 +144,7 @@
   \item All DD are used (referenced) by at least one other model
   \item The IMs remain abstract
   \item Input data constraints are given, with a rationale where appropriate
-  \item Properties of a correct solution are given
+  \item Properties of a correct solution are given (or explicitly left blank)
   \item Equations are balanced with respect to units of all terms
   \end{todolist}
   

BlankProjectTemplate/docs/SRS/SRS.tex

@@ -937,8 +937,8 @@ be covered in the Verification and Validation document.}
 \item[NFR\refstepcounter{nfrnum}\thenfrnum \label{NFR_Accuracy}:]
   \textbf{Accuracy} \plt{Characterize the accuracy by giving the context/use for
     the software.  Maybe something like, ``The accuracy of the computed
-    solutions should meet the level needed for <engineering or scientific
-    application>.  The level of accuracy achieved by \progname{} shall be
+    solutions should meet the level needed for $<$engineering or scientific
+    application$>$.  The level of accuracy achieved by \progname{} shall be
     described following the procedure given in Section~X of the Verification and
     Validation Plan.''  A link to the VnV plan would be a nice extra.}