CT014-3.

5-2-Database and Web Database Systems

Group Assignment

Page 1 of 11

Database and Web Database System (DTWDS)Group Assignment Learning Outcomes: Create, alter and remove relational tables, indexes and data using an appropriate database language. Design and justify the design of a database system and select, justify the selection and exploit any associated underpinning technologies, including web based technologies.

The Lotus University Lecturer Schedule Management Case Study The Lecturer Schedule Management Systemis a database system which can be used by lecturers and students to plan consultations, FYP presentation schedules, and Midpoint schedules and integrate these with the lecturers time table. From this system, lecturers can place and publish the schedule for the consultation hours while students are able to book appointments/ slots for the published consultation schedule. This system is further described below: Time Table: A. Admin Publishing lecturer time table The schedule for the intake will be published by admin. The published time table is based on availability of venue (lab/classroom/auditorium), intake size, and modules. Admin will be able to update the time table anytime in a year based on intakes and change of venues. They should be able to modify the time table in case of any request for change is submitted. B. Lecturer View the published time table Once the intake time table is published,a lecturer can view his/her own time table. The information viewed consists of time, hours, date and day of the class and the venue. Lecturers will not be able to modify the time table but they can now set new or edit consultation hours.

Level 2

Asia Pacific Institute of Information Technology

2011

CT014-3.5-2-Database and Web Database Systems

Group Assignment

Page 2 of 11

C. Student View the published lecturers time table Once the intake time table is published, student can view and check the time table by selecting the lecturers name. The information viewed consists of lecturer name, time, date and day of the class and the venue.

Final Year Project (FYP) presentation & Mid-Point Presentation: A. Admin Publishing presentation schedule The presentation schedule will be added by the admin upon confirmation from the students and lecturers of their availability. The admin will have to update the slots chosen for the lecturer and/or advisors individually. He or she should ensure that there are no clashes in time table before updating the schedule. The admin personnel should be able to edit/delete the presentation schedule in case there is a change. B. Lecturer View the published schedule Once the presentation is published,a lecturer can view his/her own time table. The information viewed consists of time, hours, date and day of the presentation and the venue. Lecturers will not be able to modify the presentation or time table but they can now set new or edit consultation hours. C. Student View the published lecturers schedule Students can view the selected lecturers schedule. The schedule will include the lecturers class time table and presentation time table. They will not be able to modify the schedule.

Level 2

Asia Pacific Institute of Information Technology

2011

CT014-3.5-2-Database and Web Database Systems

Group Assignment

Page 3 of 11

Consultation Hour: A. Lecturer Publishing the consultation schedule The schedule for the consultation hour will be published by lecturers. The published consultation schedule is based on office hours, from 8.30am until 6.00pmweekdays, from Monday until Friday. In order to publish the consultation schedule, the information that should be defined by lecturers are: i. ii. iii. The venue (location of the campus and the room) The time and date (for weekdays; Monday, Tuesday, Wednesday, Thursday and/or Friday) The date validation of the consultation hour (from the date that the consultation hour was scheduled until when)

View, modify or cancel the published consultation slot The published consultation schedule can be viewed by lecturers for revising purposes. The details of the published consultation schedule are venue (location and room), time and date of the consultation and the date validation of the consultationschedule. Lecturers are also able to modify the published consultation slots by modifying the lecturers availability or even cancel any particular slot that has been publishedbut yet to be booked by any students in the schedule.

View the student appointment or cancel the booked consultation slot Once the student books the consultation slot, lecturers can view the detail of the students appointment. The detail of the appointment consists of students ID, students name and the booked slot information which are time, date and day. If a lecturer is unable to attend the booked consultation slot, he or she can cancel the booked slot and the lecturers will give a remark as the cancellations reason. The notification of the cancellation will be sent to the student who booked the slot. Lecturers will also receive a notification from the student if the student has cancelled the booked consultationslot. The information of the slots cancellation by the student is student ID, student name and the booked time and date.

Level 2

Asia Pacific Institute of Information Technology

2011

CT014-3.5-2-Database and Web Database Systems

Group Assignment

Page 4 of 11

Flow chartfor the consultation process (for lecturers)

Start

Publish the consultation schedule

View/ modify or cancel the published consultation schedule

View the student appointment for the consultation slot If it cancelled Students appointment Not cancelled Meet the student for the consultation session

End

