代写FIT9132 Introduction Databases - Assignment 2代写R语言

FIT9132 Introduction Databases - Assignment 2

Creating, Populating and Manipulating Databases - Pets First (PF)

Purpose

Students will be asked to implement, via SQL, a small database in the Oracle RDBMS from a provided logical model case study, followed by the insert of appropriate data to the created tables. Once populated the database will be used to carry out specified DML commands and make specified changes to the database structure via SQL. Students will then use SQL and NoSQL to write queries to produce specified output. This task covers learning outcomes:

1. Apply the theories of the relational database model.

3. Implement a relational database based on a sound database design.

4. Manage data that meets user requirements, including queries and transactions.

5. Contrast the differences between non-relational database models and the relational database model.

Your task

This is an open book, individual task. The final output for this task will be a set of tables and data implemented in the Oracle RDBMS. In addition students will create a set of relational (Oracle) and non relational (MongoDB) queries which meet the user requirements.

Value

40% of your total marks for the unit

Due Date

Wednesday, 5th June 2024, 11:55 PM

(note: staff support is unavailable after business hours)

Submission

● Via Moodle Assignment Submission

● FIT GitLab check ins will be used to assess history of development

Assessment Criteria

● Application of relational database principles.

● Handling of transactions and the setting of appropriate transaction boundaries.

● Application of SQL statements and constructs to create and alter tables including the required constraints and column comments, populate tables, modify existing data in tables, and modify the "live" database structure to meet the expressed requirements (including appropriate use of constraints).

● Application of SQL select statements to produce outputs that meet user requirements.

● Mapping of relational database data into non relational database data structure.

● Application of MongoDB operations to produce outputs that meet user requirements.

INSTRUCTIONS

Pets First has several clinics distributed across the suburbs. For each clinic, they record the clinic's ID (which is used to identify the clinic), the clinic's name, its address, and the clinic's contact phone number. The practice has several veterinary surgeons (vets) who work in these clinics. A vet is assigned to one clinic as their home (or base) clinic. A clinic must have at least one vet assigned to it as the vet's base clinic to function.

The details Pets First records about a vet are their vet ID (used to identify a vet), the vet's given name and family name, the vet's contact phone number, and the date they were first employed by Pets First.

Some Pets First vets are specialists in areas such as oncology, cardiology, dermatology, etc. If the  vet is a specialist, their area of specialisation is also recorded as part of their vet details (specialist  vets only specialise in one particular area). These specialist vets, as well as having a home clinic (their base clinic) where they accept general visits, also rove around all clinics when their specialist skills are required to treat an animal.

Each clinic appoints one of the vets based in the clinic (i.e. those vets assigned to the clinic as their home clinic) as the head vet for that clinic.

Pet owners, who are each assigned a unique owner ID, have their given name and family name recorded by the practice. The practice also records the owner's contact phone number. Each owner may have one or more pets; for each pet, the practice records a unique animal ID, the animal's name, the year the animal was born and the type of animal they are, for example, a cat. Each animal is only recorded as being owned by one owner. PF also records if an animal is currently alive or not.

When an animal needs veterinary attention (such as annual injections) or is ill, the owner books a visit with a vet. During the booking, the date and time of the visit, the visit length, the required service(s), the clinic, and the attending vet are recorded (this attending vet may be one based at this particular clinic, i.e., this is their home clinic, or the visit may need the services of a roving specialist vet).

On the scheduled visit date, the owner brings their pet to the clinic to be attended to by the vet.

During the visit, the practice records the pet's weight for this visit and any notes that the vet needs to make about the pet's condition. If required, the vet also updates the length of the visit and the required service(s) based on the examination.

The owner may also visit one of the practice's clinics without making any booking, e.g., for emergency treatment.

Every visit must involve at least one service charge; however, there may be no drug charges.

Drugs and services have a standard charge, which must be recorded in the database. A particular service will only be charged once for a visit. If necessary, the vet will adjust the cost charged to cover any "extra" work under this service or to give a discount. For example, using the invoice below - the standard service cost for a skin allergy treatment (S009) is $85, but here on the sample invoice, the vet has given a $5 discount and charged only $80.

During a visit, the attending vet may need to prescribe drugs for the animal. The practice identifies a drug by a unique drug ID and records the drug's name and usage instructions (for example, "Analgesic for post-surgery pain relief; 0.01 mg per kg"). When a drug is prescribed during a visit, the actual drug dose and frequency of administration are recorded. The line cost listed on an invoice is the total cost for items listed on that line; for example, in the invoice below, the $13.5 charge for corticosteroid is the total charge for the 3 items.

