GitHub/quartz
1
0
Fork 2
mirror of https://github.com/jackyzha0/quartz.git synced 2025-12-24 13:24:05 -06:00
Code Issues Actions Packages Projects Releases Wiki Activity

vault backup: 2022-06-13 12:34:23

Browse Source
This commit is contained in:
Jet Hughes 2022-06-13 12:34:23 +12:00
parent 2c9b6c9dd7
commit bff210f9cd
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
content/notes/i201-practice.md
View File

@ -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
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