Scribd
Upload
34 views4 pages

Aais Week 1 Notes

Uploaded by

annis aminudin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
34 views4 pages

Aais Week 1 Notes

Uploaded by

annis aminudin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

User  data

Accounting dept  (abc)

 (xby) Have their own info need

Credit control dept  (zbq)

Data redundancy and flat file problem (data ada multiple copy)

Issue: take extra storage, spent a lot on storage (ex: info B hv being put at 3 places of dept in slides)

: need to update banyak kali (B hv being put at 3 places of dept, so kene update 3 3 sekali, if one tak
update, nanti satu tu outdated, tak sync)

: info not being current (distribute to 3 ppl, but dorang tgh update, 3 orang buat benda sama at the same
time, mess up, ex: isi list name kat ws group)

: task data dependency ( data and task dia connected, user 1 nak data from program 3 (z) , user 1 kene
request from user 3 , if user 3 failed to provide, maybe because of task data dependency)

Ex : User 1 change the info of the item, so nanti user lain ada their own pov so masalah nanti mess up
DATABASE/data sharing approach (solvekan masalah flat file problem)

Only need 1 , save on storage, save on need for updating, so everyone get the same data Tak mess up,
solve task data dependency sebab dah tak perlu contact user 3 sebab dia dah ada access to the data ,
because data and task no longer dependent between each other

Advantage :

- No data redundancy (Tak perlukan extra storage)


- Only single update needed (no extra updating needed)
- Only have current value (all can get updated data
- Task data independent

Disadvantage :

- Costly to implemented (sebab ada additional hardware, software, storage & network resources
required)
- Can only run in certain operating environment (may unsuitable for some system)
- So different from the file-oriented , the database approach requires training user (ex: inertia or
resistance)
Element of databased environment

Need databased management system to manage (dbms)

Since databased can be access by many ppl , so there is an issue in internal control(security) and dbms

- Dbms ( to manage the database but when data is available to everyone, so we need to bring in
internal control

DBMS FEAUTRES:

1) Program development
2) Backup and recovery (duplicate of that data incase some other issue arise, to protect from data
loss, distruption)
3) Database access (who, when gonna access the data?)
4) User programs (when user want to access data (edit/update data) , they will interact with their
user program to let them know its updated)
5) Direct query

DDL *data definition language

- Programming language use to define the databased (identify name and relay all data element,
record, and file
- D means design the 3 view based on data, record, file
- 3 view: 1) internal view : computer pov (how comp install data)
2) conceptual view[schema] : how data is connected, structured in logical view (how we pic the
data connected to each other) (one but very detail)
3) user view[subschema] : many view, different user, have different view
DML *data manipulation language

- M for manage (add,delete, update data)


- Put things into it (To populate the database)
- Use by DBMS to retrieve, process, and store data to/from databased
- Can be use to patch 3rd party application to the DBMS

DQL *data query language

- Q for question
- So questioning the database(survey databased,but doesn’t change the data)

Relational model

Two dimensional (column, row)

ER DIAGRAM (NI YANG KITA GUNA UNTUK BUAT DATABASE) YANG TIME TABLE TU

You might also like