Some visits require further follow-up visits, the system needs to record, for these subsequent visits, which visit generated the follow-up. A given visit may require multiple follow-up visits to address an issue identified in the initial diagnosis. For example, the pet may have an infected wound from a fight. The first visit (e.g. visit id 21) for this issue results in antibiotics being given and the wound being stitched. Follow-up visits may be required for example, to remove the stitches (e.g. visit id    23), check the wound healing (e.g. visit id 25), provide further antibiotic injections (e.g. visit id 27), etc. All of these follow-up visits are related to the original visit (visit id 21).

Based on these requirements, a data model has been created for PF:

The schema/insert file for creating this model (pf_initialSchemaInsert.sql) is available in the archive ass2_student.zip. This file partially creates the Pets First tables and populates several of them (those shown in purple on the supplied model). You should read this schema carefully and be sure you understand the various data requirements.

IMPORTANT points for you to observe when completing this assignment are:

1.   The ass2-student.zip archive also contains seven script. files to code your answers in. You MUST ensure these files are regularly pushed to the GitLab server so that a clear development history is available for the marker to verify your work (a minimum of fourteen pushes are required - 2 pushes per file). In each file, you must fill in the header  details with your name and student ID before beginning work. Your SQL script. files must not include any SPOOL or ECHO commands. Although you might include such commands when testing your work, they must be removed before submission (a -10 mark grade penalty will be applied if your documents contain spool or echo commands).

2.  You are free to make assumptions if needed. However, your assumptions must align with the details here and in the Ed Assignment 2 forum and must be clearly documented (see the required submission files).

REMEMBER, you must keep up to date with the Ed Assignment 2 forum, where further clarifications may be posted (this forum is to be treated as your client). Please ensure you do not post anything that includes your reasoning, logic or any part of your work to  this assignment forum, as doing so violates Monash plagiarism/collusion rules.

3.  Views must not be used in arriving at any solutions for the tasks you must complete as part of this assessment.

4.  When handling dates with SQL, the default date format must not be assumed; you must use the TO_DATE and TO_CHAR functions where appropriate.

5.  ANSI joins must be used where the joining of tables is required.

6.   In completing the following tasks, you must design your test data so that you always get output for the queries specified below - this may require you to add further data as you   move through completing the required tasks. Such extra data MUST be added as part of Task 2 (i.e. as part of your test data load). Queries that are correct but do not produce any output (“no rows selected” message) using your test data will lose 50% of the  marks allocated. So, you should carefully check your test data and ensure it thoroughly  validates your SQL queries.

Steps for working on Assignment 2

1. Download the Assignment 2 Required Files zip archive (ass2-student.zip) from Moodle

2. Extract the zip archive and place the contained files in your local repository in the folder /Assignments/Ass2

Do not add the zip archive to your local repo.

3. Examine the extracted files, i.e. read carefully through them and ensure you understand their content.

4.  In each supplied script, fill in the header details with your name and student ID. Then, add, commit and push them to the FITGit Lab server.

5. Run pf_initialSchemaInsert.sql from the supplied zip archive to set up the initial state of the database

6. Write your answer for each task in its respective file (e.g. write your answer for task 1 in T1-pf-schema.sql and so on).

7. Save, add, commit and push the file/s regularly while you are working on the assignment

8. Finally, when you have completed all tasks, separately run each SQL or Mongo as a script (not as individual statements) and ensure there are no errors. Upload all required files   from your local repository to Moodle. Check that the files you have uploaded are the correct files (download them from Moodle into a temporary folder and check they are correct). After you are sure they are correct, submit your assignment.

For all assignment tasks, your final script. must run as a script. without errors except for SQL   errors generated by the DROP TABLE/DROP SEQUENCE statements. Any task's script that   runs with an error will receive a maximum grade of half of the task's marks -1. For example if your task 1 script runs with an error, regardless of the contained code, your maximum grade will be 15/2 => 7.5 - 1 = 6.5 marks. This will be applied even if the error is simply a forgotten semicolon.   Thus, please carefully check that your final scripts for all tasks run without error.

In arriving at your solutions for assignment 2 you are ONLY permitted to use the SQL/NoSQL structures and syntax which have been covered within this unit:

●   Topic 6 Workshop and Applied 7 - Creating & Populating the Database

●   Topic 7 Workshop and Applied 8 - Insert, Update, Delete (DML) and Transaction Management

●   Topic 8 Workshop and Applied 9 - SQL Part I - Basic

●   Topic 9 Workshop and Applied 10 - SQL Part II- Intermediate

●   Topic 10 Workshop and Applied 11 - SQL Part III - Advanced

●   Topic 11 Workshop and Applied 12 - Non-Relational Database

