EXAMINATIONS 2015 TRIMESTER 1 S W E N A D V A N C E D D A T A B A S E D E S IG N A N D IM P L E M E N T A T IO N. Appendix

Size: px

Start display at page:

Download "EXAMINATIONS 2015 TRIMESTER 1 S W E N A D V A N C E D D A T A B A S E D E S IG N A N D IM P L E M E N T A T IO N. Appendix"

Darcy Day
5 years ago
Views:

EXAMINATIONS 2015 TRIMESTER 1 S W E N 4 3 2 A D V A N C E D D A T A B A S E D E S IG N A N D IM P L E M E N T A T IO N Instructions: Appendix Do not hand this Appendix in.

1 EXAMINATIONS 2015 TRIMESTER 1 S W E N A D V A N C E D D A T A B A S E D E S IG N A N D IM P L E M E N T A T IO N Instructions: Appendix Do not hand this Appendix in. Do not write your answers on this Appendix. Contents: 1. Clinics Database Description 2. A Selection of CQL 3.1 Statements 3. A Selection of MongoDB Methods 4. XML Schema Clinics.xsd 5. A Valid Clinics.xml Document 6. The Syntax of an Identity Constraint 7. An Approximate Structure of an XQUERY Query Page 1 of 14

2 1. Clinics Database Description 1.1. Overview The clinics database should contain data about clinics, doctors, patients, and examinations. The most important clinic business rules are: 1. Each doctor is a specialist for only one group of diseases. 2. There may be more than one specialist for the same group of diseases at a clinic. 3. Each examination is performed at a single clinic. 4. In each examination a doctor makes a diagnosis. 5. A patient may be examined for a group of diseases at most once in a day. 6. At a given clinic, for a given group of diseases, a patient is always examined by the same doctor. 7. At different clinics, the same patient may be examined by the same or a different doctor for a given group of diseases. 8. A patient is examined by another specialist if he/she suffers from a disease of another group. 9. A doctor may work for several clinics Description of Database Entities The clinics database should store minimally the following properties of a: Clinic: a) A unique name of the type string. b) An address of the type string. c) A set (or list) of disease group names (of the type string) that are practiced at the clinic. Doctor: a) A unique name of the type string. b) An address of the type string. c) The disease group name (of the type string) the doctor is a specialist for. Patient: a) A unique name of the type string. b) An address of the type string. c) A list of disease groups he/she suffers. Examination: a) The date of the examination of the type int having the format yyyymmdd. b) The diagnosis of the type string. Note: An examination is a ternary relationship between a clinic, a doctor, and a patient having above listed properties. Page 2 of 14

3 1.3. User Interface The database application should present the users with the following information: a) A list of all clinics with their data. b) For a given clinic a list of doctors who practice at the clinic with their personal data. c) For a given doctor the number of examinations he made on a given date at a given clinic. d) Full information about a given patient. e) For a given patient the most recent examination for a given disease group. The query output should contain: clinic s name, doctor s name, patient s name, disease group, diagnosis, and date Sample Data Clinic name address disease groups Panacea Clinic Lower Hutt Cardio-Vascular, General Surgery, Internal Diseases, Ophthalmology Recovery Guaranteed Clinic Upper Hutt Cardio-Vascular, Muscle and Bone Diseases, Pulmonary Diseases Doctors at Panacea Clinic name address disease group James Wellington Cardio-Vascular Joan Lower Hutt Internal Diseases John Wellington Cardio-Vascular Doctors at Recovery Guaranteed Clinic name address disease group Joan Lower Hutt Internal Diseases Mike Lower Hutt Pulmonary Diseases Matthew Porirua Cardio-Vascular Mary Upper Hutt Muscle and Bone Diseases Patients name address disease group Jim Lower Hutt Cardio-Vascular, Pulmonary Diseases Paul Upper Hutt Internal Diseases Ann Lower Hutt Cardio-Vascular Shirley Wellington Muscle and Bone Diseases Page 3 of 14

4 Examinations clinic doctor patient date diagnosis Panacea Clinic Panacea Clinic Panacea Clinic Recovery Guaranteed Clinic Recovery Guaranteed Clinic James Jim Heart Attack James Jim Clogged Arteries Joan Paul Diarrhea Matthew Jim Extra Systole Mary Shirley Arthritis Page 4 of 14

5 2. A selection of CQL 3.1 Statements KEY SPACE CREATE KEYSPACE <ks_name> WITH REPLICATION = <value> where the value of the REPLICATION may be: { class : NetworkTopologyStrategy <datacenter_name>: <replication_factor>, <datacenter_name>: <replication_factor>}; or {'class': 'SimpleStrategy','replication_factor': <integer>}; USE USE <ks_name>; CREATE TABLE CREATE TABLE <column_family_name> ( <column_name> <type>, [<column_name> <type>, ] PRIMARY KEY ((partition key), clustering key) ) [WITH <option_name> = <value> [AND <option_name> = <value> [ ]]]); Where: a partition or a clustering key is <column_name>, [<column_name>, ] an option_name and value can be: CLUSTERING ORDER BY (<column_name> ASC DESC), or COMPACTION = { class = LeveledCompactionStrategy } A primary key is the only compulsory entry of a table. It can also be defined inline: <column_name> <type> [primary key], but a table is allowed to contain one key only. CONSISTENCY CONSISTENCY <consistency_level>; where consistency_level is a value from the set {ONE, TWO, THREE, ALL, QUORUM,LOCAL_QUORUM, EACH_QUORUM} INSERT INSERT INTO <table_name> (<column_name_1>[, <column_name_2>, ]) VALUES (<value_1>[, <value_2>, ])[IF EXISTS]; Page 5 of 14

