Session 3 - Object Oriented Databases

Relationship type (in the real world) :

1. Many to many
2. One to many
3. One to one

UML used:

Structural:

1. Class Diagram
2. Object diagram
3. Component Diagram
4. Deployment diagram

 Behavioral:

1. Use Case Diagram
2. Sequence Diagram
3. Collaboration Diagram
4. State chart Diagram
5. Activity Diagram

Pointer Swizzling : Ketika data penuh, maka dilakukan swizzling.
Persistence : Keabadian objek (objek dapat bertahan lama walau aplikasinya sudah dihentikan)

Contoh:  
Excel atau SQL (non-volatile data, stored in harddisk not only RAM)
Data masih bisa dibuka lagi.

Concurrency control : Data dipakai oleh lebih dari satu user dalam waktu yang bersamaan.
Recovery Control : (?) Kalau sudah di commit, data harus bisa direcover kembali.


Object Oriented Characteristic, such as:

1. Inheritance : staff under person, so all the person is inherited (schema consistency (?)   Banyak subclass (child) menginherit satu superclass (parent)  (single inheritance)
2. Encapsulation :
3. Method :
4. Polymorphism
5. Extensibility :
6. Versioning : 

          Every data have version, so you can load the data when you need
          (monthly, weekly or daily).

Object Request Broker : yang menghubungkan 2 database system yang memungkinkan adanya email, web browser, word processor, spredsheet, etc.

Set : Collection unorder, readonly, non-duplicate
Bag : Duplicate able
List : Ordered

Array : Limited length
Dictionary : (?)

Subekti
Advance Database Lecturer