mirror of
https://github.com/jackyzha0/quartz.git
synced 2025-12-24 21:34:06 -06:00
vault backup: 2022-06-13 12:34:23
This commit is contained in:
parent
2c9b6c9dd7
commit
bff210f9cd
@ -11,6 +11,16 @@ tags:
|
|||||||
## 1
|
## 1
|
||||||
a) sequence diagram - to document a *sequence* of particpant interactions required to carry out a use case
|
a) sequence diagram - to document a *sequence* of particpant interactions required to carry out a use case
|
||||||
b)
|
b)
|
||||||
1 - Actor
|
1 - Actor - a participant in the sequence
|
||||||
2 - Activation Bar
|
2 - Activation Bar - indicate when a participant is doing something
|
||||||
3 - message
|
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
|
||||||
Loading…
Reference in New Issue
Block a user