6 UPDATE UPDATE <table_name> SET <column_name> = <value> [WHERE <column_name> comp <value> [AND <column_name> comp <value> [ ]]]; where comp is a value from the set {=, <, >, <, >, <>}. SELECT SELECT {<list_of_column_names> *} FROM <table_name> [WHERE <column_name> comp <value> [AND <column_name> comp <value> [ ]]] [ORDER BY <list_of_column_names>] [LIMIT <value>]; where * replaces the list of all column names of a table. Collection Type column_name <collection_type><cql_type> where collection_type is one of set, list, map and cql_type is a type like: int, text, date, Page 6 of 14

7 3. A selection of MongoDB Methods Find db.collection.find(query, projection).<query modifier>[.<query modifier>] where: The parameter query is of the type document and specifies selection criteria using query operators. If omitted the method returns the whole collection. The parameter projection is of the type document and specifies the fields to return using projection operators. If omitted the method returns all fields in the documents matching the query document. Query Operators <field_name>: {$<operator>: <value>} <field_name>: {$<operator>: <value>, $<operator>: <value>} Equality comparison: <field_name>: <value> Some of the other operators: $ne, $gt, $gte, $lt, $lte. Projection Operators A projection document may either specify: A list of fields to return (designated by {<field_name>: 1}), or A list of fields to exclude (designated by {<field_name>: 0}) The exclusion of _id field can be mixed with fields to return Query Modifiers sort() limit() skip() Single Purpose Aggregation count() db.collection.count(query) The parameter query is of the type document and contains the query selection criteria. distinct() db.collection.distinct(field, query) where: The parameter field is of the type string and denotes the field for which the method returns distinct values. The parameter query is of the type document and contains the query selection criteria. Page 7 of 14

8 Pipelined Aggregation db.collection.aggregate([{<stage>},...]) A stage contains a stage operator and a stage document. A stage document may use expression documents as its parameters. An expression document contains an expression operator with an array of arguments. Stage Operators $group: $limit: $match: $group: $limit: $match: skip: $sort: $unwind: Pipeline Expression Operators {<operator>: [<argument1>,... ] } If an operator accepts a single argument: {<operator>: <argument>} Accumulator Expression Operators $addtoset $avg $first $last $max $min $push $sum Page 8 of 14

9 4. XML Schema Clinics.xsd <xsd:schema xmlns:xsd=" <xsd:element name="clinics" type = "ClinicsType"/> <xsd:complextype name = "ClinicsType"> <xsd:sequence> <xsd:element name="clinic" maxoccurs = "unbounded" type="clinictype"/> <xsd:element name="doctors" type="doctorstype" /> <xsd:element name="patients" type="patientstype"/> </xsd:sequence> <xsd:complextype name = "ClinicType"> <xsd:sequence> <xsd:element name = "Name" type = "xsd:string"/> <xsd:element name = "Address" type = "xsd:string"/> <xsd:element name = "Disease_Group" maxoccurs = "unbounded" type = "xsd:string"/> <xsd:element name = "Examination" minoccurs = "0" maxoccurs = "unbounded" type = "ExaminationType"/> </xsd:sequence> <xsd:complextype name="examinationtype"> <xsd:sequence> <xsd:element name="exam_doctor" type = "ExamDoctorType"/> <xsd:element name="exam_patient" type = "ExamPatientType"/> <xsd:element name="disease_group" type = "xsd:string"/> <xsd:element name="diagnosis" type = "xsd:string"/> </xsd:sequence> <xsd:attribute name = "date" type="xsd:int" use="required"/> <xsd:complextype name = "ExamDoctorType"> <xsd:attribute name = "name" type="xsd:string" use="required"/> <xsd:complextype name = "ExamPatientType"> <xsd:attribute name = "name" type="xsd:string" use="required"/> Page 9 of 14

10 <xsd:complextype name = "DoctorsType"> <xsd:sequence> <xsd:element name="doctor" maxoccurs = "unbounded" type = "DoctorType"/> </xsd:sequence> <xsd:complextype name="doctortype"> <xsd:sequence> <xsd:element name="name" type = "xsd:string"/> <xsd:element name="address" type = "xsd:string"/> <xsd:element name="disease_group" type = "xsd:string"/> <xsd:element name="doc_clinic" maxoccurs = "unbounded" type = "xsd:string"/> </xsd:sequence> <xsd:complextype name = "PatientsType"> <xsd:sequence> <xsd:element name="patient" maxoccurs = "unbounded" type = "PatientType"/> </xsd:sequence> <xsd:complextype name="patienttype"> <xsd:sequence> <xsd:element name="name" type = "xsd:string"/> <xsd:element name="address" type = "xsd:string"/> <xsd:element name="disease_group" maxoccurs = "unbounded" type = "xsd:string"/> </xsd:sequence> </xsd:schema> Page 10 of 14

