From bff210f9cd08da155e0bbdf3826c4ce57d304281 Mon Sep 17 00:00:00 2001 From: Jet Hughes Date: Mon, 13 Jun 2022 12:34:23 +1200 Subject: [PATCH] vault backup: 2022-06-13 12:34:23 --- content/notes/i201-practice.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/content/notes/i201-practice.md b/content/notes/i201-practice.md index a4fc866da..211806f41 100644 --- a/content/notes/i201-practice.md +++ b/content/notes/i201-practice.md @@ -11,6 +11,16 @@ tags: ## 1 a) sequence diagram - to document a *sequence* of particpant interactions required to carry out a use case b) -1 - Actor -2 - Activation Bar -3 - message \ No newline at end of file +1 - Actor - a participant in the sequence +2 - Activation Bar - indicate when a participant is doing something +3 - message - indicate communication between participats + +## 2 +update anomaly - e.g., when a single employee is working on two projects, and we need to update their salary, it is possible to only update their salary in one location causing an update anomaly + +root causes - this occired because there was redundancy within the database - the employee and his salary should only be stored in one location + +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