闪电代写 -代写CS作业_CS代写_Finance代写_Economic代写_Statistics代写_代码代做_IT代写_加急帮助

Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: daixieit

COMP1711/COMP8711

COMP1711

Data Modelling Assignment Part I

Happy-Holidays Car Rental

This is not an assignment that can be done at the last minute!

This assignment submission is electronic (PDF) via FLO.

You are encouraged to work in pairs for this assignment, however it is not mandatory that you do so.

WORTH: The assignment is worth 30% of the assessment.

1 General Specification

(a) Construct the information model

1. List all entities on the Entity Data Dictionary worksheet. Record the name, a description and any aliases. In the Occurrence column described how the entity exists in the organisation. List any dependent entities and indicated in the occurrence which entity it depends on.

2. List all relationships on the Relationship Data Dictionary worksheet. Record the name, a description and any aliases. In the Occurrence column described how the relationship exists in the organisation.

3. List all relationships and entities on the Relationship-Entity Data Dictionary worksheet. For each participating entity, give the multiplicity (both the participation and cardinality). If the relationship is greater than binary then list other entities on subsequent rows

4. For each identified entity and relationship list its name and its attributes on the Attributes Data Dictionary worksheet. For all attributes, give a description, an indication of the data type, length and domain, whether it can be NULL (i.e. optional), and if it can be multi-valued. If it can be multi-valued then list the range of values.

It is recommended that you use copies of the data dictionary work-sheets available as part of this specification on FLO.

I would advise that you step away from the computer when doing this.

(b) Using your answer to (a) draw up and Entity-Relationship Diagram (ERD). The diagram can be hand drawn. It should be at least A4 size. The important criteria are consistency with part (a), clarity and readability.

Entities in the ERD should fully represent the information contained in the data dictionary. That is, include all the attributes and any other necessary information. It should also conform to the Unified Modelling Language specification discussed in lectures and the textbook. Using a different modelling language will result in a grade of Fail with a mark of 1, which allows for resubmission with a maximum mark of 50%. Using software that does not use UML is not an excuse.

An example of entities is shown here:

2 Submissions

The submission of any work will be taken as your claim that it is your own work (or that of you and your partner if working in pairs), i.e. that you cognitively and physically created it. It also signals your agreement to re-do it or similar work under supervision if any doubts are raised about your authorship of the work.

The required submission for Part I of the assignment is:

Tasks (a) and (b): You are to submit finished (final) versions of the work-sheets and the associated ER diagram electronically on FLO as a single or set of PDF files. If you to choose the paper option it should be submitted to the appropriately labelled submission box.

You may also optionally submit a document (a PDF) explaining any assumptions you have made about the specifications. This may have to do with particular multiplicities you assign to relationships and entities, different types of attributes, entities, relationships versus entities. Essentially any piece of information you thought was ambiguous and you think requires additional explanation beyond tasks (a) and (b). This could include information that was clarified by a tutor.

3 Assessment

If you a working as a pair each member will receive the same overall mark.

The assignment is worth 30% of the total assessment. It will be marked out of 60. A guide to the breakdown of the marks over the parts is

(a) 20 marks (5 marks per worksheet)

(b) 40 marks (Marks allocated for entity, relationship, and attribute layout, multiplicities and general diagrammatic representation)

This is only a guide since the submissions are inter-dependent and will not be marked independently. Inconsistencies between them will lose marks.

If you receive a mark in the range 1-49% (less than 30 out of 60) then resubmission of the assignment is allowed up to one week after it is returned with a maximum mark of 50% to be awarded.

4 Specifications

In the case-study description the following notation is used to indicate the type of data items:

(N x) a digit string (integer) of length x

(S x) a character string of length x

($ x) x dollar digits and 2 cent digits

family name (S 20)

personal name (S 20)

title (S 4)

(A) a combination of

street address (S 45)

postcode (S 4)

(D) time and date or either

4.1 General details.