As detailed above, SQL/NoSQL syntax and commands outside of the covered work will NOT be accepted/marked.

Views must not be used in completing these tasks.

You must also keep up to date with the Ed Assignment 2 forum where further clarifications may be  posted. Please ensure you do not publicly post anything that includes your reasoning, logic, or any part of your work to this forum; doing so violates Monash plagiarism/collusion rules and   has significant academic penalties. Attend a consultation session or use a private Ed post to raise  such questions.

GIT STORAGE

Your work for these tasks MUST be saved in your individual local working directory (repo) in the   Assignment 2 folder and regularly pushed to the FIT GitLab server to build a clear history of the development of your approach. A minimum of fourteen pushes to the FIT Git Lab server is required (2 pushes per file). Please note that fourteen pushes are a minimum; we expect significantly more in practice. All commits must include a meaningful commit message that clearly describes what the particular commit is about and must be correctly assigned to your valid GitLab author.

You must regularly check that your pushes have been successful by logging in to the FIT Git Lab server's web interface; you must not simply assume they are working. Before submission via

Moodle, you must log in to the Git Lab server's web interface and ensure your submission files are present and their names are unchanged.

Assignment Tasks

TASK 1: DDL [15 mks]

ENSURE your ID and name are shown at the top of any file you submit.

For this task, you must add to T1-pf-schema.sql the CREATE TABLE and CONSTRAINT definitions, which are missing from the supplied partial schema script, in the positions indicated by the script's comments.

The table below details the attributes' meaning in the missing two tables. You MUST use exactly the same relation and attribute names shown in the data model above to name the tables and attributes you add. The attributes must be in the same order as shown in the model. These new  DDL commands must be hand-coded, not generated in any manner (generated code will not be marked).

To test your code, you must first run the provided script pf_initialSchemaInsert.sql to create the other required tables. pf_initialSchemaInsert.sql contains the drop commands for all tables in this model at the head of the file. If you have problems with task 1 simply rerun pf_initialSchemaInsert.sql, which will cause all tables to be dropped and correct the issues in your script. DO NOT add drop table statements to T1-pf-schema.sql

TASK 2: INSERT [20 mks]

Before proceeding with Task 2, you must ensure you have run the file pf_initialSchemaInsert.sql (which must not be edited in any way) followed by the extra definitions that you added in Task 1 above (T1-pf-schema.sql).

Load the VISIT, VISIT_DRUG and VISIT_SERVICE tables with your own test data using the supplied T2-pf-insert.sql script. file. Write SQL commands that will insert as a minimum (i.e. you may and should insert more) the following sample data:

(i)      10 VISIT entries

●    Include at least 5 different animals

●    Include at least 3 different vets

●    Include at least 3 different clinics

●    Include at least 2 follow-up visits

●    Include at least 8 completed visits and 2 incomplete visits (i.e. future visit bookings)

(ii)      15 VISIT_SERVICE entries

●    Include at least 4 visits that require more than one service in a single visit

(iii)      10 VIST_DRUG entries

●    Include at least 2 visits with more than one drug prescribed in a single visit

In adding this data, you must ensure that the test data thoroughly tests the model as

supplied, to ensure your schema is correct (you are not required to submit or code fail tests, all insert statements must execute correctly).

Your inserted data must conform. to the following rules:

1.  You may treat all the data you add as a single transaction since you are setting up the initial test state for the database.

2.   The primary key values for this data should be hardcoded values (i.e. NOT make use of sequences) and must consist of values below 100.

3.   Dates used must be chosen between the 1st April 2024 and 30th June 2024.

4.   The data added must be sensible (e.g., the follow-up visit date time should be after the previous visit’s date time, the drug line cost must be correctly calculated, etc.).

For this task ONLY, Task 2, you may manually look up and include values for the loaded

tables/data directly where required. However, you can still use SQL to get any non-key values if you wish.

In carrying out Task 2, you must not modify any data or add any further data to the tables populated by the pf_initialSchemaInsert.sql script. Design your test data so that you get output for the SQL scripts/queries specified below - this may require you to add further data as you complete the required tasks.

TASK 3: DML [20 mks]

Your answers for this task must be placed in the SQL file T3-pf-dml.sql For this and all subsequent Tasks, you are NOT permitted to:

●  manually lookup a value in the database, obtain its primary key, or manually obtain the highest/lowest value in a column,

●  manually calculate values external to the database, e.g. on a calculator and then use such values in your answers. Any necessary calculations must be carried out as part of

your SQL code or

●  assume any particular contents in the database - rows in a table are potentially in a constant state of change

