Data Management Systems: Assignment 1, Southern Cross University

Desklib provides solved assignments and past papers to help students succeed.

SOUTHERN CROSS UNIVERSITY
ASSIGNMENT COVER SHEET
For use with online submission of assignments
Please complete all of the following details and then make this sheet the first page of each file of your
assignment – do not send it as a separate document.
Your assignments MUST be submitted as either Word documents, text documents with .rtf extension
or as .pdf documents.
Student Name:
Student ID No.:
Unit Name: Data Management Systems
Unit Code: DTB91001
Tutor’s name:
Assignment No.: Assignment 1
Assignment Title:
Due date:
Date submitted:
Declaration:
I have read and understand the Rules Relating to Awards (Rule 3 Section 18 – Academic
Misconduct Including Plagiarism) as contained in the SCU Policy Library. I understand
the penalties that apply for plagiarism and agree to be bound by these rules. The work I am
submitting electronically is entirely my own work.
Signed:
(please type
your name)
Date:

Assignment 1
REPORT
BY <Insert your name>

Table of contents:
Contents
Table of contents:...........................................................................................................................................3
Entity Relationship Diagram..........................................................................................................................4
Part A: Analysis.............................................................................................................................................5
1. Client Business Rules........................................................................................................................5
2. Assumptions Made.............................................................................................................................5
3. Naming Conventions.........................................................................................................................5
4. Data Types Chosen............................................................................................................................5
Part B: Testing Queries..................................................................................................................................6
B.6.1 Workshop Enrolment List..........................................................................................................6
B.6.2 Workshop Count List.................................................................................................................6
B.6.3 Student Transcripts....................................................................................................................6
B.6.4 Student Assessment Totals........................................................................................................6

Entity relationship diagram
Student enrollment system ERD

PHPMyAdmin diagram

Part A: analysis
1. Rules of client business:
The major rule includes the primary keys which are uniquely defined. The keys like
primary and foreign keys used for data extraction. The foreign keys are the primary keys
which are used in the other table. Defining the relationships between the tables are
important and essential.
2. Naming conventions:
It includes the column use for data defining.
3. Assumptions:
Primary key cannot be similar for two different tables. Primary table of one key is the
foreign key for the other table. These are the assumptions that are used to extract data
from one table to another.
4. Chosen data types

The attributes in the table are:
 StudentID: it is the primary key which cannot be similar for two students.
 LastName: it is for the last name of the student whose data type is varchar.
 Firstname: this is the first name of the student whose data type is varchar
 City: it is information of the city to which the student belongs and the data type is
varchar
 Address: this stores the student’s address whose data type is varchar
 State: this is the state information of the student whose data type is varchar
 Phone: the data type is integer which stores the contact number.
 Postalcode: It is the integer value
 Email: this attribute stores the email of the student and is declared as the varchar
 AssessmentID: it is the primary key which cannot be similar for two students.
 UnitOfferingID: this is defined as the foreign key. It should not be null and should
be in integer or character.
 DueDate: this is the due date of the assessment. The data type used is varchar.
 AssessmentName: this is the name of the assessment and varchar data type is
used.
 PossibleMarks: t is the attribute whose data type is integer
 Description: varchar data type is used.

 CourseName: the varchar data type is used which stores the name of the course
 Notes: the varchar data type is used and it contains the notes of the course
 Creditpoints: it store the points of the credit and the data type use in integer
 CourseCode: primary key and cannot be same for the two course codes
 AssessmentID: it is the primary key which cannot be similar for two students.
 StudentID: it is the primary key which cannot be similar for two students.
 MarksAwarded: the awarded marks are stored here
 DateSubmitted: this include the information of the submission date
 DaysExtension: this is the data for the extension which uses the integer data type

 StaffID: it is the primary key which cannot be similar for two staff members
 LastName: it is for the last name of the student whose data type is varchar.
 Firstname: this is the first name of the student whose data type is varchar
 Phone: the data type is integer which stores the contact number.
 Email: this attribute stores the email of the student and is declared as the varchar
 OfficeLocation: it is the address of the office location whose data type is varchar
 Campus: this is the detail of the Campus
 UnitName: this is the name of the unit
 UnitCode: the key is primary so that the different units will have unique code
 Prerequisite: it uses data type integer
 Description: this is the attribute which stores the unit’s description and the data
type used is varchar
 UnitOfferingID: it is the primary key which does not allow to same ID for
different unit offerings
 UnitCode: the key is foreign so that the different units will have unique code
 Session: it stores session and the data type is used is integer

 Year: it stores year
 StaffID: it is the foreign key which cannot be similar for two staff members
 Locations: it store the information of the location
 WorkshopID: it is the primary key and cannot have multiple entries
 StaffID: it is the foreign key which cannot be similar for two staff members
 Locations: it store the information of the location
 UnitOfferingID: it is the foreign key which does not allow to same ID for
different unit offerings
 Campus: this is the detail of the Campus
 ClassTimes: it stores he class timings
 Weekday: the data type used is varchar and it stores the information of the
weekdays
 WorkshopID: it is the primary key and cannot have multiple entries
 StudentID: it is the primary key which cannot be similar for two students.

 UnitEnrolmentID: this is the primary key which does not store same ID
 Finalgrade: it stores the final grades
 Session: it stores session and the data type is used is integer
 Year: it stores year
 StudentID: it is the primary key which cannot be similar for two students.
 UnitOfferingID: it is the foreign key which does not allow to same ID for
different unit offerings
 EnrolmentType: it stores the enrolment’s type
 StudentID: it is the primary key which cannot be similar for two students.
 CourseCode: primary key and cannot be same for the two course codes
 EnrolmentDate: this stores the information of the enrolment’s date
 Status: it shows the status of the course

Tables Created
Figure 1Assessment
Figure 2 cource enrollement
Figure 3course
Figure 4 student
Figure 5 student assessment create query