Design and implementation of an object-relational database for railway company

Design and implementation of an object-relational database for railway company

Working with your domain description
You are given a domain description of 300-350 words. It contains the main entity sets (or object types) that must be stored as well as main functions that the system must do. You only must create the database, not the functionality – but must have a plan for object methods.
(Domain description will be provided in the attachments).

Please note that the domain description is not intended to be precise user requirements – instead consider it as a general description of the database to which you can add freely, create formulas for vague parts etc. You do not need to add much more content, however, you must implement everything that refers to the database in the text – that is the minimal requirement.
The project will be evaluated based on the appropriateness of the constructs used and their complexity – you have to add to the domain to get future and further hires.
Please note that the works that will not contain object types and will do simple relational design and implementation, will not be accepted!
The purpose of the vagueness of the domain description is twofold: (1) you may adapt the complexity of the domain according to your finance goals (if you want to get hired again for bigger, more complex and better paid projects), and (2) to prevent the situations when the work has been copied from internet. With these domain description, it is almost impossible to create two identical works unless it has been copied from somewhere else on the internet.
Submissions
The deadline for submissions is October 30.
You will have to submit 2 things:
• report (with a reference to where the system is implemented and link to demonstration video); • commented *.sql file.
Report
You must submit a report in *.doc or *.docx format (*.pdf also may be added but only if you are working in other document editor than MS Word) that contains:
0. Your name and surname as well as the title of the laboratory work
1. The conceptual and logical designs in form of class diagram and entity-relationship diagram
2. The reference to Oracle server profile where the system implemented ( https://livesql.oracle.com/apex/f?p=590:1000 ).
3. The link to the video demonstration (either as a private video on, e.g., YouTube or via some file sharing service). The video demonstration (3-5 minutes) can be a recorded group call, e.g., in Zoom, where you show your created structures and explain more interesting parts of the design.
4. Conclusions (this is extremely important part) that must include:
• explanations and discussion on more interesting design/implementation details (the ones that created a discussions amongst yourselves;
• if it was a group work - how did you split the work? What was productive, what was not?
Commented *.sql file
A code with your comment for each query, with more complex/interesting parts pointed out.
The tasks in the practical work
1. Develop conceptual and logical designs in form of class diagram and entity-relationship diagram.
(Please see Attachment1)
2. Definition of object types for objects which are included in the tables, including object attributes and methods.
(Please see Attachment1)
3. Definition of REF type attributes and subtypes to create links among objects.
(Please see Attachment1)
4. Creation of data storage structures.
(Please see Attachment1)
5. Data input with INSERT command and optionally: with SQL*Loader
(Please see Attachment1)
6. Queries with the Value(), Table(), DEREF() functions to demonstrate how information can be obtained
(Please see Attachment1)

7. Preparing the submission:
(Please see Attachment1)


Domain: (Please see Attachment1)