From 243ace1fe52fc96d6bd554d47964f244018bae2d Mon Sep 17 00:00:00 2001
From: Jet Hughes <hugje043@student.otago.ac.nz>
Date: Mon, 13 Jun 2022 12:54:24 +1200
Subject: [PATCH] vault backup: 2022-06-13 12:54:24

---
 content/notes/i201-practice.md | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/content/notes/i201-practice.md b/content/notes/i201-practice.md
index 2cbd8aff7..92f7c4231 100644
--- a/content/notes/i201-practice.md
+++ b/content/notes/i201-practice.md
@@ -7,7 +7,6 @@ tags:
 
 
 # Section A
-
 ## 1
 a) sequence diagram - to document a *sequence* of particpant interactions required to carry out a use case
 b) 
@@ -38,3 +37,15 @@ requirements - Requirements are something an information system should do, or so
 acceptance tests - not covered
 
 ## 6
+use predictive when
+- simple requirements
+- stable/mature technologiess
+- stable environment
+- non experimental
+
+## 7
+1) how quickly? - requirements should be unambiguous
+2) shouldn't say how? - requirements hould say what and not how
+
+# Section B
+## 8