11 5. A Valid Clinics.xml Document <?xml version="1.0" standalone="no"?> <Clinics> <Clinic> <Name>Panacea Clinic</Name> <Address>Lower Hutt</Address> <Disease_Group>General Sergery</Disease_Group> <Disease_Group>Internal Diseases</Disease_Group> <Disease_Group>Ophtalmology</Disease_Group> <Examination date = " "> <Exam_Doctor name = "James"/> <Exam_Patient name = "Jim"/> <Diagnosis>Heart Attack</Diagnosis> </Examination> <Examination date = " "> <Exam_Doctor name = "James"/> <Exam_Patient name = "Jim"/> <Diagnosis>Clogged Arteries</Diagnosis> </Examination> <Examination date = " "> <Exam_Doctor name = "Joan"/> <Exam_Patient name = "Paul"/> <Disease_Group>Internal Diseases</Disease_Group> <Diagnosis>Diarrhea</Diagnosis> </Examination> </Clinic> <Clinic> <Name>Recovery Guaranteed</Name> <Address>Upper Hutt</Address> <Disease_Group>Muscle and Bone Diseases</Disease_Group> <Disease_Group>Pulmonary Diseases</Disease_Group> <Examination date = " "> <Exam_Doctor name = "Matthew"/> <Exam_Patient name = "Jim"/> <Diagnosis>Extra Systole</Diagnosis> </Examination> Page 11 of 14

12 <Examination date = " "> <Exam_Doctor name = "Shirley"/> <Exam_Patient name = "Mary"/> <Disease_Group>Muscle and Bone Diseases </Disease_Group> <Diagnosis>Arthritis</Diagnosis> </Examination> </Clinic> <Doctors> <Doctor> <Name>James</Name> <Address></Address> <Doc_Clinic>Panacea Clinic</Doc_Clinic> </Doctor> <Doctor> <Name>Joan</Name> <Address>Lower Hutt</Address> <Disease_Group>Internal Diseases</Disease_Group> <Doc_Clinic>Panacea Clinic</Doc_Clinic> <Doc_Clinic>Recovery Guaranteed</Doc_Clinic> </Doctor> <Doctor> <Name>John</Name> <Address>Wellington</Address> <Doc_Clinic>Panacea Clinic</Doc_Clinic> </Doctor> <Doctor> <Name>Mike</Name> <Address>Lower Hutt</Address> <Disease_Group>Pulmonary Diseases</Disease_Group> <Doc_Clinic>Recovery Guaranteed</Doc_Clinic> </Doctor> <Doctor> <Name>Matthew</Name> <Address>Porirua</Address> <Doc_Clinic>Recovery Guaranteed</Doc_Clinic> </Doctor> Page 12 of 14

13 <Doctor> <Name>Mary</Name> <Address>Upper Hutt</Address> <Disease_Group>Muscle and Bone Diseases </Disease_Group> <Doc_Clinic>Recovery Guaranteed</Doc_Clinic> </Doctor> </Doctors> <Patients> <Patient> <Name>Jim</Name> <Address>Lower Hutt</Address> <Disease_Group>Pulmonary Diseases</Disease_Group> </Patient> <Patient> <Name>Paul</Name> <Address>Uppar Hutt</Address> <Disease_Group>Internal Diseses</Disease_Group> </Patient> <Patient> <Name>Ann</Name> <Address>Lower Hutt</Address> </Patient> <Patient> <Name>Shirley</Name> <Address>Wellington</Address> <Disease_Group>Muscle and Bone Diseses </Disease_Group> </Patient> </Patients> </Clinics> Page 13 of 14

14 6. The Syntax of an Identity Constraint <xsd:constraint_type name= constraint_name > <xsd:selector xpath= e1/ /en /> <xsd:field xpath= cn+1/ /field_name /> </xsd:constraint_type> where ei (1 < i < n) is an element, and cn+1 is either a simple and single element or an attribute, and constraint_type is one of: unique, key, keyref. 7. An Approximate Structure of an XQuery Query for $x in <xpath_expression> let $y:= <xpath_expression> [where <condition>] [order by] return element_constructor Useful functions: fn:doc() fn:distinct-values() Aggregate functions: fn:sum(),fn:count(),fn:average() ******************************************** Page 14 of 14 end

EXAM IN SEMI-STRUCTURED DATA Study Code Student Id Family Name First Name

EXAM IN SEMI-STRUCTURED DATA Study Code Student Id Family Name First Name EXAM IN SEMI-STRUCTURED DATA 184.705 12. 01. 2016 Study Code Student Id Family Name First Name Working time: 100 minutes. Exercises have to be solved on this exam sheet; Additional slips of paper will