Level 2

Asia Pacific Institute of Information Technology

2011

CT014-3.5-2-Database and Web Database Systems

Group Assignment

Page 5 of 11

B. Student View the published consultation schedule Once the consultationscheduleis published, students can view and check the available slots in the consultation schedule of a particular lecturer. The information of the available consultation sessions will consist of lecturer name, time, date and day of the consultation and the venue. Make a booking for the consultationslot Students will set an appointment with the lecturer once the consultationschedule has been published. The information that should be defined by the 1student in order to place the appointment is as following: Students ID Students name Select the date, time and day of the consultation slot.

i. ii. iii.

Once the student places the appointment for the consultation session, the appointment will be submitted to the lecturer. Studentscan also check and revise the details of the placed appointment. The detail of the appointment is as following: Students ID Students name Select the date, time and day of the consultations slot. Status of the appointment (to see whether the consultation slot has been cancelled or not)

i. ii. iii. iv.

If the studentis unable to attend the booked consultation slot, he or she can cancel the booked slot. The notification of the cancellation will be sent to the lecturer.

Login access: LecturersMUST login into the system in order to publish the consultation. Students need to login into the system before they can make consultation appointments with a particular lecturer. Admin personnel must login to the system to manage the lecturers time table and FYP/Midpoint presentation scheduling.

Level 2

Asia Pacific Institute of Information Technology

2011

CT014-3.5-2-Database and Web Database Systems

Group Assignment

Page 6 of 11

Flow chart for the consultationappointment process (for students)

Start

View the consultation schedule

Make an appointment for the published consultation schedule

If it is cancelled View and check the appointments status

Not cancelled Meet the lecturer for the consultation session

End

Level 2

Asia Pacific Institute of Information Technology

2011

CT014-3.5-2-Database and Web Database Systems

Group Assignment

Page 7 of 11

Job Tasks: Design Design a database solution for the given scenario and document the following: 1. Produce a complete Entity Relationship (ER) diagram (include attributes, keys and participation constraints) for the above mentioned scenario. State and justify all business rules applicable in your design. 2. Map your ER diagram to its corresponding relational schema and normalise all relations up to third normal form clearly illustrating the normalisation process undertaken. 3. Document the Normalisation process that defines the sets of entities obtained. Implementation Use any Enterprise Database and an appropriate web based front-end development tool to implement your solution based on the design produced above, namely: 1. Produce a set of tables and relationships based on your Entity Relationship Diagram that represent a fully normalised data model suitable for the Lotus Lecturer Schedule Management System. You should identify the primary keys in each table and each field's data type.Include appropriate integrity constraints in your tables. A copy of the relationship diagram between all tables in the database (relational schema) should be attached in your documentation. Corresponding DDL statements for the tables and DML statements (extracted from your coding) should be documented. Produce an application which meets the minimum requirements: a) b) c) d) A login menu to control access of the Admin personnel, lecturers and students. Interactive forms with validations and tab control. Standardised buttons (Add, Edit, Update, Save, Delete ... etc) Data Entry forms for all modules mentioned above. Appropriate menu management. Database: Tables / Entities with relationship between them. Identify the primary keys and foreign keys (if any). Attributes which are not identified in the above case study should be created to meet the domain needs.

2.

3.

4.

Level 2

Asia Pacific Institute of Information Technology

2011

CT014-3.5-2-Database and Web Database Systems

Group Assignment

Page 8 of 11

e)

Reports : i) ii) iii) iv) Lecturer ConsultationONLY (Weekly &daily) report. Lecturer Class Time Table ONLY (Weekly & daily) report. Lecturer Presentation Schedule ONLY report. Lecturer Full Schedule (including time table, presentation & student consultation) Weekly report.

Note: You are required to document the application interface, search / query display and report in your documentation. Include also any justifications you deem is necessary. 5. You are expected to include appropriate validations within your application.

Documentation Minimum requirement of your documentation: 1. 2. 3. 4. 5. 6. 7. 8. Introduction of the system ER Modelling Business Rules Normalisation Process Database Schema / Diagram Data Dictionary SQL Statements (DDL & DML) System Screen Shots with brief explanations

Level 2

Asia Pacific Institute of Information Technology

2011

CT014-3.5-2-Database and Web Database Systems

Group Assignment

Page 9 of 11

