Course:COMP1419 Distributed Data Management Technologies Lecturer: Dr Chiyaba Njovu

Coursework Number: 1 of 1 Date Set: Wednesday 26/10/2006

Coursework ID: 132354 Deadline Date: Friday 12/12/2007

Contribution: 30% of course Return Date: 17/01/2008

This coursework should take an average student who is up-to-date with tutorial work approximately 30 hours Learning Outcomes: All Plagiarism is presenting somebody else’s work as your own. It includes: copying information directly from the Web or books without referencing the material; submitting joint coursework as an individual effort; copying another student’s coursework; stealing coursework from another student and submitting it as your own work. Suspected plagiarism will be investigated and if found to have occurred will be dealt with according to the procedures set down by the University. Please see your student handbook or the “Little Book of Plagiarism” for further details of what is / isn’t plagiarism.

An electronic copy of your work for this coursework must be uploaded by the midnight on the Deadline Date using the link on the coursework Teachmat page for COMP1419. It must be in a Word document, and there are limits on the file size (currently 8 megabytes). The last version you upload before the deadline will be the one that is marked. Make sure that the file you upload is virus-free and not protected by a password otherwise it will be treated as a null submission. Your work will be submitted for electronic plagiarism checking. Your work will not be printed in colour. Please ensure that any pages with colour are acceptable when printed in Black and White. There is no need to submit a paper copy of this coursework. Coursework submitted after the published deadline without an extenuating circumstances claim will receive a ZERO grade. If you have extenuating circumstances you may submit your coursework up to two weeks after the published deadline without penalty but this is subject to acceptance of your claim by the School Extenuating Circumstances Panel. If your claim is rejected then you will receive a zero grade for your work.

• • • • • •

Coursework Regulations
1.

1

Coursework submitted more than two weeks late will be given feedback but a grade of non submission will be awarded regardless of any extenuating circumstances. However, if your Extenuating Circumstances claim is accepted then the Extenuating Circumstances Panel will recommend to the Progression and Award Board that you be permitted to retake a different item of assessment at a future assessment point. Please refer to the University website for further detail regarding the University Academic Regulations concerning Extenuation Circumstances claims. .
2.

Do not ask the lecturers for extensions to published deadlines - they are not authorised to award an extension. All courseworks must be submitted as above. Under no circumstances can they be accepted by School academic staff.

3.

Please note: Coursework will only be returned by the above Return Date if the coursework is submitted on time and is submitted in accordance with the specification provided. Detailed Specification The revived Timely Prosecution Services (TPS) has a number of prosecution judges. Each judge has a list of outstanding cases over which he will preside. Only one judge presides per case. For each case, one prosecuting counsel is appointed to represent the TPS board. Cases are scheduled at one court for an estimated duration from a given start date. A case can try more than one crime. Each crime can have one or more defendants. Each defendant can have one or more defending barristers. If a crime has more than one defendant, each defendant can have one or more defence counsels. Defendants may have more than one outstanding case against them. There is also a requirement that we need to maintain a history of cases a judge presided over and record the outcomes of all these cases. Requirements In this coursework, you are required to perform the following activities:
1.

Devise a comprehensive conceptual model, using Chen’s notation’s or Crow’s foot notation or in the ERWIN or Visio software case tools, for a centralised database system to be installed and managed at the Timely prosecution Service (TPS) Headquarters. The basic model should be based on the business rules given. Bonus marks will be awarded to students whose model incorporates additional business or operational constraints which must be clearly stated in a section of its own in your written submission. Your conceptual model should clearly show all entity types, their relationships, and cardinality and

2

participation constraints of each relationship together with clear explanations of the business rules or assumptions that are being modelled. 2. Map the conceptual model devised in (1) above into a set of relations in the relational data model. You will need to clearly specify the constraints implemented in the relational data model.
3.

Implement the relational logical schema devised in (2) as a database system in an oracle environment, insert enough data and demonstrate the full system functionality using SQL queries and possibly reports. Remember to use table level constraints on all your tables.

4.

By querying the relevant data dictionary views, produce a listing of the TPS database metadata.

5. Create an appropriate user interface using Oracle forms to allow users to input data.
6.

Suppose the TPS was to be distributed according to the different regions in the UK (East, West, South and North), devise a distributed database design strategy that would enable the TPS officers to monitor traffic cases according to the regions. Your system should also be able to track cases tried in different regions at different times, where applicable.

7.

Using two schemas (Obiwan and quigon), implement a distributed database system and ensure that data for different regions can easily be identified. Using Oracle SQL, you will need to demonstrate distributed database functionality using examples of at least two (2) global view queries and five examples of local view queries. For example:• • • • •

8.

Cases by a given prosecutor in different states or courts State with the largest number of a particular type of crime in a given year The most common types of crimes in a given state Most adjourned cases in a given period of time Judges with more than ten(10) adjourned cases in a given year.

3

Deliverables You will be required to submit your implementation of the database system at 18.00 pm on the 13th December, 2007 and all work that will not have been submitted by then will attract a mark of Zero. 1. You are required to submit a written report supporting your implementation. This should include your design decisions and rationale on the following issues:

An ER diagram showing the base model for the Timely Prosecution Service System. A relational database schema for the TPS System A list of screen shorts of each user interface form or report or some useful form of evidence of testing of your system A reflective discussion on how your design and implementation could be improved and suggestions for future work, if any.

• •

2.

You will be required to demonstrate your work earlier submitted to a tutor on a day and time that will be allocated to you prior to 13th December, 2007. Note that tutors will be at liberty to ask questions relevant to your work in order to satisfy themselves that it is your own work.

Assessment Criteria To pass this coursework, students must: • • •

Submit a well documented EER model Demonstrate the ability to manipulate data stored in one database Demonstrate how to use Oracle Developer tools for user interface design Demonstrate an appreciation of the underlying principles in database engineering and how they can be used in problem solving in disparate application domains.

Grading Criteria 70% and above An extremely well written and presented report which shows a complete model and implementation of the State Patrol database. The report should also

4

demonstrate a clear understanding of problem solving in general and distributed data management in particular. Between 60 and 69 Report lacks some detail but shows a complete design model and a working implementation of the system. The report also shows a clear understanding of the principles in distributed data management. Between 50 and 59 Report lacks some detail but demonstrates some understanding of both design and implementation issues in distributed data management. Between 40 and 49 Report lacks some details but the design model and implementation demonstrates some understanding of the core principles in distributed data management. Below 40 Weak report and an inadequate implementation which fails to demonstrate basic understanding of the principles involved. There may be many technical errors or many areas of the report missing. Submission This is an INDIVIDUAL assignment. Your report should include a well documented ER model produced by ERWIN case tools and a list of assumptions essential for understanding your design decisions. This part of the report should not exceed five (4) A4 sides including diagrams. Your implementation should conform to your model and any deviations should be clearly explained as part of your design decisions in mapping from the conceptual to the logical schema. Screen shorts of forms and reports illustrating your answers to some of the requirements should be clearly labelled as such. The relevant SQL code should also be included. You will NOT pass the coursework unless you have demonstrated your implementation of the system and submitted a report.

5

Note that it is acceptable to learn from colleagues, but it is a serious matter if you copy from each other. You must also comply with the deadline date and the school rules for late coursework submission will be applied.

6