Your answers must recognise that you are dealing with only a very small sample snapshot of a multiuser database; as such, you must operate on the basis that there will be more data in all of the database tables than you currently have access to. Thus, data will be in a constant state of change. Your answers must work regardless of the extra quantity of this extra "real" data  and the fact that multiple users will operate in the tables simultaneously. You must consider this aspect when writing SQL statements.

For any following SQL tasks, your SQL must correctly manage transactions and use sequences to generate new primary keys for numeric primary key values (under no circumstances may a new primary key value be hardcoded as a number or value).

You must ONLY use the data as provided in the text of the questions.

For Task 3, you must complete the following sub-tasks in the same order they are listed. Where you have been supplied with a string in italics, such as Bayside Veterinary Clinic, you may search in the database using the string as listed. Where a particular case for a word is provided, you must only use that case (same spacing, case, etc) in your SQL code. When a name is supplied, you may break the name into first name and last name. For example, Olivia SMITH can be split into Olivia and SMITH; again, note that the case must be maintained as it was supplied. Failure to adhere to these requirements, such as changing the case of a provided string, will result in a grade penalty.

(a) An Oracle sequence will be implemented in the database to insert records for the VISIT table.

Provide the CREATE SEQUENCE statement to create a sequence that could be used to provide primary key values for the VISIT tables. This sequences must start at 100 and increment by 10. Immediately before the create sequence command, place an appropriate DROP SEQUENCE command so that the sequence wil be dropped before being created, if it exists. Please note that this is the ONLY sequence that can be introduced and used in Task 3. [1 mark]

Questions 3b, 3c, 3d and 3e are related questions. You can use the information below as needed in any part of Task 3.

(b) Jack JONES, a current customer, called Pets First to book a visit for Oreo, his rabbit which was born on 01 Jun 2018. The visit is scheduled for 19 May 2024 at 2 PM for 30 minutes.   He indicated that the visit is for general consultation (service code: S001) with Dr. Anna

KOWALSKI at Bayside Veterinary Clinic (clinic id: 3). You may assume that there is only one customer with such a name and Jack only has one rabbit born on such a date. You  may also assume that there is only one vet with such a name in the system. Take the necessary steps in the database to record the required entries for this visit booking. [5 marks]

(c) On 19 May 2024, Jack brought Oreo to the clinic as scheduled. Dr. Anna KOWALSKI

examined Oreo and found an ear infection. She decided to record an ear infection treatment service only and charge Jack the standard cost for this treatment. She gave (and charged) 1 bottle of Clotrimazole to Jack. You may assume that there is only one service named ear infection treatment and one drug named Clotrimazole in the system.

Dr. KOWALSKI also scheduled a follow-up visit for Oreo at 2 PM seven days after this visit for another ear infection treatment at the same clinic.

Make these required changes to the database data. You may make up (invent) any other required information when making these changes. [10 marks]

(d) On 21 May 2024, Jack called PF and cancelled Oreo’s 19 May follow-up visit since he has to go overseas for a work emergency.

Make these required changes to the data in the database. [4 marks]

TASK 4: DATABASE MODIFICATIONS (13 marks):

Your answers for these tasks (Task 4) must be placed in the supplied SQL script.

T4-pf-mods.sql

The required changes must be made to the "live" database (the database after you have completed tasks 1, 2 and 3). You MUST not edit and execute your schema file again. Before carrying out the work below, please ensure that you have completed tasks 1, 2 and 3 above.

If, in answering these questions, you need to create a table, please place a drop table statement immediately before your create table statement.

(a) PF would like to determine the total number of times each service was provided in a visit where the charge made was lower or higher than the standard cost (i.e., not charged at the standard cost). Add a new attribute that will record this requirement. The default value for this new attribute is 0.

Based on the data currently stored in the system, this attribute must be initialised to the number of times each service was provided in a visit and not charged at its standard cost.

As part of your solution, provide appropriate select and desc statements to show the changes you have made. Select to show any data changes that have occurred, and desc tablename, e.g., desc customer, to show any table structural changes. [5 marks]

(b) PF would like to allow the pet’s owner to pay for the visit's cost in instalments, i.e. the pet’s owner can pay each visit's cost via multiple payments across several dates and   times. PF also wants to record the payment method for each payment. The owner can pay the cost/part of the cost by Card or Cash. PF plans to include other payment methods in the future.

Change the database structure to support these new business rules. All currently completed visits in the system must be recorded as being fully paid on their visit date. The payment method for these visits must be recorded as Historical.

As part of your solution provide appropriate select and desc statements to show the changes you have made. Select to show any data changes that have occurred and desc tablename e.g. desc customer to show any table structural changes. [8 marks]