70 likes | 196 Vues
This project by Aaron Klor and Dan Matz from Missouri State University focuses on developing a self-checkout shopping cart system utilizing DB4O, an object-oriented database system. The project covers key functionalities including product management (add/edit/remove), user management, and transaction handling. While embracing an object-based approach, it emphasizes methods for database interactions relevant to high-order programming languages. The document also touches on the relevance of ER diagrams, schema diagrams, and constraints in an object-oriented context, offering insights into modern database design.
E N D
Self Checkout Shopping Cart CSC 335: Database System Concepts Term Project Aaron Klor and Dan Matz Missouri State University
Functionality Recap • Transacting • Administrating • Product add/edit/remove • User add/edit/remove • Transaction view/delete/output
Database • Object database • NOT Relational database • NO SQL • Entirely object based • Just “store” objects • Well suited for high-order, object-oriented languages
DB4O • Database 4 Objects - http://www.db4o.com/ • Single-file database • Similar to SQLite • Can be configured for client/server • Available for Java and .NET languages • GPL license model
DB4O Usage • Import library • Database access methods/classes
Objects • Product, Transaction, User • All extend DatabaseObject • Database Object • Provided by us • Abstract class • Provides super type • ID • ImageLocation
Not Relational, But • Some terms still apply: • ER Diagramming still useful • Specialization important – “IS A” • Schema diagrams still useful • Constraints • Foreign keys • Functional dependencies • Others do not • Normal forms • Used for column normalization – No columns!