From 6a5368ecb08951d465e848cd92ce3042ebaaa32a Mon Sep 17 00:00:00 2001 From: Jet Hughes Date: Mon, 13 Jun 2022 12:44:23 +1200 Subject: [PATCH] vault backup: 2022-06-13 12:44:23 --- content/notes/i201-practice.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/content/notes/i201-practice.md b/content/notes/i201-practice.md index 211806f41..2cbd8aff7 100644 --- a/content/notes/i201-practice.md +++ b/content/notes/i201-practice.md @@ -23,4 +23,18 @@ root causes - this occired because there was redundancy within the database - th how it can be solved/avoided - this can be easily avoided by normalising the database to remove redundancies. ## 3 -a) business functions are things that the business *ought* to be doing, for example "accept payment from customer". The can be identified by verb phrases \ No newline at end of file +a) business functions are things that the business *ought* to be doing (not what it is doing now), for example "accept payment from customer". each business function essentially become a fuction or a set of functions within the information system. they do not describe the who, how, or where of the function. + +b) business function are typiclaly modelled using use case diagrams. in the final system they become features or a set of features + +## 4 +1) dont have the technical ability +2) not legal +3) organisational - lack of institutional will + +## 5 +requirements - Requirements are something an information system should do, or some constraint it should adhere to + +acceptance tests - not covered + +## 6