General Requirements: In this assignment you are required to: Form a group of 3 in a group. Design and implement a solution to a business problem. Implement the solution using any Enterprise database and an appropriate web based frontend development tool of your choice. Document the solution as set out in the assignment requirements. Submit Workload Matrix (describing the individual components handled) signed by all group members, attached in the documentation. Submit Marking Scheme attached in the documentation (last page). Submit a CD containing the softcopy of both your documentation and application. It is vital that you keep an electronic copy of the submitted file(s) as your receipt. The onus will be on you to produce this in case your disks/CDs become unreadable for some reason. Presentation schedules will be published at a later date. Note: It is acceptable for discrete activities of this assignment to be undertaken by individual group members. However, it is essential that all group members understand the presentation in its entirety. At the end of the demonstration your group will be asked a series of questions to explore your understanding and analysis of the given problem. Responses to these questions such as I dont know because I didn't work on that part of the assignment are not acceptable and will result in a penalty for either the entire group or specific individual(s).

Assessment Criteria: Group Component (50%) ERD Mapping & Normalisation Tables Implemented SQL (Query) Individual Component (50%) Understanding and analysis of the problem Q and A Forms & Implementation Reports Contribution

15% 15% 10% 10%

10% 10% 10% 10% 10%

Level 2

Asia Pacific Institute of Information Technology

2011

CT014-3.5-2-Database and Web Database Systems

Group Assignment

Page 10 of 11

Performance Criteria: The following guidelines indicate the standard that will be expected for each grade. Distinction (75% and above) Demonstrates an excellent understanding of the problem. The ERD will be implementable and any errors and/or omissions will be minor. The assumptions for the ERD will be logical and almost comprehensive. The database will be implemented to a high standard of functionality, with appropriate integrity constraints in place and will be appropriately normalised. Queries will have been attempted and all or most queries will function. The forms produced would be well designed with user-friendly features and include appropriate validations. The report feature will be well implemented. Toolbar appropriately implemented, well integrating the working prototype application. Documentation will be to a high standard. The student will be able to discuss his/her design and implementation at the presentation and will be able to explain the way in which he/she has attempted the project. Credit (60 74%) Demonstrates a good understanding of the problem. The ERD will be implementable and errors and/or omissions will be minor. The assumptions for the ERD will be logical but with some minor errors and/or omissions. The database will function and will be appropriately normalised although with some errors and/or omissions. Some integrity constraints may be omitted. Queries will have been attempted and most queries will function. The forms produced will be satisfactorily designed with user-friendly features. There may be some minor validations errors. The report feature will be satisfactorily implemented. The toolbar feature will be appropriately implemented, satisfactorily integrating the prototype application. Documentation will be satisfactory. The student will be able to discuss his/her implementation at the presentation and will be able to explain the way in which he/she has attempted the project. Pass (50 59%) Demonstrates some understanding of the problem. The ERD will be implementable although with some errors and/or omissions. The assumptions for the ERD will be logical but with some errors and/or omissions. The database will function and will be appropriately normalised although with some errors and/or omissions. Some integrity constraints may be omitted. The forms produced would be satisfactorily designed though with not user-friendly features with some validation errors. Queries will have been attempted and some of the queries will function. The report feature will be satisfactorily implemented though with some errors and/or omissions. Toolbar appropriately implemented though with some errors and/or omissions and satisfactorily integrated with the application. Documentation will be adequate. The student will be able to discuss his/her implementation at the presentation and will be able to explain the way in which he/she has attempted the project.

Level 2

Asia Pacific Institute of Information Technology

2011

CT014-3.5-2-Database and Web Database Systems

Group Assignment

Page 11 of 11

Fail(0 49%) Demonstrates poor understanding of the problem. The ERD will not be implementable or will not cover major aspects of the scenario. The assumptions for the ERD do not reflect the scenario. The database may have limited functionality and major errors and/or omissions. Most integrity constraints will be omitted. The forms would be poorly designed, with hardly any validations and possibly with integration issues. Queries may not have been attempted or very limited queries have been produced. Other elements not attempted or not satisfactory. Documentation may be limited or not to an acceptable standard. Explanations will be limited but sufficient to demonstrate that the student understands the work that has been submitted. Note: Zero mark will be awarded for single table implementation or insufficient explanations to demonstrate that the student understands the work that has been submitted.

Level 2

Asia Pacific Institute of Information Technology

2011