From 1e91bfce73214de564c3915fc88c05081b7b0751 Mon Sep 17 00:00:00 2001
From: Spencer Smith <smiths@mcmaster.ca>
Date: Wed, 30 Sep 2020 16:27:24 -0400
Subject: [PATCH] Additional information on scope, assumptions and system
context
---
BlankProjectTemplate/docs/SRS/SRS-Checklist.tex | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/BlankProjectTemplate/docs/SRS/SRS-Checklist.tex b/BlankProjectTemplate/docs/SRS/SRS-Checklist.tex
index b77e4e4..cb60d66 100644
--- a/BlankProjectTemplate/docs/SRS/SRS-Checklist.tex
+++ b/BlankProjectTemplate/docs/SRS/SRS-Checklist.tex
@@ -97,7 +97,8 @@
\item Introductory blurb Includes a ``roadmap''
\item ``Purpose of the Document'' discusses the documentation's purpose, not
the program's purpose
- \item Scope of the requirements is an abstract version of the assumptions
+ \item Scope of the requirements is an abstract version of the assumptions.
+ Every item of the scope should be reflected in at least one assumption.
\item Characteristics of the intended reader are not confused with the user
characteristics
\item Characteristics of the intended reader are unambiguous
@@ -107,7 +108,13 @@
\begin{todolist}
\item System context includes a figure showing the relation between the
software system and external entities
- \item User characteristics are unambiguous
+ \item If the software will depend on other software, such as other libraries,
+ this is part of the system context. Try to keep the libraries generic,
+ unless specific libraries are needed, which will mean software constaints
+ are also specified.
+ \item User characteristics are unambiguous (for instance, don't just say the user will know
+ physics, say they will know Newtonian mechanics as typically covered in the
+ first year of an engineering or science degree)
\item User characteristics are specific
\item System constraints have an appropriate rationale (a constraint without a
reason for that constraint is likely making the SRS less abstract than it
--
GitLab