The description is unrealistic in its simplicity and stripped down details but hopefully it has a real world flavour (and gives students insight into the real world use of databases). I have tried to make the description as precise as possible. Any solution that could be reasonably derived from the description will be accepted. For instance, it can often be argued whether a minimum participation should be 0 or 1.

PLEASE base the design on the description, that is, treat the description like requirements. Failure to adhere to the description is very poor professional practice. (If you really believe the description is invalid, please discuss it with me as soon as possible.) I am quite happy, in consulting, to explain any part of the description that is problematic. Also keep up to date on FLO for any clarifications.

4.2 Happy-Holidays

The car hire firm Happy-Holidays, requires a database system to manage their fleet of hire vehicles. Each vehicle in the fleet has a unique fleet membership number (N 3). Also recorded is the vehicle's registration number (S 7), colour (S 20), and make (S 8). All cars are the current model. If a car is fitted with a mobile phone, its phone number (S 12) is recorded. Cars can either be traditional cars or electric cars. Traditional cars are either diesel or petrol operated (N 2). The electric cars have four types (S 5): Battery electric vehicles (BEVs), Plug-in hybrid electric vehicles (PHEVs), Fuel cell electric vehicles (FCEVs), Non-plug-in hybrid EVs (HEVs).

Each Happy-Holidays depot has an identification code (N 2). Also recorded is the depot's address (A), 1 to 4 phone numbers (S 14), and a fax number (S 14). The current location (depot) of vehicles available for hire is recorded.

Happy-Holidays has several different types of daily hire tariffs. For each type, an identification code (S 2) is recorded only with a description of the conditions under which it applies (S 50). For each make of car, the daily rental tariff ($ 3) is recorded for each of the tariff types. Also recorded for each make of car is the daily insurance tariff ($ 3).

The company also keeps records of the inventory items such as GPS navigation systems (N 3), infant car seats (N 2), and booster car seats (N 2). Electric cars come fitted with a GPS navigation system.

When a vehicle is hired, the depot from which it is hired, the hire time and date (D) are recorded. The hirer (client) involved is recorded along with the type (S 2) and number (S 20) of the credit card to be used to pay for that hire. The company only accepts Master card or Visa card. (For security reasons neither cash nor cheques are accepted by Happy-Holidays.) There will be one or up to four persons recorded as being nominated drivers of the hired vehicle (None of these have to be the hirer). A vehicle's kilometreage (N 5) (distance travelled) is recorded when it is hired, and the fuel level for traditional cars only (N 2). At any one time only one vehicle is on hire to a customer. Also recorded is the applicable tariff type, the number of hire days (N 2) and an indication (S 1) as to whether insurance has been taken out for each hire, and whether the customer wanted car seats (N 1) for children, or navigation system (S 1).

A make of vehicle may also be booked for a future hiring, in which case, the nominated pick-up depot, the starting time and date for the booking (D), and the intended number of hire days (N2) are recorded. An optional preferred colour (S 12) may be recorded. A client may make any number of bookings.

Happy-Holidays records the individual details of any client the first time that the person or the company1 has business with the company. A client's name (C), address (A) and one or two contact phone numbers (S 14) are recorded along with a generated unique client identifier. This identifier is used for all subsequent references to that client. If the client is a company, they must have a (single) nominated person also recorded as their representative. The details of such representatives are recorded as though they were person clients. A (person) client's driver's license number (S 12) is recorded the first time that they hire a vehicle or are a nominated driver.

For each vehicle, a service history is kept. It contains for each past service, (scheduled or repair service), the date (D), the cost (\$ 4), a service description (S 50) and the identification of the depot where the servicing was done. A vehicle may have had none or several past services. For all vehicles, the next scheduled service has the associated kilometrage (N 5), date-to-be-done-by (D) and the depot to do the servicing recorded. Any minor damages to the car such as scratches or minor dents are recorded as comments (S 200), along with the date they were entered into the database (D). Cars with significant damage are recorded as non-serviceable (N 1) and can be written-off.

4.3 Operations and Questions

The “Operations and Questions” are here to help verify/validate you design. You do not need to provide answers to questions for the assignment.